Idle Game Balance: The Math of Idle and Merge Games

An idle game is not a game you leave running — it is two curves you choose, and balancing it means choosing where they cross. One curve is what a generator costs as you buy more of it. The other is what it earns. Everything players experience — the generous first hour, the mid-game grind, the prestige reset — falls out of those two lines, and both of them fit in a spreadsheet column long before they fit in a game engine.

A disclosure up front: this blog belongs to Egmatic, a no-code 2D editor in pre-alpha built around the layer a game needs between Build and Launch. The math below is engine-agnostic — it governs idle games in every tool, and it is the rare part of game design you can fully draft without code.

The short answer#

Idle and merge economies run on one pair of formulas and one crossover rule:

Growth rates in shipped games cluster tightly: AdVenture Capitalist charges 1.07^owned for Lemonade Stands, Cookie Clicker charges 1.15^owned for buildings. That narrow band is the genre's public secret — the feel of an idle game lives less in wild invention than in where you place the wall, the multiplier bumps, and the reset.

The two curves that run every idle game#

The canonical model, laid out in Anthony Pecorella's The Math of Idle Games (he was lead producer of the mobile version of AdVenture Capitalist at Kongregate):

• cost_next = cost_base × rate^owned
• production_total = production_base × owned × multipliers

Run it on AdVenture Capitalist's first generator, the Lemonade Stand: base cost 4, growth rate 1.07, base income 1.67 per second. At ten stands, the eleventh costs 4 × 1.07^10 ≈ 7.87 while the fleet earns 16.7 per second — purchases feel nearly free. Run the same two columns on and the curve turns: by a few hundred stands, the next purchase is priced in hours of waiting. Nothing changed except the exponent doing its work.

The theorem underneath the genre: exponential growth eventually overtakes any polynomial growth, no matter how small the exponent's base or how big the polynomial's power. Income that scales with owned (linear), or even owned squared, loses the long game to a cost that scales with 1.07^owned. Designers lean on three patches to stretch the race:

• Milestone multipliers. AdVenture Capitalist doubles a generator's output at 25 and 50 owned (the boosts stack). Each bump snaps income back above cost for a while — the sudden acceleration players feel at round numbers is a table row, not an accident.
• New generators. Each tier resets the owned-counter to zero, restarting the cheap region of a fresh exponential. The newest generator dominates income almost immediately after purchase, which is also a balance warning: if it always dominates, the old ones are decoration.
• Bulk-buy pricing. The closed-form cost of buying n generators at once is cost = base × r^k × (r^n − 1) / (r − 1) with k owned — the same math your "buy max" button uses.

In the developer communities we read, the same complaint keeps surfacing: an idle economy that "outgrows the time gates" — the carefully placed waits become trivial because income pulled ahead of the cost curve somewhere. That is not a content problem. It is the crossover moving, and it means one of the two formulas needs a constant adjusted.

Merge games: the same math, one decision deep#

Merge games are idle math with a spatial interface. Triple Town (Spry Fox, 2010) established the merge-three pattern; 2048 made merge-two a global vocabulary in 2014; Merge Dragons turned it into a live-service economy at launch in 2017 — Gram Games' first in-app-purchase title, good enough that Zynga paid $250 million in cash for the studio in May 2018. Underneath the dragons sits one decision the designer makes:

Merging five instead of three saves one input in six — about 17% — and the saving compounds with every tier of the chain. Merge Dragons teaches both rules explicitly in its official guide: three matching objects become one better object, five become two. Player skill in the entire genre largely reduces to hoarding for fives, and the board space you give players to hoard in is your difficulty curve. The math created by a merging system grows fast — chain length is itself an exponent — which is why merge economies need the same cost-curve discipline as idle ones: what each tier costs to produce, versus what it pays out, must cross somewhere you chose.

Walls, time gates, and the day-7 cliff#

The place where the cost curve pulls far enough ahead of income that the next meaningful purchase takes hours is the wall. Walls are not failures — they are the genre's pacing. The design failure is an untuned wall: one that arrives by accident, usually in week one, where a player who has run out of content and multipliers faces an exponent with nothing to do about it. Balance a first wall deliberately: enough generators and milestones in front of it that the player has learned the loop, and a prestige system waiting behind it.

Time gates — waits that pace progress directly — interact with the curves honestly: a gate is a fixed cost in seconds, and an economy whose income curve outpaces its cost curve turns every gate trivial. If beta players describe your mid-game as "trivially solvable," check whether a multiplier stack has pushed income permanently above cost before blaming the gates.

Prestige: the pressure valve#

Prestige — reset everything, keep a permanent bonus, popularised by Cookie Clicker — has two jobs: it resets the player to the cheap region of the curve with more power (the ladder), and it drags a runaway currency back to a number a human can read. Four shipped games, four real formulas:

The exponent is the design lever. A square root means each doubling of prestige currency demands roughly four times the earnings; Cookie Clicker's cube root pushes that to eight; Egg, Inc.'s one-seventh exponent makes each run worth prestige on its own — a fit for its two-hour offline cap, since progress cannot lean on idle time. Realm Grinder's use of max earnings adds a rule the others lack: resetting at the same point you always do earns exactly nothing new, so players must push further each run. Pick the doubling cost you want players to face, and the formula picks itself.

The spreadsheet loop: balancing without code#

The practical secret of the genre: none of this needs a build. Pecorella's own balancing models, referenced throughout the series, are spreadsheets he published for anyone to duplicate. The loop that replaces guesswork:

1. List every generator in rows: base cost, growth rate, base income.
2. Add two computed columns — cost of the next one and total income at this count — and fill down for a few hundred purchases.
3. Chart both. The crossings are your walls; count the rows between them to read wall placement in purchases, then in seconds at expected income.
4. Place multipliers on purpose. Set the ×2 bumps (25, 50, 100 owned) where the gap gets discouraging; each one is a spike of felt progress.
5. Run one week in the sheet. Sum income day by day against costs; if the sheet says day 7 is a flat line with nothing to buy, the cliff is now visible in advance — move a wall or add a milestone.
6. Choose prestige from the table above, and sanity-check the doubling cost against how long a run takes.
7. Only then wire the numbers in. The tuning happened at design time; the engine just executes constants.

This is also why economy design is a genuine no-code discipline: the decisions are arithmetic and chart-reading. If you want the broader habit of testing a mechanic before building it, how to validate game mechanics before you build covers the pattern — an economy is just the mechanic whose prototype is a spreadsheet. And because an idle economy is ultimately a function of saved state plus a timestamp rather than a running simulation, the question of where that state lives is the natural next one; the client-side version of it is one of the five patterns in async multiplayer without a server.

Where Egmatic fits#

Egmatic is being built for exactly this kind of design-first work: you direct, it executes, you own the result. An economy tuned in a spreadsheet is a table of constants and rules — precisely the kind of thing our no-code, AI-native editor is meant to let you express without a code file in sight, alongside the save, sync, and ship layer the finished game needs. It is honestly pre-alpha; features arrive when they hold up, and we say so.

If you are balancing an idle or merge economy right now, the waitlist at egmatic.com is where you weigh in on what the editor should handle for you — so the ship layer fits the game you actually tuned, not a template.

One adjacency worth naming: in idle and merge games, the numbers are the feel. The pacing curve is what making your game feel good means when there is nothing to jump. Juice still matters — the merge pop, the purchase sound — but no amount of screen shake fixes a wall nobody placed.

Common mistakes#

• Picking a growth rate by feel. Shipped games cluster near 1.07–1.15, and the choice should come off a chart, not vibes; 1.07 and 1.15 are different games.
• Linear or polynomial costs. Income that is also linear eventually overtakes them permanently; the game becomes trivially solvable and dies of inflation. The exponential must always reclaim the lead.
• Letting the newest generator dominate. If tier n+1 out-earns every earlier tier the moment it is affordable, the earlier tiers are UI clutter — spread value by varying multipliers across generators.
• Walls that arrive by accident. Every crossover in the sheet is a scheduled emotion: chart them, then decide which ones get a multiplier, a feature unlock, or a prestige button in front of them.
• A prestige formula chosen last. The doubling cost (4×, 8×, 128× earnings) sets the length of every run in the game; choose it with the cost curves on the same screen.
• Treating merge-5 as a bonus rule. At 2.5 inputs per output versus 3, it is a 17% economy-wide discount that compounds per tier — it belongs in the balance sheet from day one, not in a patch note.

The takeaway#

Idle and merge game balance is not a mystery genre — it is two curves, a crossover, and a reset rule, all of them visible in a spreadsheet before any code exists. Choose the growth rate deliberately, place the walls on purpose, spend multipliers where the chart sags, and pick a prestige exponent for the run length you want. The games that feel generous never stopped being exponential; they just chose where the exponent bites. Tune the sheet until the first week reads the way the game should feel — then build.