Game economy design faucets sinks

A game economy breaks when players either run out of currency and stall, or accumulate so much that nothing feels earned — and both failures are invisible until players quit. Faucets are every source of currency in your game: quest rewards, loot drops, crafting outputs, daily bonuses. Sinks are everything that drains it: upgrades, consumables, cosmetics, repair costs, fast-travel fees. The job of economy design is keeping those two sides in balance so that player wealth grows at a rate that feels rewarding without outpacing the content that demands spending.

What Are Faucets and Sinks, Really?

A faucet is any system that creates currency from nothing — it is a net injection into your economy. A sink is any system that destroys currency permanently. The critical distinction is “permanently.” A player trading gold to another player is not a sink; the gold still exists in the economy. A player paying 500 gold to repair gear and that gold disappearing from the system — that is a sink. In a single-player game you control the entire supply, so the math is simpler. In multiplayer, every transaction between players is a zero-sum transfer, and your actual economy health is determined only by injections versus destructions. I have seen studios accidentally build zero sinks into a multiplayer game and wonder why their auction house collapsed inside two weeks.

Soft Currency, Hard Currency, and Premium Currency — Why Split Them?

Most economy designs use at least two currencies for good reason. Soft currency (gold, credits, whatever you call it) is earned through normal play and spent on core progression. Hard or premium currency is scarce — gated by real money, extreme effort, or rare drops — and reserved for high-value items so that players feel the weight of each spend decision. If you collapse everything into one currency, you lose the ability to tune spending pressure independently for each player segment. A player who grinds eight hours a day and a player who plays thirty minutes a week need different economic experiences, and split currencies let you design for both. Adding a third “prestige” or “endgame” currency is fine if it maps to a real late-game economy layer, but every currency you add is a UI burden and a tuning surface that can break independently.

How Does Inflation Actually Happen in a Game Economy?

Inflation happens when faucets outpace sinks over time. The early-game sword that cost 200 gold at launch feels free by week three if players are earning 500 gold per hour and you never added proportional sinks. The symptom is that prices lose psychological weight — players stop caring about currency at all, which means rewards stop mattering, which means progression feels flat. The root cause is almost always that faucet rates were tuned against a vertical slice where players had limited content, and then the live game provided far more earning opportunities than the design assumed. The fix — retroactively adding sinks or nerfing drop rates — is always painful and usually breeds community backlash. Tune sinks aggressively from the start and you can loosen them later; doing it in reverse is much harder.

Single-Player vs. Multiplayer Economy — Where the Concerns Diverge

In a single-player game, the economy is a pacing tool. You are tuning how long a player sits in a tier before they can afford to move on, and the main failure mode is either gating too hard (grind wall) or too loose (nothing costs anything so nothing is interesting). Player-to-player trading does not exist, so you cannot get runaway inflation from external arbitrage. In multiplayer, the economy is a social system that players will probe for exploits the moment it goes live. Gold duplication bugs, farming bots, arbitrage between regions, price manipulation — all of these are real attack surfaces. Multiplayer economy design requires rate limiting on faucets (daily caps, diminishing returns on repeated content), robust sinks tied to competitive progression so high-level players are constantly draining wealth, and ideally a data pipeline so you can watch the aggregate supply curve in real time and respond. At Sinfull Studios, working in single-player Unreal projects, I design economies with explicit spreadsheet models before a single Blueprint node gets placed — knowing that the single-player version is forgiving but building that discipline now matters if anything ships in a connected context.

How Do You Actually Tune Player Wealth Pacing?

Start with a target earn rate per hour at each progression tier, then price every meaningful sink as a multiple of that rate. A common rule of thumb: a major upgrade should cost roughly 2–4 hours of focused earning at the tier where it is relevant. That creates a spend decision that feels significant without being a grind wall. Then model what happens if a player skips all optional content, and what happens if they do everything — the earn rate spread between those two playstyles defines your economy’s tolerance band. If a completionist earns 10x what a critical-path player earns, your sinks need to scale with engagement or your completionist players will run out of things to spend on. Data assets and a data-driven tuning layer in Unreal (whether that is a spreadsheet pipeline into a DataTable, or a more formal GAS-adjacent system) are worth the setup cost because they let you adjust values without code builds.

What Are the Most Common Economy Design Mistakes?

  • No sinks in the early economy — players accumulate currency that has no pressure valve, then feel nothing when prices appear later.
  • Sinks tied to content players can avoid — if the only meaningful sink is PvP repair costs and half your players skip PvP, half your economy has no drain.
  • Currency that cannot be spent at a given tier — earning hard currency before the shop that accepts it exists is a frustrating UI problem that reads as a broken economy.
  • Tuning faucets against internal QA playthroughs — QA players never play at live-game pace or volume; always model against your expected player percentiles.
  • Adding a new currency to solve a problem that a well-placed sink would fix — more currencies rarely solve balance issues, they just move them.

Why Does a Broken Economy “Quietly” Ruin Progression?

Because players rarely articulate it as an economy problem. They say the game “feels grindy” or “feels pointless” or “nothing matters.” Those are economy symptoms. When a player is always broke, every reward feels inadequate and every upgrade feels out of reach — that is a sink-heavy or low-faucet problem. When a player is always flush, purchase decisions disappear, and with them goes the pleasure of saving toward something. The economy is the invisible scaffolding under the progression system; when it works, players do not notice it. When it breaks, they just stop playing and write a Steam review about pacing. Catching it requires actually modeling the numbers before launch, not reacting to reviews afterward. The design is also largely invisible in marketing — nobody ships a trailer showcasing their sink tuning — which means it is chronically underprioritized until it is too late to fix cleanly.

What Is a Practical Starting Point for a Solo Developer?

Build a spreadsheet before you build the system. Define your currencies, list every faucet with an estimated output per hour of play, and list every sink with its cost and expected purchase frequency. Sum the columns. If faucets outpace sinks at any tier, you have inflation risk — add a sink or reduce a faucet before a single line of implementation. In Unreal, put every economy value in DataTables so you can adjust without recompiling. Add a debug HUD that shows current player wealth, total earned, and total spent — you will need it during playtesting. And treat your first playtest economy numbers as wrong by definition; build the instrumentation to see where they are wrong before you commit to them. The economy is not a feature you finish; it is a system you monitor and adjust for the life of the game. If you treat it as a one-time design decision, it will break quietly and take your retention numbers with it.

Explore Game Development with Unreal Engine at Sinfull Studios for more.

Frequently Asked Questions

What is the difference between a faucet and a sink in game economy design?

A faucet is any system that creates currency from nothing — quest rewards, loot drops, crafting outputs — injecting wealth into the economy. A sink is any system that permanently destroys currency, such as upgrade costs, repair fees, or consumables. Healthy economy design keeps these two forces in balance so player wealth grows at a rate that feels rewarding without outpacing the game’s spending demands.

Why do game economies cause inflation and how can you prevent it?

Inflation happens when faucets outpace sinks over time — players accumulate more currency than the game gives them meaningful ways to spend. The most common cause is that earn rates were tuned against early playtests and did not account for the earning volume of live players with access to all content. Preventing it requires modeling faucet and sink totals in a spreadsheet before implementation, aggressively tuning sinks from launch (it is easier to loosen them later than to add them retroactively), and using data-driven value tables so adjustments do not require code builds.

How does economy design differ between single-player and multiplayer games?

In a single-player game, the economy is a pacing tool — you control the entire supply and the main failure modes are grind walls or trivial cost structures. In multiplayer, the economy is a social system exposed to arbitrage, bots, duplication exploits, and player-driven price manipulation. Multiplayer economies require rate limiting on faucets (daily caps, diminishing returns), sinks tied to competitive progression so high earners are constantly draining wealth, and live monitoring of the aggregate supply curve to catch runaway inflation before it damages the game’s marketplace.

Related reading from Sinfull Studios

Sinfull Studios builds games in Unreal Engine from Regina, Saskatchewan. Have a project or a question? Get in touch.