Color Road gates look like a reflex test, and the code agrees only partly. Every gate follows a spawn distribution, a passing rule, and a color switch schedule you can plan against. The players who pass 50 gates do the same arithmetic as you can, just faster.
What a gate is, mechanically
Each obstacle is a colored ball in one of three lanes. A gate checks color, then position. Inside the collision window, which spans road distance 40 to minus 20, the engine compares the gate color to your ball color.
1. Same color, same lane. The gate collects. Your score rises by one.
2. Different color, same lane. The run ends on contact.
3. Any color, different lane. The gate passes you. Nothing happens.
The third rule is the one players miss. Dodging your own color costs you a point but never a life. When the road offers no safe collect, dodge without guilt.
The window itself is generous in depth, about 60 units of road, while your ball sits at a fixed 22 pixel radius. You do not need pixel timing. You need to be in the right lane before the gate arrives, which is a planning problem.
The spawn odds you can rely on
At spawn time the engine rolls one gate against your current color. The roll gives 40 percent matching your color and 60 percent spread over the other three colors, 20 percent each. The lane is uniform over three.
Three consequences follow.
1. Any single gate has a 13 percent chance of being both your color and in your lane, roughly one collect opportunity per eight gates if you never move.
2. Six of ten gates threaten you if you hold a lane, so holding a lane forever is a losing strategy by construction.
3. Gates spawned before a color switch carry the old color assumption, so the gate right after a switch is more likely to be a mismatch for you than usual.
The color switch every eight collects
Every eighth collected obstacle changes your ball to one of the three colors you do not currently hold. The engine never repeats your color on a switch. The HUD marks your color with a dot labeled YOUR COLOR, and the switch plays a distinct power up sound.
Count your collects in cycles of eight. The exact rule to apply is the following.
1. Collects one through seven. Play the gates as they come.
2. On the seventh collect, stop trusting the gate colors you see ahead, because one more collect re-rolls your color and those gates were spawned against your old one.
3. After the switch, glance at the HUD dot before committing to the next collect. Reading your ball's own color off the road is the common error after a switch.
Speed changes the math, not the rules
Speed starts at 280 road units per second and rises by 3 per collect, capped at 800. The cap is reached at 174 collected gates. The road ahead spans 1200 units, so your visible warning time shrinks from about 4.3 seconds per gate at the start to 1.5 seconds at the cap.
Gates fade in at 960 units, so the farthest gate always appears faint. Use the faint ones for lane planning and the near ones for commitment. Gap spacing runs 180 to 280 units, so at start speed a gate arrives every 0.6 to 1.0 seconds. At cap speed, every 0.2 to 0.4 seconds, which is faster than a read of both color and lane. Past roughly 100 collected gates you are playing from pattern memory of the switch count, with the HUD dot as your only check.
One input note from the code. Lane changes are instant in game logic, and only the drawn position eases toward the lane. A swipe over 30 pixels or a tap on the correct half of the screen changes your lane immediately, so visual lag on screen is never a gameplay delay.
Deterministic passing routine
Apply this loop to every gate, in order.
1. Read the gate color first, lane second.
2. If the gate color matches yours and the lane is reachable, move to collect.
3. If the gate color differs and it is in your lane, move to either other lane, and prefer the lane of the next gate if that gate is your color.
4. After every collect, update your count modulo eight.
5. On a switch, confirm the new color on the HUD before the next collect attempt.
Step 3 is where runs survive. Choosing between the two escape lanes is the only real decision in the game, and the correct choice is always the one that sets up the next gate.
Honest limits of this approach
Scoring raises speed by 3 per point, so every collect shortens your future decision window. The distribution is random per gate, and runs exist where several consecutive gates miss your lane entirely. The switch re-roll also means a streak of bad gate colors right after a switch is normal variance, and no routine prevents it. Players who report scores above 150 at cap speed are reacting to lane before confirming color, and accept occasional deaths from color misreads.
Checklist before your next run
1. Keep your eyes one gate ahead, never on your ball.
2. Count collects in eights and expect the switch on the eighth.
3. Confirm the HUD dot after every switch.
4. Escape mismatches toward the lane of the next matching gate.
5. Dodge your own color when no collect is safe, it costs a point only.
6. Treat faint distant gates as planning data, near gates as commitments.
What is your score at the moment the switch count first trips you up, typically somewhere past 40 collected? That number separates reading speed from planning speed and tells you which to train. Test every rule here at https://webrecast.com/en/color-road, ideally with the engine source open beside the game. If your collected counts disagree with the switch schedule, send the run length and the gate sequence.
