If your Timeline is stuck: do not start by editing a save file. v0.110 fixes one specific case where an Epoch unlock earned at the end of a run could vanish and permanently block progress. The official notes say affected saves are repaired when loaded. Update to the beta, launch cleanly, load the affected profile, and check the Timeline before trying anything invasive.
What v0.110 actually fixes
The wording matters. Mega Crit documents a bug where an Epoch unlock earned at the end of a run could be lost, permanently blocking Timeline progress. v0.110 fixes the cause and repairs affected saves on load.
That does not mean every locked Timeline node is a bug. A node may still depend on normal progression, a run result, a different profile, or content not yet reached. The repair targets the missing Epoch state described in the patch notes.
| Symptom | Likely next step |
|---|---|
| Progress stopped immediately after earning an Epoch | Try the v0.110 load repair |
| Timeline is locked on a different profile | Open the profile where the progress was earned |
| Problem appears only with mods | Retest without mods before blaming progression |
| Main branch still shows the issue | Remember the repair is currently in beta |
| A node is locked but no Epoch was lost | Continue normal progression and verify its requirement |
Safe repair checklist
Use the least destructive path first.
- Finish or record any run you care about. Branch changes during an active Early Access run add uncertainty you do not need.
- Confirm the affected profile. Timeline progress belongs to the profile state you are loading, not merely the installation.
- Close the game fully. Do not switch branches while it is still running.
- Opt into beta v0.110.0 in Steam. Wait for the update to finish.
- Launch without unnecessary mods. A clean first load makes the result easier to interpret.
- Load the affected profile and open Timeline. The official repair is performed on load; there is no separate repair button in the patch notes.
- Restart once and check again. This confirms the repaired state persisted.
If the missing progress returns, stop there. Extra “fixes” only add risk.
How to tell whether the repair worked
Look for a state change, not just the absence of an error message.
- The previously blocked Timeline route can advance.
- The earned Epoch state is present after restarting.
- Loading the same profile twice produces the same result.
- The problem remains fixed with the same branch and mod state.
Take one screenshot of the branch version and one of the Timeline state if the problem continues. Those two facts make a bug report far more useful than “my unlock is gone.”
Profile, branch, and mod mix-ups
Progression troubleshooting often goes sideways because three different variables change together.
Profile
Confirm the selected profile before testing. A healthy Timeline on another profile does not prove the affected one was repaired, and an empty profile is not evidence of data loss.
Branch
The current main branch is v0.107.1. The documented automatic repair is in v0.110 beta as of this guide's update. If you switch back to main after testing, do not assume beta-only card or save behavior will remain identical.
Mods
Mods can change unlock flows, dependencies, and error behavior. Disable them for the first repair attempt. If the Timeline works cleanly, re-enable mods in small groups until the conflict is isolated. The Steam Workshop mods guide covers dependency and version checks.
What not to do first
Avoid these as opening moves:
- downloading a stranger's progress file;
- changing undocumented save values;
- deleting the profile to “force a refresh”;
- copying beta saves over main saves without a backup plan;
- stacking several community workarounds before checking the official repair.
Manual editing can hide the original problem, unlock the wrong state, or make future support harder. It is a last resort, not a faster version of the official fix.
If the Timeline is still stuck
Collect a small, precise report:
| Field | What to record |
|---|---|
| Game version | Exact number shown in game |
| Branch | Main or beta |
| Profile | Which profile is affected |
| Lost moment | End of which run or unlock |
| Mods | None, or a complete list |
| Repair result | What changed after the first v0.110 load |
Then use the game's official feedback or bug-report path. Describe observable events in order. “I finished a run, saw an Epoch unlock, reopened Timeline, and this node remained blocked” is actionable. “Timeline broken” is not.
The practical takeaway
v0.110's repair is good news because it handles the documented failure automatically. The sensible order is: verify profile, update, load cleanly, check persistence, then report with evidence if needed.
Early Access progression can change. Keep branch labels in screenshots and avoid unsupported save edits unless official support specifically directs you there.
