Idle game design explained

What idle games are

An idle game (also called an incremental, clicker, or “number go up” game) centers on a primary resource that grows over time — often currency, cookies, gold, or energy — which players spend on generators or multipliers that accelerate future growth. The defining contract: progress continues while the player is away, within limits.

Subgenres differ in how much active play they require:

• Pure idle — minimal input; automation handles everything after early unlocks (e.g. AdVenture Capitalist).
• Semi-idle / incremental — active bursts matter; idle earnings supplement but do not replace clicking or ability timing.
• Idle RPG hybrids — combat, gear, and gacha layered on exponential stat curves (common in Asian mobile markets).

Unlike action games where mastery is reflex-based, idle design mastery is curve engineering — when the player hits a wall, when a breakthrough feels earned, and when a reset delivers a dopamine spike without invalidating prior time.

The core loop

Every successful idle game repeats a tight four-step cycle:

1. Earn — tap, passively generate, or receive offline income.
2. Spend — buy generators, upgrades, or automation.
3. Accelerate — income rate increases super-linearly for a window.
4. Hit a wall — next purchase cost outpaces income; player waits, optimizes, or resets.

Production formulas

Most idle games model income as a sum of generator outputs. A common pattern:

income_per_second = Σ (owned[i] × base_rate[i] × multipliers)

Upgrade costs typically follow exponential scaling:

cost(n) = base_cost × growth_raten

where growth_rate is often 1.07–1.15 per level. The ratio between income growth and cost growth determines how long each “tier” lasts. If costs outpace income too aggressively, players churn at the first wall; if too loosely, numbers inflate without meaningful decisions.

Milestones and burst rewards

Flat exponentials feel monotonous. Designers inject threshold bonuses — every 25 or 50 levels of a generator doubles output, or unlocking generator N+1 requires owning N at level 10. These create visible “spikes” on the income chart and give players short-term goals between major walls. Pair milestone pacing with progression system principles: each spike should teach a new optimization (which generator to prioritize, when to stop leveling vs buy new).

Prestige and meta-progression

Prestige (also called ascension, rebirth, or New Game+) is the idle genre's signature retention mechanic. The player voluntarily resets most or all progress in exchange for a permanent multiplier or new currency that makes the next run faster.

When to offer the first prestige

The first prestige should arrive after the player has experienced one full “wall → breakthrough” cycle — often 30–90 minutes of first-session play for browser titles, or 2–4 hours for mobile. Too early and prestige feels trivial; too late and the wall feels like punishment.

Prestige currency math

A typical formula awards prestige points based on lifetime earnings:

prestige_points = floor( (lifetime_earnings / scale)exponent )

with exponent between 0.4 and 0.6 so returns diminish but never fully plateau. Each prestige point might grant +1% global income. The key design question: does prestige unlock new mechanics (a second generator tree, a skill tree) or only multiply existing ones? New mechanics extend content life; pure multipliers are cheaper to build but exhaust faster.

Meta-layers beyond prestige

• Achievement multipliers — one-time bonuses for milestones.
• Research trees — spend prestige currency on branching upgrades.
• Seasonal ladders — limited-time resets with exclusive cosmetics.
• Cross-prestige currencies — diamonds or souls that never reset, funding gacha or permanent unlocks.

Offline progress and the anti-idle paradox

Offline earnings are the hook that brings players back. When they reopen the app, show a satisfying summary: “While you were away, your factory earned 1.2M cookies.” Implementation is usually:

offline_gain = min(elapsed_seconds, cap) × income_per_second × offline_efficiency

Caps matter: uncapped offline income lets players skip weeks of design with one long absence, collapsing pacing. Common caps: 4–24 hours of simulated production, sometimes extendable via IAP or rewarded ads.

The anti-idle paradox

Pure idle games risk optimizing themselves into boredom — if automation handles everything, why open the app? Strong designs introduce periodic active interruptions: timed events, mini-games, boss fights with DPS checks, or limited-time multipliers that reward checking in. The paradox is real: players want automation, but total automation kills engagement. The fix is rhythmic alternation between idle accumulation and short active bursts — similar to tension-release cycles in game pacing.

Automation tiers and player agency

Automation unlocks are the genre's skill expression. Early game: player clicks manually. Mid game: auto-clickers, managers, or AI assistants buy upgrades on schedules. Late game: entire production chains run unattended.

Each automation tier should feel like a meaningful promotion, not a settings toggle. AdVenture Capitalist made managers iconic — hiring “Bob the miner” is a moment. Give automators names, flavor text, and visible animations so players attach to them.

Leave at least one optimization lever even at max automation: which generator to prioritize, when to prestige, which research branch to take. Without decisions, the game becomes a screensaver.

Monetization without breaking trust

Idle games monetize aggressively because sessions are short and whales chase speed. Common levers: time skips, offline cap extensions, permanent multipliers, cosmetic themes, and battle passes. The danger is pay-to-skip-math — when spending collapses the curve so completely that non-payers hit hopeless walls.

Ethical patterns: sell convenience (skip 4 hours, not 4 weeks), keep prestige math identical for payers and non-payers, and never gate core generators behind paywalls. Track day-1, day-7, and day-30 retention with analytics — idle games live or die on whether the second prestige feels faster than the first.

Worked example: mobile cookie factory

You are designing a mobile idle game with three generators: Ovens (manual tap + low passive), Delivery trucks (medium passive), and Factories (high passive, expensive).

• Oven — base 1 cookie/s, cost 15 × 1.10ⁿ, milestone double at levels 10, 25, 50.
• Truck — base 8 cookie/s, unlocks at 50 total ovens owned, cost 100 × 1.12ⁿ.
• Factory — base 60 cookie/s, unlocks at 10 trucks, cost 1,000 × 1.14ⁿ.

First wall: player buys 5 ovens, income is ~6/s, next oven costs ~24 — roughly 4 seconds wait. Feels fast. At 20 ovens, income ~40/s, next cost ~90 — ~2 second wait. Wall arrives when first truck costs 100 but income is only 35/s — player waits ~3 seconds, buys truck, income jumps to 43/s. First prestige unlocks at 1M lifetime cookies, awarding +5% per prestige point (sqrt scaling). Offline cap: 8 hours at 50% efficiency. Rewarded ad doubles offline claim once per session.

Playtest target: first prestige in ~45 minutes; second run to same wall in ~20 minutes. If second run is not noticeably faster, prestige math is too weak.

Genre and platform decision table

Common pitfalls

• Number notation without meaning — switching to scientific notation too early makes upgrades feel abstract; use suffixes (K, M, B, T) with clear jumps.
• Dead generators — older generators become useless after unlocking the next tier; add synergies so early generators still contribute.
• Prestige that feels mandatory too soon — if the only way past a wall is reset, players feel punished rather than empowered.
• Uncapped offline earnings — one-week absence should not trivialize a month of active design.
• No second-session hook — if day-2 income is identical to day-1, retention collapses; prestige or milestone must accelerate.
• Float precision bugs — at 1e308 cookies, JavaScript doubles overflow; use logarithms or arbitrary-precision libraries server-side.
• Automation without flavor — faceless auto-buyers feel like cheating; personify managers and celebrate unlocks.

Production checklist

• Define income and cost formulas in a spreadsheet; simulate 10 prestiges.
• Target first prestige time and verify second run is 40–60% faster.
• Set offline cap and efficiency; playtest 1-hour and 24-hour returns.
• Add at least three milestone bonus tiers per generator.
• Implement big-number handling (log storage or decimal library).
• Design one active interrupt per session (event, boss, timed boost).
• Personify automation unlocks with UI celebration.
• Track time-to-wall, prestige rate, and D1/D7/D30 retention cohorts.
• Ensure paid time skips do not exceed 24-hour equivalent of free play.
• Load-test server authority if income is validated server-side.

Key takeaways

• Idle games are progression machines built on exponential curves, automation tiers, and optional prestige resets.
• Core loop is earn → spend → accelerate → wall; milestones and prestige prevent monotony.
• Offline progress drives return visits but needs caps to protect pacing.
• Anti-idle paradox — total automation kills engagement; alternate idle accumulation with short active bursts.
• Monetization should sell convenience, not mandatory progression — prestige math must feel fair to non-payers.

Related reading

• Game monetization explained — F2P, IAP, ads, subscriptions, and ethical revenue
• Game economy design explained — sources, sinks, inflation, and currency balance
• Game player progression systems explained — XP curves, unlock trees, and prestige loops
• Game analytics and player retention explained — cohorts, churn, and live-ops tuning