Puzzle database
Event Room Decisions
Puzzle and event decision framework
The puzzle hub starts with event-room decisions because secrets, risks, and one-off choices are easier to index than a complete spoiler database.
Low by default
Decision checklist before taking a risky option
Editorial rule
Puzzle and event pages should label spoiler depth clearly. The first version should help players decide risk without dumping every secret result above the fold. A good event page starts with the current decision state: HP, deck strength, potion belt, route pressure, and whether the deck still needs card rewards.
Decision checklist
Before taking an event option, compare the downside against the next fight window. A strong reward is not free if it costs the HP, card quality, or potion buffer needed to survive the route. This page should grow into a spoiler-controlled table as event data is verified.
- Take risk when the deck is already stable enough to absorb the downside.
- Avoid greedy event choices when the next elite or boss is already dangerous.
- Link event outcomes to collectibles, unlocks, and boss-prep pages.
Common mistake
The common mistake is rating an event by its best possible outcome instead of the current run state. Exact event names, costs, rewards, and hidden outcomes are needs verification, so the page should teach spoiler-light risk evaluation before publishing a full answer table.
Evidence to collect next
The next event-room pass should capture the pre-choice screen, HP, gold, relics, potion belt, deck weakness, route pressure, patch version, and result. A post-reward screenshot is not enough because it hides the risk calculation that made the decision correct or greedy.