Librarian-AP v1.1.3
Client-only hotfix. 1.1.2 was released to stop a New Game inheriting the previous run's progress,
and it only fixed part of it. This completes that fix.
Update if you are on 1.1.2
Keep your existing apworld and seed — nothing on the generation side changed, so no
regeneration is needed. Extract the zip and dropLibrarian/into your Steam install (overwrite).
The title screen bottom-right should readLibAP v1.1.3.The included apworld is a version-label bump only; grabbing it is optional and changes nothing.
What was still broken
If you launched the game, let it load an existing save at the title, then pressed New Game, the
new run could still adopt that old save's history — sending a burst of level-up and row-completion
checks it had never earned, straight into the multiworld.
1.1.2 closed two of the paths that did this. Two more were reading the old save directly and were
missed; both are now closed, along with the underlying rule so it cannot happen a third time.
If this happened to your run
Checks already sent cannot be un-sent by updating. If a run received a burst of items it never
earned, it is best to regenerate and start new.
Everything else
Unchanged from 1.1.2. Your saves, slots and the crash-recovery fix from that release all continue to
work as they did.
If something breaks
Send crash_trace.log (header should read mod=1.1.3), the last ~200 lines of UE4SS.log, and one
line on what you were doing.