PEAK Citadel Guide: Traps, Medieval History and Save State

What the official updates establish about Citadel

The Final Ascent update introduced Citadel alongside Gloom and other late-route systems. Patch 2.01.a later improved Citadel level generation to prevent floating obstacles, and Patch 2.03.a placed a new batch of Gloom/Citadel maps into the daily rotation while Caldera and The Kiln were being prepared. Patch 2.04.a brought Caldera and The Kiln back, so Citadel should be read as part of a changing pool rather than a permanent daily endpoint.

The official posts are strong evidence for release and fixes, but they do not provide a complete trap map or a guaranteed route order. Use the image and map page as context, then read the trap state that the current session actually presents. This keeps a Medieval History attempt reproducible instead of based on an old screenshot.

How to plan a Medieval History run

The badge criterion is not simply “reach the Citadel.” The community reference says you must climb past it without being hit by traps. Petrified Rocks do not count as a trap hit. An arrow trap activated with an item in hand counts even if you take no damage, and Drowsy from a luggage trap counts as being hit. Those details make a cautious route and a cautious interaction equally important.

Before the run, tell the team that a well-intentioned item interaction can invalidate the attempt. Keep the player seeking the badge in a clear position, call out trap triggers before interacting, and do not use a saved run as evidence until the host and save path are known. Patch 2.5.a and 2.6.b address named state bugs, not every possible accidental trigger.

Citadel saves, reconnects, and revives

A Citadel badge failure can be a condition failure or a state failure. Patch 2.5.a fixed a case where loading a Citadel campfire save prevented Medieval History. Patch 2.6.a improved campfire tracking for luggage and nearby objects and fixed host run-based progress at a campfire. Patch 2.6.b fixed a case where reviving in Gloom or Citadel could prevent Medieval History. Keep those paths separate when you report a result.

The safest retest keeps the original host, uses a normal expedition, and records whether the player was alive, dead, or revived when the Citadel was reached. If a non-host hosts from a save, the 2.6.a note says item spawning may still be a little weird. That does not prove the badge failed for the same reason, but it is essential context.

• Host Keep the original host when loading a Citadel save.
• Mode Use a normal expedition because Custom Runs disable badges in the community reference.
• Trap state Record every trigger or Drowsy event, even when no damage appears.
• Revive state Record whether the badge player revived in Gloom or Citadel.
• Version Use the current patch and attach the official post that matches the path.

Citadel run checklist

The checklist turns a difficult badge attempt into a small evidence trail. It cannot reveal a hidden layout or guarantee a reward, but it makes a failed run diagnosable. When a later official note changes a condition, the dated record also tells you which advice needs an update.

• 1. Confirm the route Check whether Citadel is actually in the current map sequence.
• 2. Brief the group Explain that trap activation can count even without damage.
• 3. Mark safe pauses Agree where the badge player can stop without forcing a risky interaction.
• 4. Protect the save Keep the original host and avoid migrating a loaded run.
• 5. Record the result Write the trap, revive, save, version, and whether the badge appeared.