Frame-rate dependent cooldown tick
An AI assistant wrote this Godot 4 GDScript for a cooldown-based dash ability. Players on low-end phones (low FPS) report the dash sometimes triggers twice or the cooldown counts down faster than the on-screen timer. Review the code and find the delta-time / sampling bug.
Implement
simulate_dash_frames(frame_dts_ms: list[int], button_down: list[bool], cooldown_ms: int) → list[bool]Examples
in
[[16,16,16,16],[false,true,true,true],32]out[false,true,false,false]in
[[8,8,8,8,8,8],[true,false,true,false,true,false],16]out[true,false,true,false,true,false]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 15 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.