Ride A Pet Mutations Guide

Short answer

The official Ride A Pet description confirms that mutations make pets faster. It does not name mutation types, multipliers, triggers, stacking limits, or overwrite behavior. Community material proposes five mutation names—Shocked, Volted, Rage, Void, and Eternal—and says weather can grant them, but the current version and claimed multipliers have not been verified.

The biggest unresolved rule is whether mutations stack. One secondary Phoenix page describes first, second, and third-or-later mutation speed bands; a community mutations page says a pet can have only one mutation and that a higher mutation replaces a lower one. As of September 16, 2026, this page does not choose between those conflicting models.

Evidence layers

Layer	Claim	Status	Safe conclusion
Official description	Mutations increase pet speed.	Confirmed for the scope of the description.	Mutations are a speed-progression mechanic.
Community candidate list	Shocked ×2, Volted ×3, Rage ×4, Void ×10, Eternal ×100; obtained during weather.	Unverified current-version claims.	Use the names and numbers only as test targets, not settled stats.
Secondary Phoenix model	First, second, and third-or-later mutations correspond to different speed bands.	Conflicts with the one-mutation model and also relies on disputed Phoenix speed data.	Do not infer stacking from this source.
Community overwrite model	A pet has one mutation; a higher mutation replaces a lower mutation.	Unverified and in conflict with the Phoenix framing.	Protect valuable pets until the overwrite rule is observed in game.

Community mutation candidates

Candidate	Community-claimed multiplier	Community-claimed trigger	Evidence state
Shocked	×2	Weather	Candidate only; not verified in the current game.
Volted	×3	Weather	Candidate only; not verified in the current game.
Rage	×4	Weather	Candidate only; not verified in the current game.
Void	×10	Weather	Candidate only; not verified in the current game.
Eternal	×100	Weather	Candidate only; not verified in the current game.

These values come from a community page, not an official current-version table. They should not be used to calculate a pet’s expected speed or trade value without an in-game reproduction.

Before testing a mutation

Use a pet you can afford to test; the overwrite and loss behavior is unresolved.
Record the pet’s exact name, visible mutation label, and any visible speed value or unit before the test.
Note the server date, visible weather/event name, and any on-screen instructions. “Weather” is currently only a community claim, so record the game’s actual wording.
Choose a fixed route for a before-and-after travel-time check. Do not combine the test with a pet swap, rebirth, or upgrade.

A conservative verification procedure

Wait for an explicit game signal. Only treat an on-screen weather/event label, mutation prompt, or pet-state change as the start. A community timetable is not enough.
Apply or receive one mutation event. Follow the current game prompt rather than an assumed button path; no source in the ledger confirms the controls.
Inspect the pet immediately. Record whether a label, visual effect, or displayed value changed.
Repeat the same route. Compare the pet against its own pre-mutation time under matched conditions.
Test overwrite behavior separately. If the game offers another mutation, use a non-critical pet and capture whether the old label remains, is replaced, or is combined.

Success signal: the game visibly marks a mutation and the same pet shows a repeatable speed change on the same route. A visual effect alone can confirm an effect occurred, but not a specific multiplier.

Failure branches

No mutation appears during weather: the community trigger may be incomplete, outdated, chance-based, or tied to another requirement. Do not convert a failed attempt into proof that the type was removed.
A label changes but route time does not: repeat under matched conditions and check whether the effect targets a different value. Do not assign the community multiplier from appearance alone.
A second mutation replaces the first: record both labels and treat the result as evidence for overwrite behavior for that pair and version, not necessarily a universal hierarchy.
Both effects appear: record the exact UI and measured result. This would challenge the single-mutation claim, but it still would not prove that all mutations stack.
The pet loses an effect or value unexpectedly: stop testing valuable pets and capture the before/after state. The current sources do not establish recovery behavior.

What “higher overrides lower” would need to mean

The community candidate multipliers suggest an ordering, but the ordering itself has not been confirmed by the game. A reliable overwrite rule needs three observations: the original mutation, the incoming mutation, and the resulting pet state. It also needs both directions—for example, testing a claimed higher effect over a lower one does not reveal what happens when a lower effect follows a higher one.

Until those cases are reproduced, this guide uses conflicting rather than “stacking” or “one slot” as the rule status.

Evidence and update status

Roblox experience description (src-game) — checked September 16, 2026: confirms only that mutation increases pet speed.
Community wiki index (src-wiki) — publication date unknown; checked September 16, 2026: supports the existence of community mutation material, not its current-version accuracy.
rideapet.wiki Phoenix page (src-competitor-phoenix) — publication date unknown; checked September 16, 2026: describes mutation-number speed bands; its base Phoenix numbers also conflict with another source.
Community mutations page (src-wiki-mutations) — publication date unknown; checked September 16, 2026: supplies the candidate names, multipliers, weather claim, and one-mutation overwrite claim.

Update this guide after a current-version mutation is captured with a before/after pet state, trigger, and repeated route measurement. One observation should not silently validate the entire community list.