Path of Idle: Old Gods Rising Troubleshooting & Common Issues

Version 1.1.3 fixes the sell tutorial error, Corrupt Affixes not responding to Equipment Grade and Rare Rune stats being lower than Fine Rune stats. It also intentionally migrates Doom Stage 2 saves to Stage 3 and Stage 3 saves to Stage 5. Update, restart and compare the exact symptom before changing files. The note does not promise recovery for old item values, explain unrelated crashes or make every post-update stage mismatch a confirmed bug.

Continue with: check intended Doom migration · check current Grade behavior

Source: Official version 1.1.3 fixes and migration rules ↗

Update to 1.1.2 and retest the exact action if your symptom matches one of six named fixes: Codex Seals not affecting Vault equipment affixes, Legendary Rebirth's special effect not applying, Market hide rules failing, Stele possibly advancing incorrectly, Season reward display after clearing or deleting a save, or inability to create Nightmare Difficulty after clearing or deleting a save. Record the old and current version, restart once, and reproduce with the smallest safe setup. The announcement does not promise retroactive repair, identify every affected state, or prove that a different Market, Stele, Rebirth, or save symptom shares the same root cause.

Continue with: read the complete 1.1.2 boundaries

Source: Official version 1.1.2 announcement ↗

Update before diagnosing, but do not assume an update fixes every symptom. Version 1.1.2 names six current fixes, including Market hide rules and Nightmare Difficulty creation after clearing or deleting a save; version 1.1.1 fixed Advanced Difficulty weapon Transmog display, incorrect Baptism skill tips, and one unnamed achievement issue. Neither promises that every related symptom is solved. Before trying reinstalls, registry edits, or third-party downloads, compare the installed version with the latest official announcement and restart Steam after updating. If the problem remains, preserve the current state and collect a reproducible report.

Source: Official version 1.1.2 notes ↗

Small Mill stated in official Steam announcements that demo save data could be carried directly into the full release, and the demo would close before launch. If your demo progress is missing: confirm you are using the same Steam account, wait for Steam Cloud synchronization to finish, then launch the full game. Do not delete local files, start new saves repeatedly, or download replacement saves from third-party sites. If the progress still does not appear after a full Steam restart, report the issue through the official Steam Community discussion channel with your game version, platform, and a description of what you tried.

A black screen on launch can have several causes. First, verify game files through Steam: right-click the game in your library, choose Properties, Installed Files, and Verify Integrity. Second, update your graphics driver. Third, disable overlays for one test launch. Fourth, check whether a recent Windows, macOS, SteamOS, Proton, or driver update changed compatibility. Steam currently rates the game Deck Playable, but that does not diagnose a specific launch failure. If it persists, record the exact moment, operating system, compatibility tool, and installed patch for the bug report.

If large battles stutter or the map lags, start with the in-game Hide Combat Effects setting, which the developer added during final demo updates. Close overlays and background applications for a comparison run. Lower the refresh-rate setting if needed; an earlier bug where refresh-rate settings did not apply was fixed in demo version 1.0.0.0. Keep the game and graphics driver current. If the issue is specific to one stage or one enemy type, include that detail in a report rather than treating it as a general performance problem. Performance on Apple-silicon macOS may differ from Windows; note your platform when comparing with other players.

Version 1.0.7 fixed possible Baptism errors. If you experience a Baptism-related crash or unexpected result, update first. Version 1.0.5 intentionally changed Blessing to grant one Talent Point every five levels, up to six, and the developer explicitly told players to reset Talents after updating so the new points apply. A character that appears weaker after an update may simply need the Talent reset, not a replacement. Version 1.0.7 also fixed talent slots not updating when Inspire changes. If a build looks like it has missing points or slots, confirm the installed version and refresh the affected setup before replacing the character.

If loot seems to vanish after Right Click or Put In, first check the tabs at the bottom of the Warehouse: in one resolved report, the developer said the item had most likely entered the favorites list, and the player found it in a Vault tab. For other missing-item symptoms, stop automated selling or equipment changes, then check categories, filters, every equipped character, recent orders or crafting, and the full-Vault replacement rule. Patch 1.0.12 improved Warehouse Vault category display, but it does not confirm a universal item-loss fix. Record the item name, previous location, installed version and immediately preceding action before reporting a different reproducible case.

Continue with: Inventory, Vault and filter guide

Source: Developer reply: loot found in a Warehouse Vault tab ↗

Patch 1.1.1 says it fixed an issue where an achievement could not be obtained. The announcement does not name the achievement, explain the trigger, or promise a retroactive grant, so it is not evidence that every achievement issue is fixed. Confirm that Steam is online, update the game and Steam client, restart once, and reproduce the exact condition in the current full-release build. Capture the achievement name, completion screen, installed patch and result. Do not edit a save or use an achievement tool; report unresolved cases with those details.

Source: Official version 1.1.1 announcement ↗

Stop launching and closing the game repeatedly, because each new save can make recovery harder. Note the save slot, Season, last known good progress, Steam Cloud status and whether another device was used. Patch 1.0.12 lists a fix for frequent saving, but that statement does not promise recovery of an already rolled-back save. Follow the non-destructive save-error checklist and contact the developer through Steam if the older state persists.

Continue with: Save error and recovery checklist

Source: Official version 1.0.12 update ↗

If the game freezes or crashes during a specific action, reproduce it consistently before reporting. Note the exact screen, the action immediately before the freeze, the installed version, and your operating system. Try the same action after a restart with overlays disabled. If it only happens during a specific skill, enemy, or stage, that detail is more useful to the developer than a general 'it crashes' report. Do not install third-party DLLs, registry cleaners, or replacement executables from unofficial sources; these can cause additional problems and invalidate your warranty or support eligibility.

A good bug report includes: installed game version, operating system and hardware summary, exact screen or menu where the issue occurs, the action immediately before the problem, whether it repeats after restart, and a screenshot or short video if possible. For progression issues, include the relevant chapter, class, town building, item, skill, or automation rule. Link to the official announcement or discussion when the behavior might be a documented change rather than a bug. Submit through the developer's official Steam Community channel. Avoid vague descriptions like 'it broke' or 'things are gone'; specific details let the developer reproduce and fix the issue faster.

Always start with reversible steps. Step one: confirm the installed version and update if needed. Step two: restart Steam and the game. Step three: verify game files through Steam. Step four: reproduce the issue with overlays and optional visual effects disabled. Step five: change one setting at a time and note the result. Only after these steps should you consider reinstalling the game—and before doing so, confirm how Steam Cloud protects your save and back it up through an official method. Never delete saves, edit the registry, or run third-party repair tools as an early step.

Not every unexpected behavior is a bug. Version 1.0.5 intentionally changed Blessing Talent Points and required a reset. Version 1.0.3 changed loot progression to Exploration Progress. Version 1.0.4 converted obsolete currencies. If your symptom matches a documented change, update your build or workflow instead of reporting it as a bug. A bug is behavior that contradicts the current official note and reproduces after restart with the smallest possible setup. Learning the difference saves you and the developer time.