Long Session Checklist: Memory, Inventory and Disconnect Recovery

This game is designed to be left alone. So the thing worth preparing is not a technique but whether the session itself holds up.

Across player feedback, five things go wrong: memory, inventory, what auto-combine actually covers, what happens after a disconnect, and the window itself. Each one below comes with something you can do about it.

1. Memory: leave headroom

Long-run memory use is the most common technical complaint. A roughly 46-hour Japanese review is specific. Memory footprint about twice that of comparable idle games, a leak over long sessions. And a window that stays unreadable at maximum size on a 4K display.

What helps:

• Do not run it alongside a heavy game.
• Restart the client periodically instead of leaving it up for days.
• If your machine is tight on memory, lower the resolution or close other programs first.

2. Inventory: do the arithmetic before you leave

This is the most immediate problem. Players in the Steam discussions work out that a four-to-five-hour session needs around 55 inventory slots, and longer sessions need more.

The catch is that auto-combine only covers part of the pipeline:

• Gems are never auto-combined and must be handled manually.
• Nothing in storage takes part in auto-combine, so parking materials there removes them from the loop.
• Equipment auto-combine does run while you are away, but only for some grades.

So the correct move is: keep materials you want merged in the inventory, and clear out gems once before you leave. Storage does not free up space. It just parks items somewhere they will not be processed.

3. Disconnects: farming stops until you confirm

This one costs real progress. A roughly 110-hour English reviewer documented it: after a disconnect you must confirm manually before equipment farming resumes. Until then the session yields gold and XP but no gear. He lost about five hours to it.

Check your connection before walking away, and check for a confirmation prompt the moment you come back. If you run it overnight, make it a habit.

4. The window: there is no minimise button

It is meant to sit in a corner, but on a large or high-resolution screen the default window gets too small to read. The workaround players use is to untick always-on-top in the settings and cover it with a folder window. Expecting normal minimise behaviour will not work.

5. Login and instances during launch week

If you started during the launch rush, you may also have met an unresponsive login button, a stall at 100% loading, or being unable to enter raids and arena. The workarounds players found were switching DNS (1.1.1.1 was suggested) or clearing the cache. Those were server-side conditions, not a misconfiguration on your machine.

The one-paragraph version

Before you walk away: count your inventory slots, clear gems once, confirm the connection is stable, untick always-on-top and prepare something to cover the window. If you are leaving it up all day, give the client one restart in the middle.

Where to go next

Official requirements and startup troubleshooting are in System requirements and launch fixes. Auto-combine rules and inventory management are in Synthesis and dismantle. Whether the desktop-idle design is worth it at all is covered in Desktop idle explained.

Sources

• Steam user reviews: 526 total, read 2026-09-15 — memory footprint, 4K window size, missing auto-reconnect and inventory capacity all come from player accounts there
• Steam discussion threads on auto-combine, the missing minimise option and the 100% loading stall: read 2026-09-15
• Official store page system requirements: https://store.steampowered.com/app/4891320/War_of_Genesis_Idle_Loot/ (checked 2026-09-15)

Every performance and stability claim here is a player report; the developer publishes no runtime standard. This wiki has not run a twelve-hour local soak test.