The party leader goes offline and the group falls apart or fights over the lead

A saved group needs to know who is in it even when most are away, and who leads when the leader's connection fails for a minute or for a week. Here is a rule that is calm about short drops, hands over once, and does not swing back and forth.

Why this works

Presence is a fact of the moment, not something to keep, and a short absence is normally a hiccup. Waiting a little before handing over avoids needless changes, and a fixed order of succession means nobody argues about who is next.

When not to use it

Do not hand over the lead on its own in a group where the leader holds something others must agree to, such as a guild with votes or a paid owner. Let members vote, or keep the lead with the owner until they choose.

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
• 15 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 party leader goes offline and the group falls apart or fights over the lead" (read_entry party-leader-goes-offline) 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