How can I adjust a game’s resource supply without changing everything at once?
Quick answer
Map each way a resource enters and leaves play, then choose one rule to adjust while keeping the others unchanged. Write down what you expect that change to do, record the relevant resource totals during play, and compare them with your starting version. Treat the result as a clue, not proof: a single play or example cannot establish how the change will work in every game.
The question, the details, the next step.
I’m designing a game and the resource supply feels off. How can I adjust it without changing several rules and losing track of what helped?
Start by drawing a small resource-flow map for one resource at a time. List every way it enters play—such as starting hands, turn income, or rewards—and every way it leaves, such as purchases, costs, or discards. Also note when each flow happens and whether it is optional. This map helps you see which rule you are actually proposing to change.
Next, pick one rule and write a testable design question. For example: “If the turn income changes from 3 coins to 2, will players have to choose more carefully between the two early purchases?” Keep prices, rewards, starting resources, and other rules as they are for that test. This is a structured comparison, not a guarantee that one play will reveal the best balance.
What should the resource-flow map look like? I want something I can fill in before testing.
Use one row for each source or sink, and keep the amount separate from the rule that creates it. Here is a hypothetical example for coins; the figures are placeholders, not recommendations:
Resource: Coins
Starting amount: 4 per player
Enters: 2 coins at the start of each turn
Enters: 1 coin for completing a task
Leaves: 3 coins to buy a tool
Leaves: 1 coin to reroll
Timing or conditions: task reward is optional; purchase occurs during a turn
Question to examine: Does regular income make the task reward feel unnecessary?If a rule changes based on player count, a choice, or a game event, record that condition too. If you are unsure whether an action creates or removes resources, write down the rule as stated in your current design rather than guessing at its effect. The map describes the system; it does not by itself show whether players find it enjoyable.
How do I make the change and compare it fairly with the original version?
Save a copy of the current rules as your baseline. In the test copy, change only the selected supply rule—for the example, turn income would become 1 coin instead of 2. Keep a short log with the version, the exact edit, your reason, and what you noticed. Use the same player count and setup when practical, and note anything that differed; you cannot control every difference between plays.
For example:
Version: B
Change: Turn income is 1 coin instead of 2
Design question: Will players value task rewards more?
Keep unchanged: starting coins, prices, task rewards
Record: coins held before purchases; purchases made; turns when a player could not afford a chosen tool
Observation: [write what happened, without explaining it yet]
Next decision: [keep, revise, or restore the rule, and why]Track a few observations tied to your question rather than every possible detail. If the result surprises you, check whether another rule or event could explain it before changing anything else.
What if the change seems better but I’m not sure it was the cause?
Treat that as a reason to run another comparison, not as proof. First check your log: did the test use the same setup, and did anything else change? Then repeat the baseline and adjusted versions under similar conditions if you can. Note whether the same kind of observation appears again, and record exceptions as well as examples that fit your expectation.
If the result is mixed, you might have found a trade-off—for instance, fewer coins could make rewards matter more while also delaying a purchase. Decide which part of the experience your design question is about, and choose a next test that isolates that part. Keep old versions so you can restore them. This process helps you reason clearly about a design; it cannot establish a universal answer from a small number of plays.
A practical checklist
List every way the resource enters and leaves play, including timing and conditions.
Save the current rules as a baseline before editing.
Write one design question and change only the rule that question concerns.
Keep setup and other rules consistent where practical; note differences.
Log relevant observations, surprises, and the next decision.
Repeat or restore the baseline when the result is unclear.
A few more useful answers
Should I change a resource source or a resource cost first?
Use your map to identify which rule is most directly connected to your design question, then test that rule alone. There is no universally correct first choice.
How many plays are enough to decide?
There is no fixed number that guarantees a reliable conclusion. Repeat comparisons when practical, note differences between plays, and treat the log as evidence to consider rather than proof.
What should I do if two resource rules seem to interact?
Test each rule separately first to get a clearer view of each change. If needed, test a combined change afterward and label it as a separate version.