Tell the AI how smooth the game really is, not just its average speed

A game can report a healthy average and still hitch every few seconds while the player runs through the forest. This entry gives the AI a short report from a recording of frame times that shows the average, the bad moments and how many spikes there were.

Why this works

A smooth game is judged by its worst moments, because a player does not feel an average, only a stumble. Looking at the slowest few frames, and at how often a frame is far above normal, shows the stutter that a single average number hides.

When not to use it

It tells you that the stutter exists, not why. And a short recording may miss rare freezes, so for those, record longer and in the situation where players complain, before you trust a clean report.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Tell the AI how smooth the game really is, not just its average speed" (read_entry average-fps-hides-the-stutter) 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