tableMap the symptom to an upgrade class
This decision map avoids copying an old fixed price. Read the current Shop field only after identifying the system that is holding back the next cycle.
| Symptom | Upgrade class | Success check |
|---|
| Plots spend time waiting | Grow speed or production | More completed cycles in the same observation window |
| Gnomes cannot work | Garden space or capacity | Previously idle workers receive a usable position |
| Harvest remains unsold | Sell or Auto Sell flow | Inventory reaches cash with less delay |
| Garden has spare capacity | Roll or luck improvement | New results can be placed without creating idle workers |
Run a one-change upgrade test
Change one system and observe one full cycle. Otherwise a better roll, sprinkler and expansion can hide which purchase solved the problem.
- 1
Name the limit
Use a visible symptom in the current Garden.
- 2
Read Shop now
Confirm the current cost and effect before buying.
- 3
Change one input
Keep the worker and other upgrades stable where possible.
- 4
Measure the next cycle
Check whether idle time, output or selling delay improved.
statusUse sprinkler evidence carefully
A Basic Sprinkler and growth-focused upgrades appeared in reviewed gameplay, but the collected sources do not support publishing a permanent price or exact stat here.
What it suggests
Sprinklers belong to the production-improvement path in the reviewed interface.
What to verify live
Read the current cost, area and effect before comparing it with expansion or luck.
