Sources, with the limits included.

The source and its actual review status

1. Grow a Garden Wiki: Crop Mutations ↗Community reference · indexed excerpts inspected October 17, 2026

   Direct retrieval was blocked by the source’s robots rules. We inspected search-index excerpts containing variant entries, environmental entries, rules and calculation examples. The search service marked its copy as crawled about three months earlier. We did not review a complete live revision.

2. Grow a Garden on Roblox ↗Official experience listing · identification only

   This identifies the game. It is not the source of this calculator’s multipliers or proof that they match the current game.

The inspection date describes our source check. It is not a game update date, the source’s last edit date or evidence of current mechanics. No in-game tests have been performed for this site. Every game-mechanics entry below remains community-reported.

Model evidence register

“Wiki index” below means the community page and limited inspection described above. Normal is this interface’s label for the reference’s unmodified 1× state. The calculator offers a subset of the documented variants and environments.

What follows from the assumptions

The 24 configurations come from three growth choices × four temperature-state choices (none, Wet, Chilled or Frozen) × two Shocked states. This is the number of valid configurations in this interface, not a count of mutations in the game.

Multiplier differences, percentage changes, matching-base thresholds and interval rankings are arithmetic derived from those assumptions. Automated software checks can verify these calculations and input rules. They cannot upgrade a community claim into an observed game mechanic. No crop-price, weight, probability, stock or event dataset is maintained here.

A record a player could actually verify

The steps below are a protocol for collecting evidence, not a report of an experiment we performed. If you cannot obtain an independent starting value or account for all visible effects, mark that limitation instead of filling the gap with an assumption.

1. Identify the observation. Record the date, any visible game version, crop or fruit identity and the weight displayed. Retain the full list of variant and mutation labels, plus any other active value-affecting effects you can identify.
2. Establish the input independently. If available, record an actual unmutated quote for that same fruit at the same weight before its mutations change. Keep evidence of the quote and weight. If a different fruit is used, record that difference; matching displayed weights may hide rounding and does not establish identical underlying values.
3. Control the comparison. When an observable change occurs, record the new labels, weight and quote. To examine one multiplier or replacement, the comparison must not also contain an unexplained weight change or additional effect. If it does, record it as confounded rather than a clean test.
4. Calculate a prediction separately. Apply the stated model to the independently recorded unmutated value. Record predicted and observed values together, including a difference. A mismatch is evidence to investigate, not permission to change the observation.
5. Keep unknowns visible. Without an independent base, you may inspect a relative change only if there is a reason to treat the underlying crop and all other factors as unchanged. State that condition and any display-rounding uncertainty. One observation does not validate every combination or later game version.

A circular check to avoid: dividing a mutated quote by an assumed multiplier to create the base, then multiplying that base by the same multiplier. Recovering the original quote is an identity; it supplies no independent evidence for the multiplier.

Send a correction through Contact & corrections with the affected rule and reproducible evidence. Formula changes should update the engine, evidence register and worked examples together. We publish no player observations as verified results on this page.