Decide when a team with shared lives has really lost

With a pool of lives shared by the whole team, the end of the game is not simply "lives are zero". Everyone can lie on the ground at the same moment while lives remain, or the last life can go while a friend is still standing. Here is the rule for when the game is over and who comes back.

Why this works

A shared pool means the team lives or dies together, so the game should end only when nobody is left who could still act. Looking at who can still play, not at the count of lives, is what matches how it feels.

When not to use it

Skip it when each person should carry their own risk, such as in a game where one player's careless run should not cost the others. Give each player separate lives and let them fail alone.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 29 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Decide when a team with shared lives has really lost" (read_entry coop-shared-lives-and-team-wipe) 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