You are responsible for a comprehensive **progression, economy, rewards, combat-balance, and resource-flow audit and tuning pass**.

Your job is to make the existing game's advancement and economic systems feel:

- rewarding;
- coherent;
- sustainable;
- internally understandable;
- appropriately paced;
- resistant to obvious exploits;
- worthwhile across different progression stages;
- free from obvious dead content;
- free from unintended dominant strategies;
- professionally tuned rather than arbitrarily configured.

The primary question throughout this task is:

> **Where do the game's numbers, rewards, costs, progression requirements, resource flows, or relative power relationships create boring, broken, exploitable, pointless, frustrating, or obviously unintended outcomes?**

Then fix those problems.

This is an **implementation task**, not merely a balance analysis.

Do not stop after:

- calculating curves;
- identifying overpowered items;
- identifying weak rewards;
- producing economy diagrams;
- recommending number changes;
- creating spreadsheets;
- writing a balance report;
- generating a tuning backlog.

Inspect the actual implemented systems and data.

Model relevant progression and resource flows.

Identify concrete balance problems.

Prioritize them by player impact.

Implement justified corrections.

Validate the resulting progression and economy.

Reassess.

Continue while meaningful, evidence-supported improvements remain.

The goal is:

> **Make the existing game's progression and economy feel deliberately tuned, rewarding over time, internally coherent, and resistant to obvious degenerate strategies without flattening meaningful choices or system identity.**

---

# Balance Does Not Mean Equality

Do not assume:

- every weapon should have identical DPS;
- every skill should level at the same speed;
- every activity should produce equal profit;
- every item should be equally useful;
- every combat style should perform identically;
- every resource should have equal rarity;
- every recipe should have equal efficiency;
- every progression path should take the same amount of time.

Interesting games often depend on asymmetry.

The important question is:

> **Does this difference create meaningful identity, tradeoff, pacing, risk, convenience, or strategic choice?**

or:

> **Is this merely an accidental numerical imbalance?**

Preserve intentional asymmetry.

Fix accidental imbalance.

---

# Core Scope

This pass may cover the following systems when they actually exist.

## Progression

- XP curves;
- levels;
- ranks;
- skill progression;
- account progression;
- unlock pacing;
- equipment progression;
- combat progression;
- recipe progression;
- numeric quest progression;
- area requirements;
- level gates;
- milestone rewards;
- early-game pacing;
- midgame pacing;
- late-game pacing.

## Economy

- currency creation;
- currency sinks;
- item creation;
- item destruction;
- resource generation;
- resource consumption;
- vendor prices;
- buy/sell relationships;
- crafting inputs;
- crafting outputs;
- repair costs;
- travel costs;
- transaction costs;
- player trading where applicable;
- markets where applicable;
- drop value;
- loot value.

## Combat Balance

- damage;
- accuracy;
- defense;
- health;
- attack speed;
- cooldowns;
- resource costs;
- enemy scaling;
- weapon progression;
- armor progression;
- combat-style relationships;
- ability power;
- status effects;
- encounter rewards.

## Gathering / Skilling

- gathering speed;
- resource rarity;
- XP rates;
- depletion;
- respawn;
- tool progression;
- output value;
- effort versus reward;
- processing efficiency;
- active versus relaxed/AFK methods.

## Crafting / Production

- ingredient cost;
- output value;
- XP;
- recipe unlock level;
- production speed;
- failure chance where applicable;
- profitable versus loss-making recipes;
- item utility;
- processing ratios.

## Rewards

- loot tables;
- quest rewards;
- achievement rewards;
- level-up rewards;
- rare drops;
- currency rewards;
- XP rewards;
- unlocks;
- progression milestones.

Only audit systems that actually exist.

---

# Explicitly Out of Scope

This is **not primarily**:

- a gameplay feature sprint;
- a combat-system redesign;
- a new economy system;
- a new crafting system;
- visual polish;
- UI redesign;
- environment design;
- technical-debt cleanup;
- repository cleanup;
- performance optimization;
- persistence architecture;
- multiplayer architecture;
- content expansion.

Small code or data changes are allowed when necessary to implement a justified balance correction.

Do not use balance work as an excuse to redesign whole systems.

If a serious problem requires major structural redesign, record it separately unless the redesign is directly necessary to correct a severe confirmed balance failure.

---

# Preserve the Game's Intended Identity

Before tuning numbers, determine what the game appears to value.

Possible intended qualities may include:

- long-term progression;
- relaxed progression;
- grind;
- scarcity;
- high-risk/high-reward play;
- accessible combat;
- difficult combat;
- profitable specialization;
- player trading;
- self-sufficiency;
- prestigious rare drops;
- deterministic crafting;
- randomized loot;
- active gameplay;
- relaxed or AFK gameplay.

Use evidence from:

- existing values;
- documentation;
- game descriptions;
- progression structure;
- item design;
- established mechanics;
- existing high-quality systems;
- tests;
- actual gameplay where available.

Do not impose a preferred pacing philosophy without evidence.

The purpose is to make the existing game better tuned, not transform it into a different progression philosophy.

---

# Preserve Existing Product Behavior Where Appropriate

Balance work necessarily changes some gameplay values.

However, do not casually alter:

- core gameplay rules;
- combat models;
- progression structure;
- resource ownership;
- persistence semantics;
- multiplayer authority;
- item identity;
- existing content roles;

unless the change is justified by a confirmed balance issue.

Prefer targeted tuning over broad redesign.

---

# Do Not Balance by Intuition Alone

Use quantitative evidence wherever practical.

Possible metrics include:

- XP per action;
- XP per minute/hour;
- actions per level;
- time-to-level;
- time-to-unlock;
- kills per hour;
- damage per second;
- expected damage;
- time-to-kill;
- effective health;
- resources per hour;
- currency generation per hour;
- currency destruction per hour;
- crafting cost;
- crafting margin;
- expected loot value;
- expected attempts;
- expected acquisition time;
- resource-consumption rates;
- vendor arbitrage;
- drop probabilities;
- relative power per requirement level;
- reward per unit of risk;
- reward per unit of attention.

Exact simulation is not always necessary.

But major balance conclusions should normally be explainable numerically.

Do not invent precision that the available data cannot support.

---

# Player Experience Still Matters

Numbers alone do not determine balance.

A mathematically equal outcome may not represent equal player cost.

Consider:

- effort;
- attention;
- danger;
- setup;
- travel;
- downtime;
- interaction frequency;
- skill requirement;
- equipment requirement;
- resource consumption;
- convenience;
- opportunity cost;
- execution difficulty;
- failure risk.

For example, two activities may both produce the same currency per hour.

But if one is:

- safe;
- low-attention;
- unlocked early;
- resource-free;

while the other is:

- dangerous;
- high-attention;
- unlocked late;
- expensive to operate;

they are not necessarily equally rewarding.

Balance:

> **total player investment against total player benefit**

rather than comparing one isolated metric.

---

# Inspect Before Asking Questions

Use the project itself as evidence before asking for clarification.

Inspect relevant:

- gameplay data;
- configuration;
- item definitions;
- enemy definitions;
- XP tables;
- formulas;
- loot tables;
- vendors;
- recipes;
- progression requirements;
- unlock data;
- skill definitions;
- combat calculations;
- runtime behavior;
- tests;
- documentation;
- authoritative server logic where applicable.

Ask for clarification only when:

- intended progression philosophy genuinely cannot be established;
- several materially different tuning goals are equally plausible;
- a major live-economy change would affect existing players;
- player holdings or telemetry are required to make a safe decision;
- irreversible progression migration is involved;
- a product decision is required.

Do not ask questions merely because quantitative analysis takes effort.

---

# Implementation Over Spreadsheet Production

Analysis exists to produce an **implementation queue**.

Do not spend most of the task building giant spreadsheets, simulations, or diagrams.

Once sufficient evidence establishes a real balance problem:

1. identify root cause;
2. determine the smallest effective adjustment;
3. implement it;
4. recalculate or retest;
5. inspect downstream consequences.

Use:

> **measure → compare → identify imbalance → tune → validate → compare again**

---

# Establish the Progression Map

Identify major progression systems.

Depending on the game, these may include:

- character level;
- combat levels;
- skills;
- equipment tiers;
- crafting tiers;
- quest gates;
- zones;
- abilities;
- recipes;
- reputation;
- technology;
- account unlocks.

Determine how these systems relate.

Ask:

> **What does the player become meaningfully capable of doing as progression advances?**

Map important dependency chains.

Examples:

> skill level → resource → production → equipment → combat access

or:

> quest → area → enemy → drop → crafting unlock

Use the actual project rather than assuming a generic structure.

---

# Establish the Economy Map

Map major economic sources and sinks.

For each meaningful currency or resource identify:

## Sources

How does it enter circulation?

Examples:

- monster drops;
- gathering;
- quests;
- vendors;
- crafting;
- achievements;
- daily/periodic rewards;
- player trades.

## Sinks

How does it leave circulation?

Examples:

- purchases;
- crafting;
- repairs;
- consumables;
- travel;
- taxes;
- upgrades;
- destruction;
- irreversible transformation.

Not every item needs a permanent sink.

Not every currency must maintain perfect equilibrium.

But major resources should not accumulate or disappear accidentally.

Match the analysis to the actual game.

A single-player economy and a persistent multiplayer economy have fundamentally different long-term concerns.

---

# Establish Representative Progression Slices

Divide progression into representative stages.

For example:

## Early

Ask:

- What are the main player goals?
- What upgrades matter?
- How quickly does advancement occur?
- Is the player starved of necessary resources?
- Are early upgrades meaningful?

## Mid

Ask:

- What options open?
- What activities become efficient?
- Which resources matter?
- Are multiple meaningful paths available?
- Does crafting remain relevant?

## Late

Ask:

- What goals remain?
- Are upgrades still meaningful?
- Do costs and sinks still matter?
- Are high-level activities worth engaging with?
- Does progression remain sustainable?

Use the game's actual structure instead of forcing arbitrary thirds.

Look for discontinuities between stages.

---

# Execution Strategy

Work autonomously where possible.

If the environment supports parallel agents, workers, subprocesses, or independent contexts, use them where they materially improve analysis.

Do not require delegation.

A single capable session must still be able to execute the prompt sequentially.

Good independent analytical areas may include:

- XP progression;
- combat;
- gathering;
- crafting;
- vendors;
- loot;
- enemy scaling;
- economy sources/sinks.

Serialize changes when several systems depend on the same:

- XP curve;
- currency;
- item tier hierarchy;
- damage formula;
- crafting economy;
- shared loot model;
- progression gate.

Do not allow independent tuning workstreams to optimize interconnected systems toward contradictory targets.

Centralize final tuning decisions.

---

# Balance Priority Queue

## P0 — Exploit / Catastrophic Economic Problem

Examples:

- infinite currency generation;
- guaranteed vendor buy/sell profit loop;
- legitimate item duplication;
- repeatedly claimable reward;
- negative cost;
- progression bypass;
- arithmetic overflow producing extreme values;
- reversible conversion producing unlimited value.

Fix immediately.

## P1 — Major Progression Failure

Examples:

- one strategy massively dominates intended alternatives;
- important progression tier is pointless;
- severe progression wall;
- severe XP discontinuity;
- low-level activity beats intended high-level content without compensating tradeoff;
- impossible enemy scaling jump;
- major currency becomes functionally meaningless;
- key progression path deadlocks.

Prioritize heavily.

## P2 — Significant Balance Problem

Examples:

- one weapon family consistently underperforms;
- one skill progresses disproportionately slowly;
- crafting tier is economically irrational;
- obvious reward outlier;
- weak milestone;
- equipment upgrade provides negligible benefit;
- risk and reward are badly disconnected.

Spend substantial effort here.

## P3 — Minor Tuning

Examples:

- small adjacent-tier irregularity;
- modest loot adjustment;
- minor XP anomaly;
- small pricing inconsistency;
- small stat outlier.

Address after larger issues.

---

# XP Curve Pass

Inspect progression curves.

Calculate where useful:

- XP required per level;
- cumulative XP;
- percentage increase between levels;
- representative actions required;
- estimated time;
- unlock positions.

Look for:

- accidental spikes;
- suspiciously flat regions;
- impossible values;
- abrupt pacing cliffs;
- late levels requiring negligible additional effort;
- early levels taking disproportionately long;
- duplicated thresholds;
- broken formulas.

Do not automatically smooth every curve.

Exponential or intentionally uneven progression can be appropriate.

The question is whether the curve supports intended pacing.

---

# Time-to-Level Analysis

For major progression systems, estimate practical time-to-level at representative points.

Evaluate:

- early;
- mid;
- late;
- endgame.

Use representative available activities.

Ask:

> **Does the progression curve match the game's intended pacing?**

Compare sibling skills where useful.

Do not require identical rates.

Different skills may justify different pacing based on:

- attention;
- profit;
- risk;
- input scarcity;
- AFK potential;
- utility;
- prestige.

---

# XP Source Comparison

For each progression family compare available XP sources.

Look for:

- one activity dominating all alternatives;
- high-level activities giving worse XP than low-level activities with no compensating value;
- newly unlocked content immediately becoming obsolete;
- unlocks providing no useful progression advantage;
- activities producing disproportionately strong XP and profit simultaneously.

Preserve alternative methods with meaningful tradeoffs.

The best XP activity does not also need to be the best profit activity.

---

# Unlock Cadence

Inspect how often progression produces meaningful unlocks.

Possible unlocks include:

- equipment;
- resources;
- areas;
- recipes;
- abilities;
- quests;
- activities.

Look for:

- long dead stretches;
- several redundant unlocks clustered together;
- unlocks already obsolete when acquired;
- requirements placed after the content would have been useful.

Do not invent major new content.

If existing underused content can safely improve a gap, consider making it relevant.

---

# Early-Game Progression

Inspect:

- grind before first meaningful upgrades;
- resource starvation;
- equipment gaps;
- excessively slow early levels;
- early rewards that become obsolete immediately;
- requirements that delay basic progression unnecessarily.

Do not turn this into an onboarding or tutorial redesign.

Focus on numerical pacing and resource availability.

---

# Midgame Progression

Look for:

- repetitive dominant activities;
- missing equipment steps;
- crafting becoming irrelevant;
- currency becoming excessively abundant;
- severe resource bottlenecks;
- long stretches without meaningful goals;
- poor progression between early and late content.

Midgame is often where disconnected systems become most obvious.

---

# Late-Game Progression

Inspect whether late progression provides:

- meaningful goals;
- worthwhile upgrades;
- sustainable resource use;
- reasonable reward rates;
- meaningful specialization;
- appropriate prestige.

Do not trivialize endgame merely because values become large.

Do not assume infinitely increasing grind is automatically desirable.

---

# Progression Wall Hunt

Look for points where required effort rises dramatically without corresponding:

- unlock;
- reward;
- choice;
- power;
- prestige;
- new activity.

Not every grind increase is a problem.

Investigate cliffs that appear unsupported.

---

# Progression Compression Hunt

Search for mechanics that unintentionally skip major intended progression.

Examples:

- cheap high-tier vendor item;
- powerful low-requirement drop;
- missing recipe requirement;
- reward granting advanced equipment too early;
- requirement check missing on one acquisition route.

Fix confirmed unintended shortcuts.

Do not remove intentional alternative progression.

---

# Progression Gate Audit

Inspect requirements such as:

- levels;
- quests;
- items;
- currency;
- reputation;
- area unlocks.

Look for gates that:

- require content unlocked after the gate;
- are impossible;
- are meaningless;
- create abrupt pacing cliffs;
- duplicate another requirement unnecessarily.

---

# Circular Progression Check

Search for impossible dependency loops.

Example:

> need item A to acquire resource B → need resource B to create item A

Determine whether alternate acquisition exists.

If no valid path exists, progression is deadlocked.

Fix confirmed loops.

---

# Milestone Value

Major milestones should usually matter.

Examples:

- notable level thresholds;
- new equipment tier;
- new area;
- boss completion;
- major skill threshold.

Look for milestones heavily emphasized by the game that provide negligible benefit.

Do not invent rewards without project support.

Use existing content when possible.

---

# Equipment Tier Pass

Compare neighboring equipment tiers.

For weapons inspect:

- damage;
- speed;
- accuracy;
- range;
- special properties;
- requirements;
- acquisition difficulty;
- operating cost.

For armor inspect:

- defense;
- mitigation;
- resistances;
- penalties;
- requirements;
- cost.

Ask:

> **Does upgrading usually provide a meaningful but not absurd improvement?**

Intentional sidegrades are valid.

Later equipment does not need to strictly dominate every earlier item.

---

# Adjacent Tier Analysis

Compare progression ladders incrementally.

For example:

> T1 → T2 → T3 → T4

Do not compare only the weakest and strongest tiers.

Many balance problems exist between neighbors:

- one tier barely improving;
- one tier jumping dramatically;
- requirement spikes;
- acquisition difficulty not matching benefit;
- old tier remaining better unintentionally.

---

# Dead Item Hunt

Search for items with no plausible reason to use.

Possible causes:

- strictly inferior stats;
- higher requirements with lower benefit;
- excessive crafting cost;
- obsolete immediately when unlocked;
- no recipe use;
- no vendor value;
- universally superior alternative available at the same stage.

First determine whether the item is intentionally:

- cosmetic;
- collectible;
- quest-specific;
- niche;
- transitional;
- sidegrade.

Fix only truly dead gameplay content.

---

# Dominant Item Hunt

Search for items making intended alternatives irrational.

Ask:

- Is it too powerful?
- Too cheap?
- Too easy to acquire?
- Too broadly useful?
- Missing an intended drawback?
- Available too early?

Do not nerf an item merely because it is a logical upgrade.

Dominance becomes a problem when it collapses intended choice.

---

# Trap Choice Hunt

Identify options that appear legitimate but are catastrophically worse without a meaningful niche.

Examples:

- weapon doing dramatically less damage with no compensation;
- recipe destroying large value for negligible XP;
- high-level activity worse than low-level version in every relevant dimension;
- expensive consumable strictly inferior to cheaper one.

Fix the underlying mismatch or restore the intended tradeoff.

---

# Combat DPS Pass

For relevant combat options calculate expected output.

Consider:

- base damage;
- attack speed;
- accuracy;
- cooldown;
- resource cost;
- range;
- status effects;
- utility.

Do not compare only raw maximum hit.

Evaluate expected performance over time.

---

# Attack-Speed Normalization

When weapons have different speeds, compare damage over time.

Inspect whether:

- slow weapons are accidentally strictly worse;
- fast weapons multiply flat bonuses disproportionately;
- status effects scale unintentionally with hit frequency;
- per-hit resource costs distort expected efficiency;
- attack-speed differences create unintended proc dominance.

---

# Accuracy / Defense Pass

Inspect hit probability relationships.

Look for:

- accuracy effectively irrelevant;
- defense effectively irrelevant;
- severe thresholds causing sudden impossibility;
- equipment upgrades providing no meaningful hit-rate benefit;
- formulas saturating too early.

Use expected outcomes rather than isolated stats.

---

# Effective Health Analysis

Where relevant, compare survivability using:

- health;
- mitigation;
- defense;
- evasion;
- resistances;
- healing.

Do not balance only around raw HP.

Estimate practical time-to-defeat under representative conditions.

---

# Enemy Difficulty Curve

Map representative enemies across progression.

Inspect:

- health;
- damage;
- accuracy;
- defense;
- mechanics;
- reward;
- requirements;
- intended player tier.

Look for:

- sudden difficulty cliffs;
- later standard enemies being easier than earlier equivalents without purpose;
- reward disconnected from difficulty;
- enemies requiring substantially better gear without improved payoff.

Preserve intentional bosses, elites, and special encounters.

---

# Risk Versus Reward

Compare activities by:

- danger;
- attention;
- travel;
- equipment risk;
- resource consumption;
- difficulty;
- failure probability;

against:

- XP;
- loot;
- currency;
- progression;
- unique rewards.

Riskier content should generally provide some reason to engage with it.

That reason does not need to be maximum raw profit.

---

# Combat Style Balance

If multiple combat styles exist, compare relevant:

- melee;
- ranged;
- magic;
- abilities;
- special systems.

Evaluate total value:

- DPS;
- range;
- safety;
- mobility;
- utility;
- equipment cost;
- consumable cost;
- convenience;
- target access.

Do not force identical DPS.

Examples of legitimate tradeoffs:

- ranged may pay ammunition cost for safety;
- magic may pay resource cost for utility;
- melee may provide lower operating cost but greater positional risk.

Balance total value.

---

# Cooldown Balance

Inspect abilities with cooldowns.

Compare:

- effect;
- damage;
- duration;
- utility;
- resource cost;
- cooldown;
- risk;
- opportunity cost.

Avoid abilities that are:

- always correct to use immediately;

or:

- never worth using;

unless that role is clearly intentional.

---

# Resource-Cost Balance

For resources such as:

- ammunition;
- mana;
- stamina;
- reagents;
- consumables;

compare operating cost against benefit.

High-cost styles should have compensating value.

Do not make resource costs irrelevant without design evidence.

---

# Consumable Balance

Inspect relevant:

- healing;
- buffs;
- food;
- potions;
- ammunition;
- temporary boosts.

Compare:

- effect;
- cost;
- availability;
- requirement;
- inventory burden;
- cooldown/action cost.

Look for one cheap consumable making intended alternatives obsolete.

---

# Healing Economy

Where healing consumables exist, compare healing per:

- item;
- inventory slot;
- cost;
- acquisition time;
- action/cooldown where relevant.

Do not reduce the entire decision to one ratio when different consumables have distinct roles.

---

# Gathering Rate Pass

Measure representative resource generation.

Consider:

- node availability;
- travel;
- depletion;
- respawn;
- tool quality;
- success chance;
- inventory limitations;
- attention requirements.

Compare generation against actual downstream consumption.

A resource economy cannot be judged only by acquisition speed.

---

# Gathering XP Pass

Compare XP rates across resource tiers.

Ask:

- Does progressing into higher-tier resources generally provide appropriate value?
- Are higher-tier resources intentionally worse XP but more valuable economically?
- Are lower-tier resources intended as training methods?
- Does the tradeoff make sense?

Do not require the best XP and best economic reward to come from the same resource.

---

# Tool Progression

Inspect tools such as:

- pickaxes;
- axes;
- fishing tools;
- harvesting tools;
- production tools.

Compare upgrade benefit against:

- requirement;
- acquisition difficulty;
- cost.

A tool upgrade should usually matter.

Avoid tiers that exist numerically but create imperceptible benefit.

---

# Resource Scarcity

Inspect how frequently important resources enter the game.

Look for resources that are:

- so abundant they lose purpose;
- so scarce they block intended progression;
- generated almost exclusively by an unintended activity;
- bottlenecked far beyond downstream consumption;
- generated far beyond any plausible use.

Scarcity should support intended progression.

---

# Resource Sink Pass

For important generated resources ask:

> **What consumes this?**

Potential sinks include:

- crafting;
- consumables;
- upgrades;
- repairs;
- construction;
- vendors;
- irreversible transformations.

Not every resource needs a permanent sink.

But large mismatches between generation and consumption deserve investigation.

---

# Gathering → Production Chain Review

Trace important chains.

Examples:

> ore → bar → weapon

> logs → components → equipment

> fish → cooked food

For each chain consider:

- gathering time;
- processing time;
- XP;
- conversion ratios;
- output utility;
- required levels;
- economic value.

Look for:

- impossible bottlenecks;
- useless intermediate materials;
- bizarre conversion ratios;
- progression tiers that do not line up.

---

# Processing Yield

Where raw resources become processed resources, inspect:

- conversion ratios;
- failure rates;
- bonus output;
- XP;
- downstream requirements.

Ensure downstream demand broadly makes sense relative to upstream supply.

---

# Crafting Recipe Audit

For important recipes compare:

- input value;
- output value;
- XP;
- production time;
- requirements;
- utility;
- alternative acquisition.

Look for:

- heavily loss-making recipes with no progression purpose;
- output worth dramatically less than ingredients without compensation;
- free value loops;
- recipes no rational player would use;
- recipes unlocked after their output becomes irrelevant.

Some loss-making training recipes may be intentional.

Evaluate their role.

---

# Crafting Progression

Inspect whether higher crafting levels provide:

- useful recipes;
- meaningful efficiency;
- worthwhile outputs;
- access to better or more specialized products.

Look for tiers containing little reason to progress.

Do not invent a new crafting system.

Tune existing progression.

---

# Drop Versus Craft Balance

When items can be both crafted and obtained through drops, compare the acquisition routes.

Crafting does not always need to be:

- cheaper;
- faster;
- stronger.

Drops may be:

- prestigious;
- rare;
- convenient.

But avoid a crafting system whose main outputs are universally trivial to obtain elsewhere.

---

# Vendor Price Audit

Inspect:

- buy prices;
- sell prices;
- spreads;
- same-item pricing across vendors;
- related item relationships.

Search aggressively for:

> **buy low → sell high → guaranteed unlimited profit**

unless merchant arbitrage is an explicit intended mechanic.

---

# Vendor Arbitrage Hunt

Where data permits, programmatically compare:

- identical items across vendors;
- crafting ingredient/output prices;
- currency conversion rates;
- bulk behavior;
- buyback behavior;
- reversible transactions.

Treat infinite risk-free currency loops as P0.

---

# NPC Vendor Role

Determine what each vendor is intended to do.

Possible roles:

- primary acquisition;
- convenience;
- price floor;
- currency sink;
- beginner supply;
- emergency fallback.

Tune pricing relative to purpose.

Do not blindly match NPC prices to player-market value.

---

# Currency Source Pass

Map major currency sources.

Estimate relative contribution from:

- combat;
- quests;
- selling;
- gathering;
- production;
- activities;
- recurring rewards.

Look for one unintended source overwhelming all others.

---

# Currency Sink Pass

Map major sinks such as:

- vendors;
- repairs;
- crafting fees;
- travel;
- upgrades;
- services;
- taxes.

Ask whether currency enters substantially faster than meaningful systems remove it.

Interpret this according to the product.

Persistent economies require more scrutiny than finite single-player economies.

---

# Inflation Review

For persistent multiplayer economies, estimate:

> **currency created per active player over time**

against:

> **currency destroyed per active player over time**

Exact equilibrium is not required.

But unchecked perpetual creation deserves scrutiny.

Do not make major live-economy corrections casually.

Existing player wealth may make apparently simple balance changes consequential.

---

# Item Faucet / Sink Review

For tradeable persistent items identify:

- generation;
- destruction;
- consumption;
- binding;
- loss;
- replacement.

Consumables naturally leave circulation.

Permanent equipment may accumulate indefinitely.

That may be acceptable.

Do not invent artificial destruction merely because an item lacks a sink.

---

# Loot Table Audit

For important drop tables inspect:

- probability;
- quantity;
- expected value;
- rare rewards;
- progression relevance.

Check for:

- invalid probability totals;
- unreachable entries;
- duplicated entries;
- accidentally guaranteed high-value drops;
- absurd expected values;
- rewards inappropriate to difficulty.

---

# Expected Loot Value

Calculate expected value where useful:

> **expected value = Σ(probability × value)**

Use the most meaningful value available:

- vendor value;
- crafting replacement value;
- acquisition cost;
- stable market value where actual reliable data exists.

Do not invent precise market value where none is available.

---

# Rare Drop Review

For rare progression-relevant items inspect:

- drop probability;
- kill/action duration;
- expected attempts;
- expected acquisition time;
- alternate acquisition paths;
- importance.

A 1-in-10,000 drop may be reasonable for prestige.

It may be unreasonable for mandatory progression.

Context matters.

---

# Bad-Luck Consideration

If mandatory progression depends heavily on randomness, evaluate:

- expected attempts;
- high-percentile unlucky outcomes;
- acquisition alternatives;
- whether failure prevents progression entirely.

Do not automatically add pity systems.

Correct only clearly unreasonable mandatory randomness.

---

# Quest Reward Balance

Where quests provide numeric or economic rewards, compare them against:

- duration;
- difficulty;
- prerequisites;
- progression stage;
- repeatability.

Look for:

- major quest providing obsolete reward;
- trivial task providing disproportionately strong reward;
- repeatable reward breaking the economy.

Do not rewrite quests.

---

# Achievement Reward Balance

If achievements provide gameplay rewards, inspect:

- repeatability;
- exploitability;
- requirement;
- relative value.

Cosmetic-only achievements require little economic tuning.

---

# Skill Interdependence

If systems feed one another, inspect whether the relationship is coherent.

Examples:

- Mining → Smithing;
- Fishing → Cooking;
- Gathering → Crafting;
- Farming → Production.

Look for:

- production consuming dramatically more input than normal gathering can supply;
- one skill becoming unintentionally impossible without trading;
- raw input with no meaningful use;
- production output with no demand.

Preserve intentional specialization and player trade.

---

# Money-Making Comparison

Estimate representative profit or value rates across common activities.

Do not force equality.

Classify approximate activity cost such as:

- low-risk / low-attention;
- high-attention;
- high-risk;
- high-requirement;
- high operating cost.

Rewards should broadly reflect total investment and opportunity.

---

# AFK Versus Active Balance

If the game supports relaxed or AFK activities, compare them against active methods.

Active gameplay may reasonably provide:

- higher XP;
- better resources;
- greater profit;
- more unique rewards.

AFK activity may remain valuable because it requires less attention.

Do not eliminate relaxed play simply because active play is more efficient.

---

# Opportunity Cost

When comparing activities, include what the player gives up.

Examples:

- rare resources;
- inventory space;
- travel time;
- equipment commitment;
- risk;
- attention;
- consumables;
- alternate activity time.

Balance is multidimensional.

---

# Dead Content Hunt

Search for implemented activities or rewards rational players would almost never use.

Examples:

- resource with no meaningful use;
- recipe worse than easier recipe in all relevant ways;
- monster harder than alternatives but rewarding less;
- equipment tier strictly dominated;
- progression activity unlocked after it becomes irrelevant.

First establish whether it serves:

- collection;
- flavor;
- quest;
- cosmetic;
- transition;
- niche strategy.

Fix only genuinely dead gameplay content.

---

# Dominant Strategy Hunt

Ask:

> **If a rational player discovers this strategy, is there any meaningful reason to do anything else?**

Potential causes:

- XP vastly above alternatives;
- profit vastly above alternatives;
- low risk combined with high reward;
- one weapon strictly superior;
- exploitative production loop;
- one resource route dominating all others.

Do not punish optimization itself.

Fix strategies that collapse intended gameplay choice.

---

# "How Would Players Optimize the Fun Out of This?" Review

Assume players will aggressively optimize progression.

Ask:

> **Which strategies would make large portions of implemented content irrational to engage with?**

Look for:

- one XP method dominating;
- one money-maker dominating;
- one weapon dominating;
- one recipe dominating;
- one resource route dominating;
- repeated reward loops.

Require quantitative evidence.

Do not nerf efficient play solely because it is efficient.

---

# "What Would Players Never Use?" Review

Ask:

> **What content is numerically so weak that a rational player has almost no reason to use it?**

For each candidate inspect:

- requirement;
- cost;
- reward;
- acquisition;
- comparison to alternatives;
- potential niche.

Do not assume every low-usage option needs a buff.

Some may intentionally serve transitional or thematic purposes.

---

# "Where Can Players Print Money?" Review

Explicitly inspect:

- vendors;
- crafting;
- conversion;
- refunds;
- reward claiming;
- trading;
- dismantling;
- repair/resale;
- reversible systems.

Look for guaranteed positive-net-value loops with negligible limiting input.

Fix unintended loops.

---

# Transaction Conservation

For conversions ask:

> **What enters the transaction and what leaves?**

Inspect:

- crafting;
- trade;
- vendors;
- upgrades;
- dismantling;
- refunds;
- conversions.

Ensure unintended duplication or free value creation does not occur.

---

# Numeric Boundary Review

Inspect relevant:

- zero;
- negative values;
- maximum values;
- overflow;
- underflow;
- rounding.

Pay particular attention to:

- currency;
- XP;
- item quantities;
- prices;
- damage;
- probabilities;
- costs.

Arithmetic correctness can become a balance exploit.

---

# Rounding Consistency

Check where values are:

- floored;
- rounded;
- ceiled.

Repeated conversions may create value if rounding rules differ between forward and reverse operations.

Fix exploitable or clearly unintended behavior.

---

# Probability Audit

For chance-based systems validate:

- probability bounds;
- percentages;
- weighted tables;
- cumulative selection;
- integer conversion;
- random-selection logic.

Look for:

- probability above valid range;
- impossible outcomes;
- integer truncation;
- unintended bias;
- duplicated entries.

Correctness and balance overlap here.

---

# Expected-Time Analysis

For probability-based progression estimate:

> **expected attempts ≈ 1 / probability**

Then multiply by representative action duration.

Use this to detect absurd mandatory grind.

Remember that expected value does not describe the full player experience when variance is large.

---

# Variance Awareness

Two systems with identical expected reward can feel very different if one has extreme variance.

Consider:

- whether the reward is mandatory;
- whether content is repeatable;
- whether rarity is part of the intended excitement;
- whether alternatives exist.

Do not flatten randomness unnecessarily.

---

# Power-Creep Review

Inspect progression tiers for bonuses that compound too aggressively.

Especially:

- percentage modifiers;
- multiplicative stats;
- critical modifiers;
- stacking buffs;
- overlapping set bonuses.

Check interactions, not only individual values.

---

# Modifier Stacking

Determine whether bonuses combine:

- additively;
- multiplicatively;
- through caps;
- in a specific order.

Search for combinations producing extreme unintended results.

Do not add arbitrary caps merely because numbers become large.

Fix the underlying unintended relationship when possible.

---

# Ratio Analysis

Useful diagnostic ratios may include:

- DPS per requirement level;
- defense per cost;
- XP per minute;
- profit per hour;
- healing per cost;
- output value per input value;
- gathering output per tool tier.

Ratios help identify outliers.

They are not universal truth.

Always interpret them in gameplay context.

---

# Outlier Detection

Where practical, programmatically identify values significantly above or below neighboring values.

Potential targets:

- item stats;
- XP rates;
- requirements;
- vendor prices;
- enemy stats;
- drop values;
- resource yields.

Investigate outliers.

Do not automatically normalize them.

Unique items, bosses, milestone rewards, or prestige content may intentionally be extreme.

---

# Balance Data Quality

Determine where authoritative gameplay values actually live.

Avoid tuning:

- stale duplicated constants;
- obsolete data files;
- UI-only values;
- client copies when the server is authoritative.

If one value exists in several locations:

- determine the authoritative source;
- update consumers appropriately;
- avoid leaving UI or tooltip values stale.

Do not turn this into a broad architecture refactor unless duplication directly undermines balance correctness.

---

# Simulation Where Useful

Create lightweight simulations only when they materially improve confidence.

Possible examples:

- XP progression;
- combat DPS;
- time-to-kill;
- expected loot value;
- currency flow;
- crafting profitability;
- rare-drop acquisition time.

Use the simplest model that answers the actual balance question.

Do not build a massive simulator simply because it is possible.

---

# Change Conservatively

Balance systems are interconnected.

Prefer:

- small;
- explainable;
- targeted;

adjustments before broad global retuning.

After each meaningful change ask:

> **What else does this affect?**

For example, increasing ore yield may affect:

- gathering XP;
- production supply;
- equipment production cost;
- vendor value;
- market supply;
- player wealth.

Trace downstream relationships.

---

# Avoid Compensation Chains

Watch for:

> **change A → breaks B → change B → breaks C → change C...**

If one tuning adjustment requires many compensating changes, reconsider whether the original assumption is correct.

Large interconnected changes can be justified.

Treat them as major changes rather than pretending they are small tuning.

---

# Balance Versus Live Economy Risk

If the game has:

- persistent multiplayer;
- player trading;
- accumulated inventories;
- large existing player holdings;
- live currency balances;

economic changes can materially alter existing player wealth.

Treat changes involving:

- item value;
- major currency supply;
- major sinks;
- persistent costs;
- progression migrations;

as high-risk.

Do not casually reset or devalue player holdings.

When current-player data or telemetry is unavailable, state the uncertainty.

---

# Work in Balance Waves

Do not tune random numbers across the project.

## Wave A — Exploits and Broken Economics

Fix:

- infinite loops;
- duplication-like economic behavior;
- impossible progression;
- catastrophic outliers;
- severe unintended dominant strategies.

Validate.

## Wave B — Progression Curves

Audit:

- XP;
- time-to-level;
- unlock cadence;
- tier requirements;
- progression walls;
- progression skips.

Tune major problems.

Validate.

## Wave C — Combat

Audit:

- weapons;
- armor;
- enemies;
- combat styles;
- abilities;
- consumables.

Tune meaningful outliers.

Validate.

## Wave D — Gathering and Production

Audit:

- resource rates;
- skill XP;
- tools;
- conversion ratios;
- recipes;
- production economics.

Validate.

## Wave E — Currency and Rewards

Audit:

- sources;
- sinks;
- vendors;
- loot;
- quest rewards;
- major milestones.

Validate.

## Wave F — Last 10%

Search for:

- dead items;
- trap choices;
- weak milestones;
- adjacent-tier anomalies;
- small economic loops;
- remaining unexplained outliers.

Tune worthwhile findings.

---

# Reassess After Every Wave

Ask:

- What is the strongest dominant strategy now?
- What content remains dead?
- Where is progression slowest relative to intended pacing?
- Where is progression unexpectedly fast?
- Which resource is overproduced?
- Which resource is underproduced?
- Which currency lacks meaningful sinks?
- Which equipment tier provides weak value?
- Which enemy has poor risk/reward?
- Did a previous adjustment create a new economic loop?
- Did tuning flatten meaningful choices?
- Did a buff create new power creep?
- Did a nerf undermine progression satisfaction?

Recalculate.

Reprioritize.

---

# Productive Balance Loop

Do not stop after fixing obvious outliers.

Balance changes alter relationships.

Examples:

- weapon tuning exposes armor imbalance;
- gathering tuning changes crafting margins;
- crafting tuning changes vendor profitability;
- vendor tuning changes currency sinks;
- XP tuning exposes unlock pacing.

Continue:

> **measure → compare → tune → validate → recompute**

while meaningful, evidence-supported imbalance remains.

Do not manufacture number changes merely to continue working.

Stop when remaining differences are:

- intentional;
- subjective;
- content-dependent;
- dependent on player telemetry unavailable here;
- within reasonable tolerance;
- better evaluated through real player testing.

---

# Regression Validation

After tuning verify relevant:

- requirements;
- unlocks;
- drops;
- vendor relationships;
- recipes;
- XP;
- combat formulas;
- UI/displayed values;
- save compatibility;
- multiplayer authority where applicable.

Do not accidentally introduce:

- negative prices;
- impossible content;
- duplicate rewards;
- invalid probabilities;
- stale UI values;
- broken item requirements;
- unreachable recipes.

---

# Independent Final Balance Review

Near completion, review major areas with fresh context.

Evaluate separately:

## Progression

Audit:

- XP curves;
- time-to-level;
- unlock cadence;
- walls and skips.

## Combat

Audit:

- weapons;
- armor;
- enemies;
- styles;
- abilities.

## Economy

Audit:

- currencies;
- vendors;
- sources;
- sinks;
- arbitrage.

## Gathering / Production

Audit:

- resource generation;
- tools;
- recipes;
- processing economics.

## Rewards

Audit:

- loot;
- milestone rewards;
- quest rewards;
- rare drops.

The purpose of fresh review is to challenge existing tuning, not merely approve it.

---

# "Where Does Progression Stop Feeling Worthwhile?" Review

Inspect progression for stages where:

- required time rises sharply;
- unlocks weaken;
- power gains become negligible;
- one repetitive method dominates;
- resources become meaningless;
- milestones stop mattering.

Identify where player investment and payoff separate.

Tune only when evidence supports intervention.

---

# Anti-Homogenization Review

Before completion ask:

- Did every skill converge toward the same XP rate?
- Did every combat style converge toward the same DPS?
- Did every activity converge toward the same profit?
- Did equipment lose distinct identity?
- Did risk/reward differences disappear?
- Did progression become unnaturally smooth?
- Did relaxed and active methods lose their intended relationship?

Undo unjustified flattening.

Balance should support meaningful tradeoffs.

---

# Anti-Nerf-Everything Review

Do not solve every problem by lowering rewards.

Sometimes the correct fix is to:

- buff an underperformer;
- reduce cost;
- improve requirement timing;
- improve utility;
- strengthen a sink;
- move an unlock;
- improve reward quality.

Preserve a healthy sense of player power and advancement.

---

# Anti-Inflationary-Buff Review

Conversely, do not solve every problem by buffing upward.

Buff chains can create:

- runaway player power;
- trivial enemies;
- currency inflation;
- resource inflation;
- content obsolescence;
- compressed progression.

Prefer the smallest change that restores the intended relationship.

---

# Final Cross-System Review

Before finishing, inspect the game as one interconnected economy.

Review:

- XP curves;
- progression requirements;
- equipment progression;
- enemy progression;
- gathering rates;
- production ratios;
- crafting margins;
- currency sources;
- currency sinks;
- vendor relationships;
- loot expected value;
- reward progression;
- dominant strategies;
- trap choices;
- progression skips;
- progression walls.

Ensure individual fixes still form a coherent whole.

---

# Completion Standard

The progression/economy/balance pass is complete when, to the degree available evidence can establish:

1. major progression systems have been mapped;
2. major resource and currency flows have been mapped;
3. obvious economic exploits are eliminated;
4. severe unintended progression walls are reduced;
5. severe unintended progression skips are reduced;
6. major XP outliers are corrected;
7. important unlock pacing is coherent;
8. major equipment tiers have meaningful relationships;
9. obvious dead items/content are reduced where justified;
10. unintended dominant strategies are reduced where they undermine choice;
11. major combat options have defensible tradeoffs;
12. enemy difficulty and reward relationships are more coherent;
13. gathering output aligns reasonably with downstream resource needs;
14. crafting costs, progression, and rewards are more coherent;
15. obvious vendor arbitrage is eliminated;
16. currency sources and sinks are more intentional;
17. important loot tables have reasonable expected value;
18. mandatory rare progression is not accidentally absurd;
19. important balance changes have quantitative justification;
20. meaningful asymmetry and system identity remain intact;
21. no known balance regression introduced by this pass remains;
22. remaining uncertainty depends on player telemetry, live-economy evidence, subjective product decisions, content expansion, or further real-player testing.

The objective is not:

> **make everything equal**

The objective is:

> **make progression, power, effort, risk, scarcity, cost, and reward relate to one another in deliberate and defensible ways.**

---

# Final Report

When complete, provide a concise balance report.

## 1. Overall Result

Summarize the largest improvements to progression and economy health.

## 2. Critical Exploits / Broken Loops

Describe meaningful economic or progression exploits fixed.

For each significant issue, summarize:

- **Problem**
- **Cause**
- **Fix**
- **Impact**

## 3. Progression

Summarize meaningful changes to:

- XP curves;
- level pacing;
- unlocks;
- progression walls;
- progression skips.

## 4. Combat Balance

Summarize meaningful:

- weapon;
- armor;
- enemy;
- combat-style;
- ability;

changes.

## 5. Gathering and Production

Summarize meaningful:

- resource rates;
- XP;
- tool progression;
- processing;
- recipe;
- crafting-economy;

changes.

## 6. Currency and Economy

Describe meaningful findings involving:

- sources;
- sinks;
- vendor pricing;
- arbitrage;
- inflation;
- persistent-economy risk where applicable.

## 7. Loot and Rewards

Summarize meaningful changes to:

- drop tables;
- quest rewards;
- rare drops;
- milestone rewards.

## 8. Dead / Dominant Content

Describe important trap choices, dead content, or dominant strategies corrected.

## 9. Intentional Asymmetry Preserved

Explicitly describe major differences deliberately retained.

## 10. Validation

State exactly what was actually performed, including relevant:

- calculations;
- simulations;
- runtime tests;
- comparisons;
- progression slices;
- economic-loop checks.

Do not imply measurements or simulations occurred when they did not.

## 11. Deliberately Unchanged

Describe suspected issues preserved because:

- evidence was insufficient;
- player telemetry is needed;
- the difference appears intentional;
- live-economy consequences are uncertain;
- risk exceeded confidence;
- another specialized pass should own it.

## 12. Remaining Opportunities

List only worthwhile future balance work.

For each include:

- **System**
- **Issue**
- **Evidence**
- **Likely player impact**
- **Scope:** Tiny / Small / Medium / Large
- **Recommended priority**

Do not pad the report with microscopic number tweaks.

---

# Final Directive

**Think like a systems designer and game economist, not someone making numbers symmetrical.**

Use evidence.

Model relationships.

Consider player effort.

Consider opportunity cost.

Consider risk.

Consider attention.

Consider acquisition difficulty.

Consider long-term resource flow.

Consider downstream effects.

Do not balance only by raw DPS.

Do not balance only by XP/hour.

Do not balance only by vendor price.

Do not require every activity to provide equal rewards.

Do not destroy intentional asymmetry.

Do not allow obvious exploits merely because correcting them changes numbers.

Do not change major values without inspecting downstream relationships.

Repeatedly ask:

> **What does the player invest?**

> **What does the player receive?**

> **How long does it take?**

> **What risk, attention, or resource cost is required?**

> **What alternative would a rational player choose instead?**

> **Does progression continue to feel worthwhile as the player advances?**

> **Is this difference intentional, or merely an unexplained outlier?**

Continue:

> **measure → compare → identify imbalance → tune → validate → recompute**

while meaningful, evidence-supported improvements remain.

Leave behind the **same game**, but make its progression, combat, rewards, resource flows, crafting, and economy substantially more coherent, rewarding, sustainable, defensible, and professionally tuned.