Tools

Evil School Wiki Tools

Interactive checklists and trackers built for completionists hunting all demo and full-game endings.

Last updated:

Tools Hub

Evil School’s 42 endings and 100+ branches demand more than memory. This tools hub hosts interactive helpers that persist your progress in the browser — no account required — so you can focus on story beats instead of spreadsheets.

Tools complement guides; they do not replace them. Pair every tracker with narrative context from Endings Hub, Branching Paths, and Choices and Consequences.

Available tools

Demo Ending Checklist

The flagship tool for players working through the February 2026 demo. Chapter 1 is fully playable; later chapters appear as under-two-minute previews, but several outcomes still register in demo saves. The checklist lets you mark:

  • Chapter 1 endings you have confirmed
  • Preview-scene outcomes glimpsed in Chapters 2–6
  • Failed trials versus successful hunts
  • Clue combinations you have tried

Open the page and use the embedded <DemoEndingChecklist /> widget — progress saves locally until you clear browser data.

Planned tools (post-launch)

After August 14, 2026, we intend to add:

  • Full Ending Matrix — requirements for all 42 routes
  • Blood List Tracker — trial order optimizer for Li Manting, Zhang Yao, and secondary targets
  • Clue Board — visual map linking evidence to Clue Hunting nodes

These depend on verified full-game data. Demo tools ship first because that is what players need today.

How tools fit your playthrough

  1. Start a demo run following Getting Started.
  2. Open Demo Ending Checklist in a second monitor or phone browser.
  3. When an ending triggers, mark it immediately — some routes differ only by a single mid-scene prompt.
  4. Cross-check unfamiliar flags in Demo Endings before replaying.

Speedrunners can ignore trackers; narrative completionists should treat them as essential. Tools never spoil unseen CG — they only record what you have already witnessed.

Technical notes

Wiki tools run client-side in static pages generated by Astro. They respect the same locale paths as the rest of the site — English at root, /fr/, /de/, and /es/ prefixes for translations once localized UI ships. If a checklist fails to load, ensure JavaScript is enabled and retry after a hard refresh.

For release news affecting tool data (demo patches, ending renames), watch Updates Hub and Demo Next Fest.

Tool design philosophy

Static wiki tools prioritize privacy and speed — no login walls, no analytics on your ending history. When the full-game matrix launches, it will reuse the same localStorage pattern so completionists can export JSON backups manually if browsers reset.

Accessibility

Checklist controls target keyboard navigation and high-contrast labels once the DemoEndingChecklist component ships in production builds. Report UI issues via Official Links Hub community channels so we can patch the widget without touching your saved marks.

FAQ

Frequently Asked Questions

Quick answers to the most common questions.

Does the Demo Ending Checklist spoil endings?

It lists ending names only after you mark them. Titles stay collapsed until you confirm witnessing the outcome yourself.

Will my checklist sync across devices?

Not currently. Progress uses browser local storage on the device where you mark entries.

Are tools available in the demo executable?

No. These are web tools on the wiki, designed for use alongside the Steam demo or full game.

When will full-game tracking arrive?

After the August 2026 launch once we verify all 42 ending conditions. Follow Updates for announcements.