The working codes are FOREVER and INDEX—both grant freebies including potions and wins. Redeem them immediately via the bluebird button on the left side of your screen. Everything else in this guide is about not wasting what those codes give you.
Most players burn their code rewards within ten minutes because they treat potions like emergency rations rather than strategic multipliers. That's the assumption worth challenging: you don't "use" potions, you schedule them. A speed potion active during a rebirth run compounds your base gain permanently. The same potion used casually while chatting in the lobby? Gone. The tutorial never explains this timing asymmetry, and it's the single biggest waste of early progression.
First-Hour Priorities: The Sequence That Actually Sticks
Your first hour breaks into three phases, and the order matters more than the actions themselves.
Phase 1 (0–10 minutes): Code redemption and inventory audit
Redeem FOREVER and INDEX. Check what you actually received—potions vary in duration and multiplier, wins are currency for hatching Cores. Don't hatch anything yet. The temptation to immediately roll for a "powerful Core" is strong, but early Cores have low base stats and you'll rebirth soon enough to invalidate them. Wins spent on hatching before your first rebirth are wins thrown away.
Phase 2 (10–40 minutes): Baseline speed run without potions
Run the track. Learn the layout. Note where you hit speed walls—literal or figurative points where your current max speed caps. This establishes your unboosted baseline. The game tracks this implicitly through your rebirth multiplier calculation, but never shows you the number directly. Your goal: know your rough speed before you ever pop a potion.
Phase 3 (40–60 minutes): Stacked potion deployment
Now use one potion. Not two. Not three. One. Run until it expires. Note the speed delta. This gives you a clean A/B test of potion value versus your baseline. Many players stack multiple potions immediately, muddying what each contributes. You lose diagnostic information and often waste overlapping durations.
The hidden variable here: potion timers run in real-time, not play-time. Alt-tabbing to check a code list? Timer's burning. Stuck on a loading screen? Timer's burning. The tutorial implies these are buffs you "have active while playing." They're not. They're buffs you have active while the universe continues existing.

What the Tutorial Under-Explains: Rebirth Math and Core Timing
Rebirth resets your speed to zero but multiplies your future gain rate. The tutorial frames this as "help you gain speed at an even quicker rate on your next attempt." What's unsaid: the multiplier applies to base speed gain, not total speed. This creates a compounding structure where early rebirths have outsized impact, but each subsequent rebirth faces diminishing returns relative to the time invested.
| Rebirth Timing | Speed Reset | Multiplier Applied To | Strategic Implication |
|---|---|---|---|
| Before first potion use | Zero | Base gain only | Wasted—no stacked multiplier to compound |
| During active potion | Zero | Base gain × potion multiplier | Optimal—potion benefits permanently baked into future runs |
| After potion expires | Zero | Base gain only | Suboptimal—you ran the potion for temporary benefit only |
The rebirth button glows when available. Ignore the glow. Rebirth when your potion timer has the most remaining duration, not when the game suggests it. This usually means rebirthing immediately after using a fresh potion, not at the end of a long session when you're already fatigued.
Core hatching follows similar hidden logic. Cores provide "special assistance"—typically passive speed boosts or auto-run features. But Cores have rarity tiers, and early-game currency (wins) generates common-tier Cores at rates that make rare-tier acquisition statistically painful. The trade-off: wins spent on Cores are wins not spent on future rebirth acceleration or potion purchases. If you hatch ten commons to get one uncommon, you've delayed your second rebirth by a factor that compounds across your entire session.
Decision shortcut: Hatch exactly one Core in your first hour. Any rarity. Test its mechanic. Then stop. The marginal utility of additional early Cores is near-zero compared to rebirth timing optimization.

Time and Currency Traps: Three Mistakes That Kill Momentum
Mistake 1: Chasing expired codes
The expired list is long—WORLD4, AMETHYST, DARKMERCHANT, EASTER, BUNNY, QUEST, and dozens more. Players find these on old forum posts or video descriptions, try them, get nothing, and keep trying. Each attempt costs maybe five seconds. Across a session, this accumulates. More subtly, it trains a scavenger mentality: you're playing the code-hunting metagame instead of the speed-running game. Check one reliable source (the current working list), redeem what's live, move on.
Mistake 2: Saving potions for "when I really need them"
This is loss-aversion bias in game form. Potions early compound through rebirth multipliers. Potions late add linearly to already-large numbers. A 2× potion at 100 speed gives +100. The same potion at 10,000 speed gives +10,000—but your rebirth multiplier was already built without it. The permanent gain from early use dwarfs the absolute number from late use.
Mistake 3: Ignoring the social multiplier
The game doesn't emphasize this, but running near other players often triggers proximity speed bonuses or competitive draft effects. The track isn't purely solo time-trial. Positioning matters. Most players hug the inside line for shortest distance; the optimal line sometimes drifts wider to maintain drafting position behind faster runners. This is counterintuitive and never tutorialized. Test it: run the same segment three times—solo, behind someone slightly faster, and leading. Measure your speed at fixed checkpoints. The drafting benefit, if present in your server version, typically exceeds the geometric shortcut of inside lines on longer straights.

The Next Three Decisions That Shape Your Run
After your first hour, you're at a branch point. These three decisions, made in sequence, determine whether you plateau or accelerate:
Decision 1: When to second-rebirth
The glow will tempt you. Resist until you have a fresh potion active and at least thirty minutes of uninterrupted play ahead. The second rebirth's multiplier stacks on the first. Interrupting this run wastes the compounding.
Decision 2: Core specialization versus diversity
By now you have 2–3 Cores. Do you level one high or spread across several? The asymmetry: specialized Cores unlock threshold abilities at higher levels that often include passive potion-like effects. Diversified Cores give more frequent but smaller bonuses. For sustained progression, specialization wins. For leaderboard pushes where specific mechanics matter, diversity can counter particular track segments. Most players should specialize until they hit their first Core's threshold ability, then reassess.
Decision 3: Wins allocation—hoard versus spend
Wins accumulate from codes, running, and achievements. The temptation to spend them as they arrive is strong. Better: set a wins floor (say, the cost of your next planned rebirth acceleration) and only spend above that floor. This prevents the "I was saving for X but spent on Y" drift that kills long-term plans.

The One Thing to Do Differently
Stop treating codes as bonus gifts and start treating them as timed infrastructure. FOREVER and INDEX aren't "free stuff"—they're a narrow window of multiplied potential that closes as your session progresses. Redeem them, schedule their benefits against rebirth timing, and ignore everything else until that compounding is locked in. Speed in this game isn't about running fast. It's about running at the right moment.



