Path of Idle: Old Gods Rising Troubleshooting & Common Issues

The fastest fix for most reported issues is updating to the latest official patch. Version 1.0.7 fixed possible Baptism errors and possible black lines on the Chapter 20 map. Version 1.0.5 changed Blessing Talent Points and required a Talent reset. Version 1.0.3 fixed Rare and Legendary Rune Pouches not being craftable. Many community reports describe symptoms that were already resolved in a later build. Before trying reinstalls, registry edits, or third-party downloads, confirm the installed version against the latest Steam announcement. Restart Steam after updating to ensure the patch fully applies.

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 to the latest version from the manufacturer. Third, disable Steam overlay and any third-party overlays for one test launch. Fourth, if the game previously worked, check whether a recent Windows, macOS, or driver update changed compatibility. The official requirements list Windows and Apple-silicon macOS; SteamOS or Proton compatibility on Steam Deck is unverified. If the issue persists after these steps, record the exact moment the black screen appears and include it in a 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.

Before assuming data loss, check whether an update changed a system you were relying on. Version 1.0.4 converted obsolete Agony Scales back to Abyssal Scales; a player who did not read the note might think currency disappeared. Version 1.0.3 removed Loot Progress and replaced it with Exploration Progress, which changed how rewards are earned. A full Vault can also replace lower-level equipment automatically since version 1.0.7, which may look like an item vanished when it was actually auto-replaced. Check the Vault history, update notes, and automation filters before concluding that save data is corrupted.

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.