Crafting Systems Are Your Game Economy's Blind Spot

Faucets and sinks are the standard vocabulary for economy design, and for good reason — most mechanics genuinely are one or the other. A quest reward is a faucet. A store purchase is a sink. The framework holds up for the majority of a typical game's economy events. It breaks down, quietly, for one specific mechanic type most games have somewhere: crafting.

Why crafting doesn't fit the binary

A crafting system takes resources the player already has and converts them into something else — raw materials into a finished item, three common cards into one rare one, scrap into a repaired weapon. That transaction consumes a resource and generates a different one in the same action. It's not purely a faucet, because it requires the player to already hold something to spend. It's not purely a sink, because it produces a real, usable output rather than simply removing value from circulation.

2026 economy-design writing has a name for this category that most faucet/sink discussions skip past: converters. A converter is a mechanic that transforms one resource into another, functioning as a source and a drain simultaneously rather than sitting cleanly on either side of the ledger. Crafting is the most common converter in strategy, construction, and simulation-style games, but the pattern shows up anywhere a game lets players combine or refine what they've collected into something new.

Why this categorization actually matters for balance

It's tempting to treat this as a naming distinction without practical consequence — log the material consumption as a sink event, log the item grant as a faucet event, and the net math still comes out correct in your total faucet-to-sink ratio. That's true for the aggregate number. It's not true for how well that aggregate number actually tells you what's happening in your economy.

A converter counted only as a sink — tracking the materials consumed without weighting what was produced — makes your economy look more drain-heavy than it actually is, because you're seeing the cost side of a transaction that also generated real value for the player. A converter counted only as a faucet — tracking the item granted without accounting for what it cost — makes the opposite mistake, understating how much of your total resource generation is actually internal recirculation rather than genuinely new value entering the system from outside.

Neither error necessarily breaks your top-line faucet-to-sink ratio, because a converter's consumption and generation partially cancel out in the aggregate math regardless of how you categorize the pieces. Where it does break something is in reading your economy's breakdown correctly. A studio looking at a chart showing faucet volume and sink volume by source, trying to understand where currency and materials are actually flowing, can badly misread a game where a large share of both the faucet total and the sink total is really the same crafting system's two halves — inflating both numbers without revealing the actual pattern underneath them.

Where this shows up as a real design mistake

The practical failure mode looks like this: a studio notices sink volume looks healthy relative to faucet volume, concludes the economy is well-balanced, and doesn't dig further. But if a meaningful chunk of that sink volume is materials feeding a crafting loop that immediately regenerates comparable value through the items produced, the actual net effect on currency accumulation is much closer to zero than the raw sink number suggests. The economy can be quietly inflating through the crafting loop's own internal recirculation while every top-line indicator looks fine, because the standard framework never separated "genuine drain" from "converter throughput" in the first place.

The reverse mistake happens too, in games where crafting is deliberately designed as a resource sink — expensive, materially costly, meant to be a genuine currency drain even though it technically produces an item at the end. Miscounting that converter as pure generation rather than acknowledging its real cost can make a studio think their economy needs more sinks when the crafting system they already have is doing exactly the sink job it was designed to do — the aggregate math just wasn't crediting it correctly.

What a genuinely useful audit looks like

Standard economy-balance guidance — scaling costs upward as players progress, adjusting drop rates based on the state of the economy — is written with pure faucets and pure sinks in mind, and it needs adaptation for a mechanic doing both at once. A converter's balance question isn't "is this generating too much" or "is this draining too much" in isolation. It's whether the ratio between what it consumes and what it produces is intentional and holding steady as players progress, since that ratio, not either side alone, determines whether the converter is a net sink, a net faucet, or genuinely neutral over time.

The practical fix is a small change to how conversion events get tagged and read, not a redesign of the crafting system itself: give converter transactions their own distinct classification in your economy data, separate from generic faucet and sink sources, so a breakdown chart can show a "conversion" slice instead of silently folding that volume into both the faucet total and the sink total. That single change turns a hidden blind spot into a visible, auditable piece of the economy — worth doing even if the converter itself turns out to be perfectly well-balanced once it's actually measured on its own terms.

The honest limit here

None of this means crafting or conversion systems are inherently risky or destabilizing — a well-tracked converter is no more dangerous to your economy than a plain faucet or a plain sink. This is a measurement-precision issue, not a design-flaw claim. A studio that's already tracking converters as their own category has nothing new to worry about here. The risk is specific to studios whose economy dashboard treats every event as strictly one or the other, because that's the exact framework a converter slips through undetected.

If your studio runs a crafting, refining, or upgrade-fusion system of any kind, it's worth a quick check: does your economy monitoring have a way to see that system's volume as its own category, or is it currently invisible inside your generic faucet and sink totals? See how gamemantra's platform approaches genre-specific economy monitoring if that check turns up a gap worth closing.