Decide the route when two characters end on equal affection

Sooner or later two characters finish with the same score, and a story that picks one by accident feels broken. Here is a fair rule for ties, for too-low scores, and for a clear winner, and how to make each case visible in a test.

Why this works

A tie should be settled by something the player did, not by the order in a list. Looking back at who reached the final score first rewards recent attention, and a fixed order is only the last resort so the result is always the same.

When not to use it

Wrong when you want the player to decide a tie themselves, which can be a lovely scene of its own. Then offer a choice at the crossroads instead of settling it quietly behind the scenes.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 2 common mistakes and the fix
• A diagram of every state
• 27 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 "Decide the route when two characters end on equal affection" (read_entry two-heroines-tied-on-affection) 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