guide
A code-reward decision guide for players choosing between repairing a weak route and testing a new crop, pet, or mutation.
Short answer
Use Grow a Garden codes to recover if your route is unstable, but use them to experiment only when your crop loop and resources can handle one failed test.
This is the fastest direct answer for readers who want the result first and the longer route logic second.
Use these pages when the short answer turns into a more specific choice.
Quick facts
Editor notes
| Route state | Use codes for | Why | Avoid |
|---|---|---|---|
| Fragile route | Recovery | Protects progress | Risky experiment |
| Stable route | One experiment | Can absorb failure | Changing several parts |
| Unclear bottleneck | Guide first | Need a target | Blind spending |
| Patch just landed | Updates first | Assumptions may change | Old spend plan |
Editor notes
Editor notes
Editor notes
Editor notes
Code rewards can cover mistakes. If the route is fragile, spend that cushion on recovery before using it for a new experiment.
A new crop, pet, or mutation test is easier to judge when the current route already works. Otherwise, the test may only add noise.
If you do experiment, use one code-funded test. Changing several things with the same reward makes the result hard to read.
Continue with
Editor notes
Editor notes
FAQ
These are the follow-up questions readers usually ask right after the short answer.
Use codes to recover when the route is unstable. Experiment only when the current route can absorb one failed test.
Read Codes pageThe safest use is fixing the weakest route piece that keeps progress from repeating.
Read Codes pageRun one experiment at a time so you can tell whether the reward-funded change helped.
Read Codes pageRe-check after code reward quality or route stability changes.
Continue with
Continue with
Continue with
Continue with