The special ending never plays because an earlier rule always wins

Endings are picked from a list, top to bottom, first match wins. Put a broad rule above a narrow one and the narrow one is dead; leave a gap and some players match nothing. This entry finds dead rules, contradictions and uncovered situations.

Why this works

When a list is read from the top and the first match wins, a rule can only be judged next to the rules above it. A broad rule hides every narrower one below it, so the order matters as much as the conditions.

When not to use it

If your endings come from points or scores, or the story picks the ending by a plain count, there is no list to shadow anything. Then check the ranges of the score for gaps and overlaps instead, and keep this for rule lists.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 2 common mistakes and the fix
• 36 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "The special ending never plays because an earlier rule always wins" (read_entry ending-order-hides-the-special-ending) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP