The first cactus passes. The second approaches while the dinosaur is still airborne. You press again. When the game stops, the immediate thought is that you needed faster fingers.
The problem may have begun in the previous jump.
Our T-Rex Runner uses the familiar rhythm of pressing, releasing, and landing. Going farther requires time to land before the next takeoff, not only choosing when to jump.
Compare a tap with a hold
On desktop, Space or Up jumps. Phones use touch-down and release. The current jump logic processes release after an internal height condition is met, ending continued ascent. Short and longer presses can therefore feel different; release does not mean an instant landing.
At the slower beginning, observe only this. Compare a short tap with a slightly longer hold over low obstacles, watching landing position instead of score.
A high jump may look safe while keeping you airborne longer. Readiness for the next group depends on how this jump ends.
Look earlier without pressing earlier
Watching only the dinosaur's feet leaves little reaction time. Look toward the right to distinguish a low cactus, a wider group, or flying obstacles at different heights.
Seeing sooner is not the same as jumping sooner. An early jump can land before the obstacle. Practice noticing, waiting, then acting at a useful distance.
No fixed distance suits every speed, device, and obstacle sequence. A rule measured in screen centimeters ignores zoom, refresh rate, and touch delay.
Sort three failures from a similar stage into late takeoff or unsuitable landing. They call for different adjustments.
Desktop has another easily missed action
In a Reddit Arduino-project discussion, some readers discover ducking only after seeing it demonstrated. Many people first learn this game as “press Space.”
On our desktop version, Down ducks while grounded and triggers faster descent in the air; releasing restores the relevant state. Learn it with room to spare, then judge which flying obstacles can be passed underneath.
“Bird means duck” is not universal. Height relative to the dinosaur still matters.
The phone interface has no separate duck button. Do not copy that desktop advice into a phone-control instruction. Practice the jump, release, and landing actions actually available there.
Choose one goal for the next round
If the second obstacle group repeatedly catches you, practice clearing the first while preparing to land for the next. If single cacti cause trouble, inspect takeoff timing rather than changing everything.
Set the score aside briefly. It records distance already traveled, not what to do this second. Watch the beginning and end of the next action.
After repeated failures, take a break. Repeating an error many times does not necessarily diagnose it faster. Short, clear practice can suit a game that restarts so easily.
This guide explains current input mechanics and practice ideas. It promises no high score and does not treat source inspection as a real-phone latency test.
When the next game stops, think back one jump: were you still keeping yourself airborne when you most needed to land?