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

Do this in order

1. Move equipped, fallback and market-pending items out of the intended combine set if the interface permits.
2. Match exact item labels and rarity, not color alone.
3. Test one controlled batch while watching inventory before and after.
4. Record what was consumed, what appeared and whether any item type was excluded.
5. 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 current community thread is narrow. A respondent says their items combined when six were collected and asks whether the original poster confused similar colors. The reply also explains why Jewels may not be automatically combined: a full inventory can block other valuable drops. That reasoning is a player explanation, not a developer statement. It is useful as a test hypothesis, not a published rule.

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 can create pressure because they occupy space while players wait for a clear combine path. Do not solve that pressure by inventing a hidden setting or rate. Separate usable Jewels, uncertain Jewels and a controlled test batch. If the inventory is close to full, make room through items whose disposal path you already understand rather than sacrificing the least-understood category.

The official roadmap indicates that convenience improvements are being developed from player feedback. Until a release notice confirms a change, the current workflow remains the one visible in the client. When a Jewel or synthesis update ships, it should trigger a review of this page, the gear decision guide and any tool that assumes the old inventory behavior.

What a trustworthy update looks like

A trustworthy update names the official notice, effective date and affected behavior. It does not turn “planned” into “released,” and it does not refresh the page timestamp because the site rebuilt. The daily monitor will add a new update only when an official post or substantive community report changes the answer.

Until then, the stable recommendation is procedural: protect important items, match labels, test one batch, record the result and stop when the behavior cannot be explained. That may sound less exciting than a rate table, but it prevents irreversible errors while the evidence is still thin.

Quick answers

Next useful pages