Find stretches where the story goes silent or the player cannot act

Action games lose people in two ways: ten minutes of shooting without a hint of plot, and a cutscene run that takes the controller away for too long. Here is how your AI lays out a route as a list of beats and flags each stretch that breaks a limit, with the beat numbers to fix.

Why this works

Players do not feel the average, they feel the longest dull stretch. Measuring runs of beats with no plot, and separately runs with no control, shows the places where attention drops, and the two kinds need different fixes.

When not to use it

Skip it when the quiet is the design, such as a long, tense stealth chase or a calm walk meant to bring relief. Judge those by playtesting; a measured limit will only tell you to break something that is working.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 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 "Find stretches where the story goes silent or the player cannot act" (read_entry story-pacing-long-stretches-without-story-or-input) 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