PeakScrollFix

PeakScrollFix (scroll disappearing fix)

⚠️ WARNING: MUST READ FIRST

• This patch may cause the game to fail to start. This module will intervene in the singleton initialization process during game startup. In some circumstances, it has caused the game to get stuck in the startup phase (crash/black screen). Please make sure you know how to delete it before installing it.
• Please delete this patch immediately after completing the Bookworm Badge to avoid conflicts with this patch the next time the bug is officially fixed (conflicts manifest as abnormal startup or disordered achievement/page records).
• Deletion/rollback only requires one step: rename PeakScrollFix.dll to PeakScrollFix.dll.disabled (or delete it directly). The main game file has never been modified.
• If the game cannot be entered after installation: rename and roll back first, and then bring BepInEx\LogOutput.log and Player.log to the author for feedback.

What does this patch fix?

After the official update of PEAK 2.4.b, the scroll (GuidebookPageScroll) next to the campfire (including the mountaintop campfire) will disappear directly after use: no guide pages will be generated, the number of pages will not increase, and the bookworm achievement cannot be advanced.

The reason lies in the game's own code (not the archive, nor the module conflict):

• 2.4.b adds a "progressive unlocking" threshold check to the book page, and the new code in Guidebook.GuidebookPageValid will read the AchievementManager singleton without null value protection;
• The single instance will be repeatedly destroyed/rebuilt at the segment junction (the campfire is exactly at the segment junction), and there is an empty window that is null for an instant;
• Open the scroll during the window period → NullReferenceException → Page selection is interrupted, the page is never generated, but the scroll has been destroyed by the coroutine as usual → "The scroll disappears directly when opened".

This patch will fill in the single instance and its page count data during the window period, or use the game's own Steam statistics (TotalPagesRead) to complete the same threshold verification and page count record, allowing the scroll to return to normal page generation after consumption.

Install

Manual installation (recommended)

• Install BepInEx 5.x (x64 / Mono version): Unzip to the PEAK game directory (Steam → Right-click PEAK → Manage → Browse local files), make winhttp.dll, doorstop_config.ini, BepInEx\ and PEAK.exe at the same level; first start the game and let it generate the directory.
• Put PeakScrollFix.dll into:

PEAK\BepInEx\plugins\PeakScrollFix\PeakScrollFix.dll

(Create a new folder if it does not exist; you can also drop it directly under plugins\)

• Restart the game (BepInEx only loads the plug-in at startup).

Module manager installation: Just use the zip of this package to install it (it has been packaged according to the specifications and depends on BepInEx-BepInExPack_PEAK).

Verify whether it takes effect

• Open PEAK\BepInEx\LogOutput.log and you should see:

[PeakScrollFix] v1.1.0 loaded. Guard active, 3/3 concrete patches applied (no generic patching).

• After crossing the section in the game, go to the campfire to pick up the scroll and use it:
• Book pages appear normally in the hand (no longer disappear out of thin air);
• [PeakScrollFix]... prompt may appear in LogOutput.log (complementary instance / no manager verification / direct record page) - if it appears, it means that the time when it would have crashed has been blocked;
• NullReferenceException... GuidebookPageValid no longer appears in C:\Users\\AppData\LocalLow\LandCrab\PEAK\Player.log;
• Progress accumulates normally: Successfully Updated Stat: TotalPagesRead (N).

N is the page flag bit mask, not the page number: Intro=1, Mushrooms=2, Campfire=4, Revival=8... accumulated page by page.

Uninstall/What to do if something goes wrong

| Situation | Action |

|---|---|

| Uninstall normally (for example, …