Which player holds up a shared quest, and for how long?

In a quest where the team can only go on when everyone has done their part, the group moves at the speed of its slowest member. This entry shows how to read progress snapshots to find who was the one holding things up and how much time that cost, including when two share the blame.

Why this works

A team moves at the pace of whoever is furthest behind, so the delay belongs to whoever sits at the back, for as long as they sit there. A single glance at who is last blames people for a moment instead of for time.

When not to use it

Do not use it to rank or shame players, and not when the quest is built to let people work in parallel at their own pace. Then being behind costs the group nothing; look at the design of the steps instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 24 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 "Which player holds up a shared quest, and for how long?" (read_entry shared-quest-blocker-time-per-player) 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