RUNAWAYS officially tracks three state crossings before Mexico: Kansas Checkpoint, Oklahoma Checkpoint, and Texas Checkpoint. Each badge description says you crossed that state line. Current walkthroughs place the checkpoints in that order and report police pressure around progression, but the official badges do not publish gate timing or pursuit formulas.
Prepare before Kansas
Complete a short driving loop and refuel through a current station. Clear the vehicle entry, point the camera down the road, and decide the first turn after the gate. Kansas is the first official state checkpoint in current community routes.
Approach with enough braking distance to handle another vehicle or changed barrier. Cross once and wait for visible feedback only if it is safe. If police appear, leave the gate area rather than reversing into it.
Cross Oklahoma cleanly
Use signs to confirm Oklahoma rather than assuming every checkpoint-looking structure is the next state. Check fuel before the approach. A wrong turn between Kansas and Oklahoma is less damaging when the tank has a recovery margin.
Maintain a straight line through the trigger and choose the road out before looking backward. The official badge proves the state-line event, not a required speed or vehicle.
Reach Texas
Texas is the last official state checkpoint before the Mexico objective in current routes. Treat it as a separate driving task: align, brake, cross, and recover. Do not let the closeness of the goal encourage a full-speed collision.
After crossing, confirm the next live border direction and fuel state. If pursuing units remain in sight, use solid road turns and keep moving toward Mexico.
Confirm checkpoint credit
Watch for normal badge or game feedback. Roblox award delivery can be delayed. Check the official badge ownership after the run. If a state badge is missing, verify that the correct trigger was crossed and try again in a fresh server before claiming a hidden requirement.
The badges do not say all three must happen in one session. Current route planning naturally connects them, but do not add an unsupported session rule. Likewise, no official condition requires a paid vehicle.
Checkpoint reference
Troubleshoot gate problems
If the vehicle catches, stop forcing forward input. Reverse, straighten, and take a wider angle. If a barrier appears closed, read the current prompt and state rather than clipping around it. Check whether another player or server event is affecting the gate.
If route signage does not match a guide, follow the live build. Rejoin a fresh server to distinguish a map update from a one-server state. Never use teleport or noclip scripts; they can bypass the intended trigger and threaten the account.
Practice one gate at a time
On the first route-learning session, treat reaching Kansas as a success even if Mexico is not attempted. Repeat the approach until the sign, braking point, opening, trigger, and departure road are recognizable. Then extend to Oklahoma and finally Texas. This reduces the amount of new road learned under one fuel and police state.
Record the vehicle and device used. A wide truck and a fast car may need different braking points, while touch steering may benefit from a straighter camera angle. The official crossing condition remains the same even when the practical approach differs.
Sources and confidence
All three names and crossing conditions are Official. Order and police response are Community corroborated. Exact road geometry, trigger width, pursuit timing, and fuel needs remain Needs in-game testing.
Use the current state sign as the final navigation authority.