Compare the possibilities.

How to read the matching value and ranges

A matching base follows from the same formula

For each scenario, estimated sale value = unmutated base × total mutation multiplier. Holding B’s mutations fixed, solve B base × B multiplier = A estimate. That gives B’s matching base = A estimate ÷ B multiplier. Every matching threshold is approximate; a displayed rounded value is not a guaranteed minimum input.

The percentage change is (B estimate − A estimate) ÷ A estimate × 100. A value of zero in A gives no percentage reference, even when B is also zero. For sensitivity, adding one unit to a base adds that scenario’s total multiplier to its estimated sale value.

Worked example: a stronger stack can start from a lower base

A base of 100 with Gold, Frozen and Shocked has a multiplier of 2,180 and an estimate of 218,000. A base of 40 with Rainbow and Shocked has a multiplier of 5,000 and an estimate of 200,000. B’s matching base is approximately 218,000 ÷ 5,000 = 43.6. At the entered base of 40, B is about 8.26% lower than A. Each additional base unit in B adds 5,000 to its model estimate.

Ranges compare bounds, not likelihood

All supported multipliers are positive, so each low base produces the low estimate and each high base produces the high estimate. A is strictly higher throughout only when A’s low estimate is greater than B’s high estimate. Reverse that test for B. If the intervals overlap or merely touch, neither scenario is strictly higher across every combination. If both intervals reduce to the identical single sale estimate, the result is a shared point.

For example, Normal with base 100–120 gives an estimate range of 100–120. Gold with base 4–5 gives 80–100. Those ranges touch at 100; A is not strictly higher in every case. The tool assigns no probability to any value within a range, and does not assume the midpoint is typical.

What this analysis leaves out

Use unmutated sale values that already account for the relevant weight. These tools do not infer weight, crop prices, mutation chances, time, availability, costs or profit. The underlying community model covers only the listed mutations and has not been independently verified in game. User-entered bounds express assumptions, not measured distributions. The base limit is 1,000,000,000,000,000; endpoint calculations must also stay within the engine’s safe numeric range. A matching value outside that range is flagged, and a positive value below numeric precision is never presented as zero. Read the method and source limits before relying on an estimate.