Field note 01 · 4 minute read

Start with the right number.

A calculator can be perfectly consistent and still answer the wrong question if the starting value is wrong.

Give the input a clear meaning

In Garden Ledger, “base value” means the sell value of an unmutated crop at the weight you want to evaluate, in Sheckles. Weight belongs in that starting number; mutations do not. The calculator applies supported mutation math after that point.

A community reference may use “base value” for a crop at its reference weight. Those two meanings are not interchangeable. A reference-size value still needs the appropriate size calculation before it can become this tool’s input. Garden Ledger has no crop-weight lookup, so it cannot perform or verify that step for you.

Decide whether your number fits

  • Seed purchase price: does not fit. It measures the cost to buy a seed, rather than the sell value of its harvested crop.
  • Weight in kilograms: does not fit. A weight is not a currency amount.
  • A minimum or reference crop value: fits only if it actually describes the weight you are evaluating and excludes mutations.
  • A quote for an already-mutated crop: does not fit directly. Reapplying its mutations would count them again.
  • A hypothetical unmutated value: fits an exploratory scenario, provided you keep that assumption attached to the output.

What double counting looks like

Consider a hypothetical unmutated value of 100 and Gold growth with no environments. This model gives 100 × 20 = 2,000. If you then enter 2,000 as the base and choose Gold again, it produces 40,000. The arithmetic is consistent, but the input repeats the Gold effect.

This is why a plausible-looking result is not enough to validate a starting value. Keep a label such as “100 Sheckles before mutations at the weight being compared” alongside the number. If you obtained it elsewhere, also note whether that source means reference-size value or weight-adjusted value.

When you only have a mutated quote

You can divide a quote by a total multiplier on paper, but the inferred base is only as reliable as every assumption behind that multiplier. An unsupported mutation, an extra bonus or a changed game rule can all affect it. Re-entering that inferred base and recovering the same quote would be circular; it would not verify the game’s formula.

For example, 2,000 ÷ 20 = 100 only describes the Gold-only hypothetical above. It does not prove that any fruit quoted at 2,000 has an unmutated value of 100. For a Sheckle estimate, Garden Ledger asks you to supply the base rather than automatically presenting an inferred value as fact.

Explore safely when the base is unknown

For a mutation-only question, open the multiplier explorer. It compares all 24 supported configurations without requiring a base. A multiplier difference can be useful even when a Sheckle estimate would depend on an unknown input.

If you have a reason to assume a base range, the comparison workbench accepts explicit low and high values. For example, Gold plus Wet applied to an assumed base range of 80–120 gives 3,200–4,800. This demonstrates sensitivity to your assumptions; it does not measure your crop or identify the correct base. Follow the three worked comparison tasks to reproduce an interval test.

Keep a useful comparison record

Note the crop, weight, base value, where that value came from, selected mutations and the date you observed or assumed them. Mark each value as observed, calculated or hypothetical. Two fruits with the same name can still be unsuitable for a mutation-only comparison if their starting values differ.

Check an unexpected result in order

  1. Confirm the entry is a sale value in Sheckles and excludes mutations.
  2. Check that it describes the relevant weight rather than a different reference size.
  3. Enter plain digits and an optional decimal point, without commas or a currency symbol.
  4. Check the selected labels against the crop and the supported scope.
  5. Compare with the actual in-game quote, allowing for unsupported effects and update risk.

Try a clearly labeled scenario →