My shooter feels sluggish and I want to know if the delay is real

Delay between pressing a button and seeing the hero act is felt long before it is measured. This helper takes the moments of your presses and the moments of the first visible reaction, and tells your AI how long the wait was, how it varies and how many presses got no answer.

Why this works

Players notice the worst delays, not the average, so the report gives the median and a high percentile. Pairing each press only with a reaction before the next press stops one reaction from being counted twice.

When not to use it

This measures the game's own delay only up to what it draws. Delay added by the screen or the controller cannot be seen from inside the game, so compare with another game on the same device before blaming the code.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 27 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 "My shooter feels sluggish and I want to know if the delay is real" (read_entry work-act-measure-button-to-screen-delay) 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