Building a Steal a Brainrot value calculator that doesn't lie about Cash/min

I've been trying to figure out which Roblox Steal a Brainrot collection is genuinely worth grinding for, versus which ones look good on paper but bottleneck on cash/minute when you actually pull them. Most community value calculators just show static values from a wiki sheet — they don't tell you whether a Tier S rarity matters when its cash-per-minute is lower than two Tier B brainrots stacked.So I built one. Here's what it does and why each piece exists.## The core misconception about brainrot valuePlayers default to ranking brainrots by rarity tier. The reasoning is "rarer = harder to get = more valuable." Half the time that's true. Half the time the tier system lies to you, and you can verify it with three minutes of cash/minute math.A Tier S brainrot that produces 18 Cash/min and a Tier S brainrot that produces 32 Cash/min are both nominally "the same tier." A Tier A at 24 Cash/min beats the 18 Cash/min Tier S in any time-bounded objective. The tier label is misleading because it conflates pull difficulty with revenue rate.The calculator has to make this comparison obvious.## Input fields that matterThe minimum useful inputs are:- Brainrot name (with autocomplete from a verified data file) — typing it freeform leads to typos and inconsistent data- Quantity owned — single brainrots versus a collection have different math- Mutation/variant flag — variant multipliers change the cash rate enough to matter- Active multiplier (if applicable) — game events frequently apply server-wide multipliersWhat I deliberately don't include:- "Rarity tier" as input — it's already implied by the brainrot data, no reason to make the user re-enter it- "Player level" or "world unlocks" — these affect what you can pull, not what each pull producesReducing inputs to four made the UI usable on mobile. Most game-value calculators have 10-15 fields because someone tried to model every edge case, and the result is a form nobody fills out.## The calculation that's surprisingly subtleThe naive calculation is cash_per_min = base_rate * multiplier. That's wrong for two reasons.First, mutation multipliers stack with active multipliers but don't always stack multiplicatively. Some mutations apply additively to base rate, others apply multiplicatively. The community wiki doesn't always specify which — I had to test by buying brainrots, applying mutations, and checking the in-game cash rate display.Second, the rate the game shows you in the inventory is rounded to the nearest integer. If you take two brainrots showing the same rate, they might actually differ by up to 0.99 Cash/min internally. For a collection of 50 brainrots that's enough rounding error to matter when you're deciding between two strategies.I ended up using the displayed integer rate with a +/- 0.5 confidence band in the calculator output. It's slightly less precise but honest about what the player can actually verify.## Sorting the outputThe output is a list ranked by total Cash/min for the input collection. But the more useful column is "Cash/min per slot" — because brainrot collections have inventory limits, and the question players actually have is "is it worth swapping this brainrot for that one?"A side-effect of building this: I stopped pulling rare brainrots that have low Cash/min ratings. Six months ago I'd have been excited about a Tier S pull. Now I check the rate first, and if it's below 25 Cash/min, the pull goes into a dump slot rather than my active rotation.## What the calculator made me stop doing- Hoarding low-rate Tier S brainrots for "value" — they're not valuable if they're not productive- Trying to maximize collection rarity — rarity diversity doesn't multiply cash rate- Running active multipliers during low-rate periods — multiplier minutes are limited, save them for high-rate runs## What I'd build differently if I started overThe biggest miss in v1 was not capturing the "what mutations exist on the brainrot" state correctly. I treated mutation as a single checkbox. It's actually multiple independent dimensions — color variant, animation variant, size variant — each with their own multiplier. Refactoring this is on the list.The other thing I'd do differently: scrape the active multiplier from the game's web API rather than asking the user to enter it. Players forget. The calculator output is wrong by 30-50% whenever a global multiplier is active and the user didn't toggle the checkbox.## Lessons that generalize beyond this specific gameAny game-value calculator should output the ranking by rate per slot rather than rate per item. Inventory is the binding constraint in most economy games.Tooltip text in the calculator should always show the source data, even if the source is "I measured this in-game." Players will trust output more if they can audit the assumptions.And the math complexity should match the actual question. A "should I grind for X" calculator doesn't need to model 14 input dimensions if 3 inputs predict the answer with 90% accuracy. The remaining 10% will be noise from the game's own rounding anyway.Brainrot value calculators are a tiny niche, but the pattern — surfacing rate-per-constrained-resource instead of raw values — is something I've started applying to other game-tracking tools too. The version of this calculator I'd want to use is the version that makes me change my play, not the version that confirms what I was already doing.