Cross-game strategy
Run Lessons
Run Lessons are strategy articles for the problems that show up across many one-more-run games: strong starts that collapse, builds that get worse after too many upgrades, patch notes that quietly break old advice, bad-run recovery, and boss prep that started earlier than the boss room.
How to use this section
Start with the failure pattern, then pick the game guide.
These pages do not replace game-specific guides. They help you name the problem first, then jump into the right hub: Rotwood for hunt timing, Everything is Crab for mutation routes, Rune Dice for board control, Vampire Crawlers for build engines, Pandora's Toybox for faith economy, or Romestead for settlement bottlenecks.
- Read the lesson that matches the way the last run failed.
- Use the decision table to identify the missing layer.
- Open the linked game guide that fixes that layer.
- Change one habit before chasing a full new build.
Start with these Run Lessons
Why Roguelite Runs Collapse After a Strong Start
Learn why a run can look ahead early and still die later because sustain, economy, route timing, boss prep, or patch context fell behind.
Build disciplineThe Beginner Build Trap
Use build ideas by situation, not rarity or popularity, and stop adding upgrades that solve different problems.
Patch readingHow to Read Patch Notes Before Copying Old Builds
Check what a patch changed before trusting an old build, route, farming loop, or boss-prep habit.
Run recoveryHow to Recover a Bad Run Before You Restart
Turn weak starts into safer route goals, build repair, unlock progress, or boss practice before quitting.
Boss prepBoss Prep Is Usually a Route Problem
Fix sustain, route spending, punish windows, and role clarity before assuming more damage is the answer.
Game selectionHow to Choose an Indie Roguelite Worth Learning
Check decision clarity, failure feedback, update stability, build variety, and session friction before committing.
Which lesson first?