game-economy-design
Skill26 starsChanged yesterdayMITView on GitHub
Covers how players earn and spend in-game currency: faucets and sinks, inflation and deflation, shop prices, loot and reward tables, crafting loops and exploit review. Use when a game needs a currency plan, drop rates or prices to tune, or a check that currency flow stays balanced.
In this repository46 other files it gives its agents.
- asaasSkill
- betterauth-integrationSkill
- bullmq-game-queuesSkill
- character-design-narrativeSkill
- ci-cd-gameSkill
- claude-agent-sdkSkill
- database-performance-tuningSkill
- elevenlabs-sound-musicSkill
- foundry-vtt-devSkill
- game-anti-cheatSkill
- game-backend-architectureSkill
- game-blenderSkill
- game-clientSkill
- game-design-fundamentalsSkill
- game-architectSkill
- game-balanceSkill
- game-buildSkill
- game-expandSkill
- game-loreSkill
- game-questSkill
- game-reviewSkill
- game-devSkill
- game-godotSkill
- game-localizationSkill
- gameplay-analyticsSkill
- game-save-loadSkill
- game-state-syncSkill
- game-unitySkill
- judgeSkill
- level-designSkill
- matchmaking-systemSkill
- mmo-designSkill
- monitoring-game-opsSkill
- nuvemshop-sdkSkill
- openclaw-genieSkill
- postgres-game-schemaSkill
- procedural-genSkill
- quest-mission-designSkill
- quest-narrative-coherenceSkill
- react-animationsSkill
- redis-game-patternsSkill
- skill-progression-treesSkill
- story-structure-gameSkill
- stripe-game-paymentsSkill
- ui-ux-gameSkill
- worldbuildingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
If inflation shows, cut the positive-sum sources or add sinks.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Game Economy Design
An economy is two choices in a loop: how players earn, and how they spend. Any tradable thing counts as money, skill points included.
Procedure
- List currencies. For each: name, how earned, how spent, what a reset does to it, cap. Copy
templates/economy-config.mdwhen you need the sheet. Its numbers are placeholders. - Map faucets. A faucet creates currency from nothing. A transfer between players is not a faucet. List every one: combat, quests, daily login, NPC buyers, insurance payouts.
- Map sinks. A sink destroys currency. Examples: shop prices (best on consumables), repair and upkeep, market taxes and broker fees, services players dislike doing (teleports priced by use), items that wear out, fees to exchange between currencies.
- Pick the model. Default to an open faucet-and-drain economy that you manage. A closed economy (fixed money) is hard to balance, sensitive to bugs and easy to gouge, and no one has built one for a large world. If the game has little persistence, ask whether it needs an economy at all.
- Choose reward form. Reward goods, not coin, where you can. Goods float with supply and demand. Fixed cash drops feel unfair once prices move. Goods inflate too: an item everyone owns is worth nothing.
- Set prices. Fixed prices work only if the money a player can hold is capped. With unbounded money, fixed prices drift toward free, and crafters who sell at fixed prices lose first.
- Pick a cost curve on purpose. Linear, exponential (1, 2, 4, 8, 16), triangular (1, 3, 6, 10, 15) or decreasing. Exponential numbers get large fast. Cost growth against income growth is your decision, so simulate it.
- Simulate before you ship. Read
boilerplate/economy-simulator.tswhen you need to check balance. Run itssimulateStageswith your per-stage faucet and sink rates, or run the file withbun boilerplate/economy-simulator.tsfor the built-in example. Fix any stage whose net flow is not where you want it. The in-memory tracker is for prototypes and tests. A live game writes each currency flow to the database (postgres-game-schema) and aggregates there. - Design drops. Use weighted tables with guaranteed drops and, where drops feel unfair, a pity counter. Copy
templates/loot-table.tswhen you need the types, including the optionalpityfield. The game keeps the counter per player. Price a conditional reward at its expected value: benefit times how often the condition holds. - Review for exploits. Assume players will find any loop that pays. Check every stack split, trade and drop path as a duplication surface. Check craft, sell and buy cycles for net gain. Cap offline and queued activity or players run mule factories.
- Add monetization last. Selling power needs very careful balancing and attracts a narrow player type. Selling time, cosmetics and convenience is the safer default. For premium currency and purchases use
stripe-game-payments.
What to track in a live game
- Total money supply, per currency (the float).
- Faucet and sink totals per source.
getTopSourceslists the biggest. - A price index over a fixed basket of goods.
- Median and mean wealth per player. A median far below the mean means a few players hold most of it.
- ARPU and ARPPU, to see whether the problem is acquisition, conversion or retention.
Watch for deflation as well as inflation. In EverQuest's Norrath, a 29-item price index fell 29 percent in one year. Set your own target ranges from playtest data. This skill gives no universal numbers.
If inflation shows, cut the positive-sum sources or add sinks.
Pitfalls
- Hyperinflation: faucets with no sinks.
- Dead economy: nothing worth buying, so currency piles up.
- Currency confusion: too many currencies.
- Duping and exploit loops: one bad stack or trade path can mint currency.
- Early abundance: players expect the early rate forever.
- Players quit rather than accept a bad market, and they gouge a market they can model. Guaranteed NPC buyers remove the reason to make what players want.
- Adjusting prices by hidden levers erodes trust. Players see the effect, not the mechanism.
- Players tune toward the optimum: given the chance, they optimize the fun out of a game. Make the optimal path fun.
Files
templates/economy-config.md: copy when you start a new economy sheet.templates/loot-table.ts: copy when you need loot table types and rarity weights.boilerplate/economy-simulator.ts: read when you need the flow tracker, inflation alerts or the stage simulation.references/sources.md: read when you need the source behind a claim.
Related skills
game-design-fundamentals (core loop), postgres-game-schema (currency and item tables), stripe-game-payments (real-money purchases), quest-mission-design (quest rewards), procedural-gen (seeded random content; this skill owns the loot table types, and the game supplies the roller).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

