The short answer
The short answer
Use a normal expedition, confirm the trigger, and finish the required state. Bookworm requires reading the Scoutmaster's final journal entry; Medieval History requires passing Citadel without trap hits; Gourmand requires cooking and eating four named foods and escaping alive; Daredevil requires landing in the Mesa cannon target zone; Aeronautics requires six balloons and floating. Saves, reconnects, and Custom Runs can change whether progress counts, so record the version and host state.
Correct trigger conditions for five high-demand badges
The criteria below are transcribed from the community-maintained PEAK Wiki badge list and cross-checked against the official patch notes where a bug fix is named. The wiki is a secondary reference, so use the in-game Accolades description and current patch if they differ. A successful action in a Custom Run should not be used to prove a normal-run trigger.
The “what counts” notes are where many failed attempts go wrong. Some badges grant immediately, while others require an end campfire or a living escape. Feeding another player can credit the feeder for food-related badges; it does not automatically credit the player who receives the item.
| Badge | Correct trigger | Custom Run? | Save or reconnect impact | If it fails | Version status |
|---|---|---|---|---|---|
| Bookworm | Find and open Scrolls until the Scoutmaster's final journal entry is read. Region-specific entries must be opened before leaving the relevant region. | Disabled; use a normal expedition. | Patch 2.4.c fixed progress resetting at the start of each run and Scrolls disappearing. The temporary salute grant is only for players who already earned it. | Use the normal scroll route again; if already earned before the bug, flip to the second Guidebook page and use the salute emote as the official temporary grant. | Fixed in 2.4.c; player report pending if progress still resets. |
| Medieval History | Pass THE CITADEL without being hit by traps. Petrified Rocks do not count as a trap hit; arrow-trap activation with an item and Drowsy from luggage traps do count. | Disabled; use a normal expedition. | Patch 2.5.a fixed a Citadel save case; 2.6.b fixed a Gloom or Citadel revive case. A loaded or reconnected run can still be difficult to classify. | Retry in a fresh normal run, avoid all trap triggers, and record whether you were revived, reconnected, or loaded from campfire. | Named cases fixed in 2.5.a and 2.6.b. |
| Gourmand | Cook and eat Half-Coconut, Honeycomb, Yellow Winterberry, and Egg, then escape alive. Well-Done, Burnt, and Incinerated versions count; feeding credits the feeder. | Disabled; use a normal expedition. | Patch 2.6.a fixed host run-based progress at a campfire, including food progress such as Gourmand. Earlier reconnect progress behavior is version-sensitive. | Repeat all four items in one tracked run, confirm the host saved at a campfire, and escape alive; do not assume a partially saved list survived a host change. | Progress save fixed in 2.6.a; condition is still run-based. |
| Daredevil | Shoot across the MESA canyon with a Scout Cannon and land inside the target zone. | Disabled; use a normal expedition. | Patch 2.4.c says the unlock requirement should now work properly. The official post does not document a save migration rule for a failed attempt. | Use a fresh normal run, place the cannon carefully, land in the target zone, and note the version if the landing is visibly correct but no unlock appears. | Requirement fixed in 2.4.c; player report pending for new failures. |
| Aeronautics | Equip six total Balloons; a Balloon Bunch counts as three. Float to trigger the badge. All living players can receive it when eligible. | Disabled; use a normal expedition. | Patch 2.4.c fixed the case where another player in the lobby could satisfy the requirement for you. Confirm who equipped the balloons and who was alive. | Have the intended player equip the six balloons, float, and retest alone in a normal lobby; record other players' actions if it still misattributes. | Attribution fixed in 2.4.c; current misattribution is pending. |
Custom Run, save, and reconnect rules
The badge reference records that badges cannot be earned in Custom Expeditions. Treat that as a mode restriction, not as proof that a failed Custom Run corrupted your account. Start a normal expedition when testing a trigger and avoid adding a Custom Run result to your evidence log. The official patch notes support this page on the specific bug paths, but they do not publish a universal guarantee for every badge after a host migration.
Save state matters most for run-based conditions. Patch 2.6.a says host run-based achievement progress should save at a campfire and names Gourmand as an example. The same post warns that non-host saves do not contain the complete world state in every path. Keep the original host, note the campfire, and verify the condition again before moving the save to another player.
| Check | Why it matters | Evidence to record |
|---|---|---|
| Normal expedition | Custom Runs disable badges in the community reference. | Mode, difficulty, and whether a custom modifier was active |
| Host identity | Host and non-host save state are not identical in Patch 2.6.a. | Original host, current host, and campfire used |
| Living or escaped | Gourmand requires an alive escape; route badges can grant at an end campfire. | Who was alive, who was revived, and whether the run escaped |
| Exact trigger | Daredevil and Aeronautics require the landing or balloon state, not a nearby attempt. | Position, item count, and the action that should have granted the badge |
What to do after a failed unlock
First separate a condition failure from a grant failure. If a Citadel trap hit, an incomplete food list, a short balloon count, or a cannon landing outside the target zone occurred, the game may be behaving as designed. If the visible condition was met in a normal run and the badge did not appear, capture the version and state before attempting a workaround.
Do not use the 2.4.c Bookworm temporary cheat as a general fix. The official post says it is for players who already earned the badge and warns that it works for everyone. It is an exception to repair lost progress, not a way to skip the journal requirement. For other badges, use a fresh normal run and the official issue channel when a current reproduction remains.
- 1. Check mode Confirm this was a normal expedition, not a Custom Run.
- 2. Check the exact trigger Compare the action with the criterion and notes in the table.
- 3. Check state Record host, campfire, reconnect, revival, and whether the player escaped alive.
- 4. Retest once Use a fresh normal run and one intended actor where attribution matters.
- 5. Report the regression Include version, timestamp, trigger, screenshot, and no private room or account data.
Quick answers
PEAK achievements not unlocking FAQ
Are PEAK achievements disabled in Custom Run?
The community-maintained badge reference says badges cannot be earned in Custom Expeditions. Test a trigger in a normal expedition.
Why is Bookworm not unlocking?
Bookworm requires the Scoutmaster's final journal entry. Patch 2.4.c fixed reset and missing Scroll cases. If you already earned it before the bug, the official temporary salute grant can restore it; do not use that cheat as a first-time shortcut.
Why is Medieval History not unlocking after Citadel?
Avoid every trap hit, including arrow-trap activation with an item and Drowsy from a luggage trap. Petrified Rocks do not count. Patches 2.5.a and 2.6.b fix save and revival cases.
Why is Gourmand not unlocking?
Cook and eat Half-Coconut, Honeycomb, Yellow Winterberry, and Egg, then escape alive. Patch 2.6.a fixes host progress at a campfire, but non-host save state still has an official caveat.
How many balloons are needed for Aeronautics?
Six total Balloons are required, and a Balloon Bunch counts as three. Patch 2.4.c fixed another player in the lobby satisfying the requirement for the wrong player.
How do I trigger Daredevil?
Use a Scout Cannon to cross the Mesa canyon and land in the target zone. Patch 2.4.c says the unlock requirement should work properly; a current visible failure is a player report pending.
Sources and limits
How to read this page
Badge criteria come from the community-maintained PEAK Wiki Badges page, while version fixes come from official Steam posts. The two sources answer different questions: the wiki describes the trigger, and the patch note describes a fix or limitation. Recheck the in-game Accolades text after a future update.