The flashlight dies in the long corridor although enough batteries exist

Counting all the batteries in the level and comparing them with all the dark minutes can look fine while the player still gets stuck. Order and a limited charge decide it. This entry walks the route and says where the light fails and by how much.

Why this works

Adding up what is available hides when it is available. A pickup that comes after the dark stretch is useless for it, and one picked up at full charge is partly lost, so only walking the route in order shows the truth.

When not to use it

Not suited to open worlds where players choose their own route, or to games with a recharging light. Without a fixed path there is nothing to walk through, so give plenty of supply and test with real players instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 29 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 "The flashlight dies in the long corridor although enough batteries exist" (read_entry flashlight-battery-route-shortfall) 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