Grow a Garden Mutations

Crop mutations are named states applied to produce in Grow a Garden. Community guides consistently connect them to sale value, appearance, weather, pets, gear, and events. They are different from pet mutations, which modify the pet itself. This hub focuses on recognizing a crop state, finding its source, and deciding whether to harvest, protect, or continue stacking.

The live game contains far more mutation records than a useful first page can verify. Public databases also disagree about counts and may include combined calculator recipes, archived event states, admin-only effects, or aliases. This is therefore a currently documented source-and-decision index, not a promise of completeness.

Evidence status: crop mutations and their broad source classes are Community corroborated across current guides. Exact multipliers, incompatibilities, trigger chances, timings, visual states, and present availability require in-game verification.

Recognize the state before acting

Inspect the crop before harvesting. Look for a visible label, color, material effect, particles, or an inspect panel. Record the crop name and every displayed mutation, not just the most dramatic appearance. Weather and pet animations can overlap, and a screenshot without the item card may misidentify the result.

Commonly documented examples include Wet, Frozen, Gold, Rainbow, Moonlit, Pollinated, Verdant, and Amber. These names illustrate different source histories; they do not prove current multipliers or availability. If the game displays a different spelling or a new state, use the live wording.

The Crop Mutations index provides a field checklist that works even when the underlying list changes.

Source classes

Weather and world events can expose eligible crops during a live condition. Pets can periodically target crops or trigger on harvest. Gear and mutation sprays can apply a named effect through player action. Seasonal events and special systems may introduce temporary states. Natural growth or rarity variants are documented separately by some databases.

Source matters because it determines what the player can control. A spray can be aimed, a pet can be equipped, weather may require waiting, and a closed event may be historical only. Open Mutation Sources to choose the route before chasing a name.

Weather mutations

When weather begins, identify its live name and read any announcement. Keep eligible crops unharvested long enough to observe a result. Do not assume every crop can receive every weather state or that an old event timer still applies.

Use a small test patch. One clearly identified crop is easier to verify than a full garden covered by several pets and sprinklers. Record the start condition, crop state before weather, and state after. A non-result may mean chance, eligibility, timing, or outdated documentation; it does not prove the mutation was removed.

Pet-applied mutations

Community references repeatedly document pets such as Dragonfly, Sea Turtle, and Scarlet Macaw in crop-mutation roles. The exact target selection, cooldown, and effect must be read on the owned pet’s current card. A pet can also carry its own mutation, which is separate from the crop state it grants.

Equip one mutation-giver at a time, leave eligible crops available, and observe a full trigger. After establishing the baseline, add copying or cooldown-support pets. This prevents the wrong pet from receiving credit for the result.

Gear and mutation sprays

Gear gives the player a more direct route when the current item explicitly names a crop effect. Mutation Spray Amber is a historical community-documented example of a crafted targeted spray, while other sprays and tools may come from shops or events. Availability, recipe, charge count, and target rules can change.

Before using any consumable, read the target prompt, select a low-risk crop for the first test, and confirm the state afterward. The Mutation Sprays guide covers safe use and the Crafting guide covers recipe checks.

How stacking should be tested

Do not assume every mutation multiplies independently. Current calculators publish combinations, but their rules may compress exclusive variants, additive groups, or historical values. Start with a crop whose existing states are recorded, add one controlled source, and compare the resulting labels and sale preview.

If the new effect replaces, refuses, or coexists with the old one, record that exact result and date. Use the Stacking Guide for a repeatable experiment. A failed attempt is useful only when the crop, source, and current states are known.

Harvest, hold, or sell

Harvest when the crop completes an immediate quest, when the source can be repeated, or when the sale funds a more important upgrade. Hold when an active weather or pet route may add a compatible state, when the crop is a controlled test, or when the event asks for delivery rather than sale. Sell only after identifying the specimen and deciding whether its special state matters more as Sheckles, event progress, or trade inventory.

Avoid holding every special crop indefinitely. Plot space and visibility are resources. Favorite or isolate the most important specimens and keep a normal production area working.

Mutation lookup fields

For each currently documented mutation, record name, entity type, source class, source name, current availability, eligible target, visible identification, stacking notes, last checked date, and evidence level. Leave unsupported multipliers blank rather than copying a confident-looking number.

This structure also exposes mistakes. A pet mutation will fail the crop-entity field; an event-only source will fail current availability; a calculator combination will fail the direct-source field unless the actual component states are known.

Common mutation mistakes

Do not confuse a crop mutation with a pet mutation. Do not treat an admin or historical event effect as normally obtainable. Do not harvest before recording the current state. Do not import a multiplier from Grow a Garden 2. Do not run several unobserved sources at once and assign the result to whichever animation appeared last.

Recovery means simplifying the setup: one crop, one source, one observation. Once the mechanic is clear, scale it across the garden.

Mutation questions

What mutations are in Grow a Garden?

Current community indexes document many natural, weather, pet, gear, and event states. This site lists useful verified classes rather than claiming an exhaustive count.

Can mutations stack?

Many community tools document combinations, but exact compatibility and value math are update-sensitive. Test one added state at a time.

What is the best mutation?

That depends on availability, target crop, stacking rules, and current multiplier. A huge historical number is not useful if its source is closed.

Where should I start?

Identify one desired state in Crop Mutations, choose a live route in Mutation Sources, then use Stacking before combining it.