Starts and Saves
Choose between continuing an existing campaign, starting a new one, and finding the Windows files for your current run.
- Fix a New Campaign Freeze
Update Imperionis in Steam before retrying New Campaign. The developer published a specific fix for a launch-era startup freeze. On the updated build, continue through commander setup and the first day normally. Esc opens the quit menu in the newer controls update.
- Find Your Windows Save Files
On Windows, paste %APPDATA%\imperionis into the File Explorer address bar and press Enter. This opens the current user’s AppData\Roaming\imperionis folder. An ongoing campaign can continue after the Day One update. Commander traits are chosen when you start a new campaign.
- Your First Days in Gaul
Start Imperionis with a commander whose trade-off fits the way you plan to play. Review the century’s condition at camp, keep enough provisions to reach the next stop, and read the day summary after each choice. Before the first engagement, check the objective and enemy rather than judging readiness by headcount alone.
Choose your starting point
Use the startup guide if a first or second fresh run stops before you can begin playing. The player report that prompted the hotfix describes a repeat failure when starting another run after finishing one. Its most useful detail is the difference between a fresh start and continuing existing progress. Make that distinction before deciding which instructions to follow.
Use the Windows file guide if the game is playable and you simply need to locate the data for the current Windows account. The developer provides a local Roaming folder. The existence of a local folder does not show whether a second installation can fetch your campaign, and identifying the directory is a different task from locating the cause of a freeze.
What changes with a fresh campaign
In the updated full game, a new campaign takes you through a commander window before the first day. The Day One notes describe options for appearance, cognomen, attribute adjustments, and a commander trait with advantages and drawbacks. This step is an expected part of starting. Its absence while continuing an old run is also expected, because existing campaigns keep working without a trait.
When comparing advice, check which build and edition the writer is talking about. The original Day One announcement was followed by a corrected build notice. A separate notice addressed new campaign startup, and a later controls update described Esc opening the quit menu. The earlier workaround in the discussion was guidance for the earlier broken build. On the updated game, use the commander window and opening event as your checkpoints.
Full release and demo
Steam publishes the full game and demo under different app entries. The demo is a short campaign sample with three combat missions in its first 24 in-game days. The full release is a longer route with more development options. The developer says the Day One update also went to the demo, but it is worth identifying the entry you are using before applying a fix for a full-release player report.
If you only want to resume an ongoing full campaign, there is no commander setup step to recover for that run. Continue it in the game and check the local folder only when you have a specific reason to find your files. If your next new campaign still fails after updating, use the startup guide’s reporting details to record the stage and edition before asking for help.
Before you compare two installations
Start by identifying which Windows account launched the game. The Roaming directory belongs to that user. If you are on another account or another machine, the same shortcut can point to a different place. The developer’s answer establishes the directory for a local installation and says cloud saves were still being worked on when the reply was written. It does not describe a cross-machine transfer or tell you how to replace one campaign file with another.
Keep the issue you report as narrow as the behavior you saw. For a local-files question, state which account and path you checked. For a new-start issue, give the point at which the screen stopped and whether a continued campaign still works. For a missing trait, first check whether you were continuing. These distinctions give you a useful next action even when you cannot immediately identify the build number.