Base Cash reward ÷ Energy cost.
Calculator Methodology
Quick answer: the calculators apply ordinary arithmetic to dated visible rows and player-entered assumptions. They do not discover hidden formulas. Inputs are bounded, invalid URL values are rejected or clamped, results are derived deterministically, and static tables explain the same decisions without JavaScript.
Source-backed presetsPlayer inputs stay customDeterministic tests
Published formulas
What each tool calculates
Base XP reward ÷ Energy cost.
Target reward ÷ reward per run, rounded up.
Hourly income × online hours + hourly income × offline hours × 0.25.
Current price ÷ blended daily income, then converted to hours or days.
Cash × 0.1 fee versus exposed Cash × player-entered loss percentage.
Input provenance
Game rows and player assumptions stay separate
Preset data
Job rows, Property samples, offline rate, bonus, and Bank fee come from dated visible screens with source IDs.
Custom inputs
Level, Energy, mastery, target, recovery time, price, schedule, Cash, and risk belong to the current player scenario—not the game database.
Validation and rounding
How unsafe or ambiguous values are handled
- Zero or negative money inputs return unavailable results rather than infinity.
- Efficiency rankings use unrounded source values; display formatting happens afterward.
- Required run counts round up because a fraction of a run cannot complete a target.
- Only allowlisted, bounded query parameters enter shared URL state.
- Unknown mastery effects are not applied to base-reward presets.
- Property prices can reflect ownership state, so the live player price can override a sample.
Update history
What was rechecked
- Published Job, Property, and Bank formulas plus validation and URL-state rules.Tested calculator libraries