A useful crop-mutation list needs more than names and large multipliers. Players need to know what the state looks like, what can apply it, whether that source is currently available, and what happens when the crop already carries another mutation. This page supplies that lookup method and a small set of currently documented examples.
Exact values are omitted unless the live game can reproduce them. Current community databases contain hundreds of entries and combinations, but totals and formulas disagree.
Core identification fields
Record mutation name, crop name, visible label, appearance, source class, specific source, date, and existing states. If a value preview is available, record it separately from a calculator result. This is enough to distinguish a direct mutation from a combined recipe or visual misunderstanding.
Never identify a state from color alone. Lighting, weather, crop rarity, and overlapping effects can change appearance.
Currently documented examples
Wet and Frozen recur in weather and mutation guides, but their relationship and value effects must be checked in the current game. Gold and Rainbow are widely documented high-visibility states. Moonlit is associated with lunar content in historical/current community material. Pollinated appears in bee-related systems. Verdant is associated with pet-applied community coverage. Amber has been documented through a crafted spray and a pet route.
Each example is Community corroborated as a game term or historical mechanic. None is a promise that its original source is currently active or that a remembered multiplier still applies.
Confirm the source
For weather, record the live weather name and event window. For a pet, record its exact live ability and target. For gear, record the item name, charge or consumption behavior, and selected crop. For an event, record the event title and whether the reward or trigger is present now.
Source confirmation matters when the same mutation has several routes. A closed craft can be historical while a pet route remains usable, or the reverse.
Decide what to do with the crop
Hold it when testing a compatible second state, completing an event delivery, or preserving a scarce specimen. Harvest it when the crop itself must be collected for a task or when the source can be repeated. Sell after checking the state and deciding that Sheckles are the goal. Trade only through the supported interface and keep community demand separate from in-game value.
Favorite or isolate high-interest crops. A crowded garden makes it easy to collect the wrong fruit and destroys the evidence needed to compare results.
Verify a multiplier
Use two specimens of the same crop with comparable visible properties. Keep one ordinary and apply one known state to the other. Record the game’s sale preview or result for each. Do not derive a multiplier when weight or another mutation differs.
Compare the result with a current calculator only after the in-game observation. If they disagree, mark the calculator value unconfirmed rather than adjusting your observation to fit it.
Maintain the crop index
Add a mutation only when its exact original-game name and entity type are supported. Merge spelling aliases into one entry, keep combined calculator recipes separate from direct states, and mark event-only sources with the event year. When a source closes, preserve the historical record but remove any instruction that tells new players to obtain it now.
Crop mutation FAQ
Are Gold and Rainbow crop mutations?
They are widely documented crop states in the original game. Their exact current value effects and sources need a live check.
Is Moonlit always obtainable?
No permanent availability is asserted. Lunar conditions and events change, so verify the live source.
Does Amber require a spray?
Historical community reporting documents both a crafted Mutation Spray Amber and a Raptor pet route. Current recipes, pet effects, and availability must be rechecked.
How do I know if two states stack?
Record the crop first, add one controlled source, and inspect whether both labels remain. See the Stacking Guide.