Good gnome placement begins with a simple rule: use every confirmed productive position, then change only one position at a time. Roll A Gnome’s official loop connects gnomes to crop production and garden growth, but public sources do not establish exact slot counts, adjacency bonuses, crop formulas, movement costs, or a universal best layout. Your current plot is the source of truth.
Map your current garden
Stand where the entire plot is visible and count only positions the interface allows you to use. Record which gnome occupies each position, its visible level, the associated crop, and whether the crop is growing, ready, or empty. Do not count decorative soil, locked plots, or another player’s garden as available capacity.
Current gameplay shows player plots marked with ownership and placed gnomes labeled above garden areas. Exact layout and capacity can change as the garden expands. Use a simple numbered map—front left, front right, and so on—rather than relying on an old screenshot.
Placement priority
Make one controlled swap
Choose the position with the lowest confirmed contribution, not the gnome with the least exciting appearance. Record one normal cycle: crop type, time from empty to ready, collected quantity, and money gained when sold alone if the game allows it. Then replace that gnome with one reserve result and repeat under the same upgrade and boost state.
If the output improves, keep the change but write down exactly what improved. If only the crop changes and sale value is unknown, the result is not yet better. If the new gnome begins at a different level, compare several cycles only after understanding whether level changes during placement. Community footage indicates visible gnome levels, but the gain method and effect are not verified.
Separate four possible benefits
More crop per cycle
Measure collected quantity while every garden-wide upgrade remains unchanged.
Faster readiness
Time from the same starting state and account for crops already partway grown.
Higher sale value
Sell a known quantity separately; avoid mixing several crop types in one total.
Special utility
Copy the game’s exact effect text and test its trigger rather than inferring from animation.
Handle reserve and duplicate gnomes
Keep a short reserve list with name, displayed rarity, level, and why it is not placed. A reserve might be waiting for expansion, a controlled comparison, or clarification of its effect. If multiple copies can be placed, label them separately. If the game provides a merge, sell, or upgrade action, read the confirmation and record what will be consumed before using it.
No current public source verifies a universal duplicate system, so do not discard copies on the assumption that only one can ever matter. Likewise, do not spend repeatedly for new names while several supported workers are idle because your garden is full.
When to expand instead of replace
Expansion is strongest when you have a usable reserve gnome, every current productive position is occupied, and the new capacity is affordable without breaking your basic roll-and-sell loop. If expansion opens space but requires another expensive step before placement, count the full cost. If your reserve’s effect is unknown, test it in a current position first when moving is reversible.
Use Garden Expansion to compare visible price, requirement, added capacity, and payback. Never assume each expansion adds the same number of spots or follows the same cost curve.
Placement mistakes to avoid
Avoid changing the whole garden and then attributing a result to one gnome. Avoid comparing output while a global upgrade or temporary boost changed. Avoid treating a visual rarity as a production multiplier. Avoid counting a crop already growing when you started the timer. Avoid moving a gnome before checking whether a confirmation warns about lost progress. Finally, avoid optimizing only travel distance if the game provides collection or Auto Sell mechanics that change the bottleneck.
A compact garden record
For each position, keep: position label, gnome name, displayed rarity, visible level, crop, start time, ready time, collected quantity, sale result, active upgrades, and check date. Unknown fields can stay blank. Repeat after a meaningful update or expansion instead of assuming the old layout remains optimal.
Next checks
Use the Gnome List to identify a reserve worker, Crops to track output, Money to value the complete sale cycle, and Offline Growth to see whether placement continues producing while away. Exact slot limits, movement rules, adjacency effects, level behavior, crop formulas, and expansion interactions still need direct testing.