Rocket Rush officially supports missile evolution. The Evolution badge says: “Evolve your missile for the first time; tiered versions for later evolutions.” This confirms a first evolution and later tiers. It does not reveal the menu, unlock, currency, materials, tier names, stat gains, appearance changes, refund rules, or best order.
The safe method is to follow the current game’s visible evolution interface, record the state before spending, read the preview, complete one supported change, and confirm both the result and badge.
Find the current evolution interface
Look for an evolution, upgrade, missile, progression, or loadout control that is actually shown by the current game. Use the root experience created by VOXELIFIED and verify Place ID 131234943387594 before following any menu directions.
If the option is locked, read the exact requirement. Record whether it names a world completion, resource, level, achievement, or another condition. Do not replace a blank or hidden requirement with a cost from Rocket Rush Simulator or another vehicle game.
The Evolution badge alone does not prove when the system becomes available. If no interface appears, continue normal course progression and recheck after explicit live feedback.
Record the state before evolving
Capture the missile’s visible name, tier, appearance, displayed attributes, equipped effect, and every resource balance shown by the interface. Unknown fields should stay unknown. A screenshot or written record protects you from attributing an unrelated run improvement to evolution.
Read the confirmation screen. Note the exact cost, whether it is consumed, the previewed result, and any warning about permanence or reset. Cancel if the consequence is unclear and the resource appears limited.
Do not assume that a more dramatic appearance means a specific speed, damage, fuel, handling, or grapple benefit. Only the live attribute or repeated controlled comparison can support that relationship.
Complete the first evolution
Compare later tiers
The badge wording mentions tiered versions for later evolutions, but no public tier list is available. Build a record for each visible tier: exact name, requirement, cost, displayed change, date, and current game version.
Compare one familiar course segment before and after. Keep camera, bindings, route, and burn plan stable. If a displayed attribute changes, record it. If a run simply feels faster or stronger once, repeat before treating the result as an effect.
Do not rank tiers without knowing tradeoffs. An evolution could alter handling, fuel, attack, appearance, or another system; the public badge does not say which.
Protect resources and progress
Use only the live game’s own confirmation control. Avoid external “evolution calculators,” scripts, account services, or trade promises that request login information. No guide needs an authentication cookie to explain a visible requirement.
If the current UI offers reset, refund, or preview behavior, read the exact terms. Do not assume an evolution can be reversed. Save scarce resources until you understand whether later systems share them.
Check whether evolution state persists after leaving a Place or rejoining. Record a successful save before planning a multi-step tier route.
Evolution FAQ
What does evolution cost?
No verified public cost exists. Read the current interface and record its date because beta costs can change.
How many tiers are there?
The badge mentions tiered later evolutions but does not give a number or names.
What stats improve?
No public source specifies the effect. Use displayed attributes and controlled before-and-after runs.
Can evolution be reset?
No verified reset or refund rule was found. Treat the action as potentially permanent until the live UI says otherwise.
Why did the badge not award?
Confirm that the action was an actual first evolution in universe 10766687030, wait for the state to save, and recheck the exact live result. Do not infer a hidden requirement from one failure.