Cube Dash feels random until you read the generator. This build assembles each level from twelve fixed obstacle patterns chosen by a deterministic formula. The cube, the gravity, and the jump arc are equally fixed. Every number below comes straight from the engine, and the strategy follows from arithmetic.
The pattern formula is deterministic
Each level is built in sections 300 to 500 px long. The pattern for each section is computed as the level index times 1000 plus the section index times 7, all modulo 12. Same level, same section number, same pattern.
Level 1 therefore opens with this repeating twelve section cycle.
1. Section 0, spike row, one spike at difficulty zero.
2. Section 1, moving platform over a 140 px gap.
3. Section 2, gap of 100 px plus difficulty scaling.
4. Section 3, spike, block, spike combo.
5. Section 4, triple spike.
6. Section 5, spike row of two, plus a gravity portal once difficulty passes 0.3.
7. Sections 6 to 11, staircase, block jump, ceiling spikes, gap plus spikes, speed portal plus block, combo again.
The cycle then repeats because 7 times 12 is 84, which is 0 modulo 12. Level 2 starts at pattern 4 and level 3 at pattern 8, so the three levels rotate the same catalog. One caveat is honest and important. Section length is 300 plus a random 200 px, so the spacing between the same hazards shifts between runs. Memorize the order, read the distances live.
Jump arc numbers you can build on
Gravity is 2200 px per second squared and the jump velocity is 750 px per second. Three results follow.
1. Air time is about 0.68 seconds per jump.
2. Peak height is about 128 px above the takeoff surface.
3. At the base speed of 280 px per second, one jump covers about 191 px of ground.
Check these against the obstacle catalog. A triple spike spans 130 px, three spikes at 45 px spacing plus the 40 px spike width, so the cube must stay airborne for 170 px including its own width. That fits inside the 191 px jump arc. A first gap of 100 px needs 140 px of flight and is comfortable.
Late gaps are different. Gap width scales to 100 plus 80 times difficulty, so it maxes at 180 px, which needs 220 px of flight. The base jump is too short. The saving grace is the distance ramp.
The speed ramp changes every late jump
The engine recalculates speed each frame as 280 times the portal multiplier times 1 plus distance times 0.00003. At the halfway point of the 12000 px level the factor is 1.18, so speed reaches about 330 px per second and a jump covers about 225 px. At the level end the factor is 1.36.
The practical rule is fixed.
1. Before roughly 4000 px, treat 191 px as your maximum clearing distance.
2. After 6000 px, treat 225 px as the working number and expect gaps up to 180 px.
3. After any speed portal, recompute, because the multiplier stacks on top of the ramp.
Portals and what they cost you
The speed portal adds 0.3 to the speed multiplier, capped at 1.8, and first appears in the level 1 cycle at section 10, once difficulty passes 0.2. At the cap plus the end-of-level ramp, speed approaches 680 px per second and a single jump covers more than 460 px. Chained jumps at that speed overshoot landing zones, so tap later than feels natural.
The gravity portal appears in the level 1 cycle at section 11, once difficulty passes 0.3. It inverts gravity and sets the fall velocity to 400 px per second toward the new floor at y = 120. Jump timing inverts with it, and ceiling spikes become the ground hazards.
Hold the input instead of tapping
The engine checks two conditions every frame. A buffered tap survives one update tick at most, but a held input triggers a jump on the first frame the cube is grounded. For staircase and block sequences, press and hold through the sequence and let the engine time the jumps. Release only before sections where an early jump kills.
Death handling is also fixed. A keyboard restart needs 0.3 seconds of death screen, a click needs 0.5. Practice mode drops a checkpoint every three sections and restarts you there, so use it to learn sections 4 and beyond before attempting a full run.
Collision is more forgiving than it looks
Every obstacle test shrinks the cube hitbox by 6 px on each side, from 40 px down to 28 px. Spikes get a second triangle test with a kill half width of 14 px plus 12 px of tolerance at the base, narrowing toward the tip. Grazing the side of a spike at peak height often survives. Trust the near miss and keep the line.
Cube Dash honest downsides
Moving platforms oscillate on a random phase, so the same section can demand different jump timing across attempts. Section length randomness means a memorized rhythm can still clip a spike placed 80 px later than your last run. The speed ramp also makes the final third of each level objectively harder than any practice data from the first third.
Before you jump checklist
- [ ] Current section pattern identified against the twelve section cycle.
- [ ] Distance read from the percentage, ramp factor applied to jump length.
- [ ] Gap width estimated as 100 to 180 px before committing to a long hop.
- [ ] Input held through block and staircase sequences.
- [ ] Portal positions recalled for the current section number.
- [ ] After a speed portal, landing markers shifted later by the new speed.
Open the [Cube Dash game](https://webrecast.com/en/geometry-dash) and test the twelve section cycle against your next dozen deaths. If your death spots do not line up with the pattern order above, send the level, the section number, and the obstacle you hit. Engine-verified corrections are welcome.
