War of Genesis: Idle Loot Auto-Combine and Jewels Guide

Do this in order

1. At User Level 17 or later, open Auto-Combine from the icon at the bottom of Inventory.
2. Review the Equipment and Accessories filters for tier, level or identical levels. On an updated client, look for the Jewel target-tier setting at the bottom of the same window.
3. Move equipped, fallback and market-pending items out of the intended combine set if the interface permits.
4. Test one controlled batch while watching inventory before and after.
5. Record what was consumed, what appeared and whether any item type was excluded.
6. Disable or narrow the rule if the result cannot be explained.

Why automation needs a protected set

Auto-combine solves a real idle-game problem: loot keeps arriving while attention is elsewhere. The same feature can silently destroy option value if it treats a class fallback, market item or rare stat roll as ordinary material. Before enabling it, define a protected set. At minimum that includes equipped gear, a known-good alternative for each class you plan to test, and anything whose purchase or listing state is unresolved.

The September 14 FAQ places Auto-Combine at the bottom of Inventory from User Level 17 and documents Equipment and Accessories filters. Two days later, the developer announced a Jewel target-tier setting at the bottom of the existing Auto-Combine window. Check the setting in your current client before following an older screenshot. A player separately reported that six matching items combined; the announcement did not establish that count as a general formula.

Run a one-batch audit

Write down the exact input item names, rarity labels and count. Take an inventory screenshot before the test. Enable or trigger only the smallest relevant automation, then compare the resulting inventory. If six items disappear, identify the output rather than assuming success from the count change. If nothing happens, check labels and eligibility before adding more items.

A one-batch audit prevents two common mistakes: trusting color when labels differ and repeating a failed action until a large quantity is gone. It also produces the evidence needed to improve this guide. A report that includes build/date, inputs, output and the visible setting is far more useful than “auto combine is broken.”

Jewels are an inventory decision first

Jewels take up space quickly, but a broad automatic rule can eat a gem you meant to socket. If the announced target-tier control is present, start with the lowest tier you can afford to lose and compare inventory before and after one batch. Keep equipped or valuable Jewels outside the test where the client allows it.

If the Jewel control is missing, do not assume a hidden switch or keep toggling unrelated Equipment filters. Check that the client is current, then use the visible manual workflow or ask official support. The announcement describes an intended change; it does not replace what your own screen shows.

What a trustworthy update looks like

The September 17 feature notice gives the intended setting and location. A separate completed hotfix notice names only client stability; it does not confirm every feature in the earlier list. Until a feature-specific completion note or a current client test is available, this guide keeps the distinction visible.

The safe routine has not changed: protect important items, read the tier labels, test one batch and stop if the result is unclear. A precise menu path is useful only when it matches the version in front of you.

Quick answers

Next useful pages