GET YOUR BEARINGS
Plan your next The Horror at Highrook session
Our independent guide breaks down The Horror at Highrook’s core systems, helping you see how narrative, crafting, and survival intertwine. By examining each documented element, you can form a clear plan without relying on undocumented shortcuts or assumptions.
01 / THE GUIDE
Skill Comparison
List each investigator’s abilities side by side. Identify which challenges they naturally mitigate, then choose primary and secondary characters for early chapters based on those strengths.
- Compare each investigator’s skill set early to see which challenges they naturally mitigate.
- Watch dialogue for hints of hidden ambitions to deepen narrative context.
02 / THE GUIDE
Crafting Log
Keep a simple log of successful recipes, noting the components used and the resulting effect. Compare outcomes to spot the most versatile tools for both combat and survival.
- Experiment with varied combinations to uncover unexpected rites.
- Keep your own record of successful recipes for future reference.

03 / THE GUIDE
Hazard Mapping
Sketch a brief map of each chapter’s known hazards—earthquakes, incursions, madness triggers. Use this map to allocate resources before entering new areas.
- Note recurring environmental cues that may hint at upcoming hazards.
- Try out newly acquired rites as the story progresses to see what they unlock.
04 / THE GUIDE
Lore Correlation
Cross‑reference collected notes with in‑game events. Highlight recurring names or symbols that may foreshadow future plot points or hidden locations.
- Prioritize reading discovered documents to fully grasp the narrative.
- Cross‑reference letters with in‑game events for hidden story links.
05 / THE GUIDE
Survival Rhythm
Track your party’s hunger, injury, madness, and disease over time. Look for patterns where certain activities raise risk, then adjust pacing to keep the team stable.
- Balance exploration with periods of rest to mitigate madness buildup.
- Monitor injury status after hazardous events to avoid cascading failures.




