ForgeTax Tribute Planning: Stages, Priorities & Rules

ForgeTax tribute planning turns the dragon's deadlines from emergencies into schedule. Planning is what separates the players who pay every bell from the players who discover their best blade was spent on relics the day before a deadline. This guide covers the five-stage plan, the two-blade rule, resource priorities under pressure, and the failure playbook for when things go wrong.

The Five-Stage Planning Table

Every run moves through the same tribute arc, and each stage has its own correct posture:

Print the table mentally and locate your run in it before every session. Most planning failures are stage mismatches — playing aggressive in the approaching stage, or conservative in the after-tribute stage when rebuilding was due.

The Two-Blade Rule

The single most valuable planning habit in the game: one blade for the current demand, one blade for development — never both roles on the same sword. When a blade carries the tribute plan and the economy plan together, one break collapses both.

The two-track split costs inventory attention — multi-blade handling is awkward, players complain — but it is the difference between a survivable break and a dead run. If you only adopt one rule from this guide, adopt this one.

Resource Priorities Under Pressure

When the deadline squeezes, spend in this order:

1. The qualifying blade — the only thing that directly pays the tribute.
2. Pressure buffer — the room to complete required actions safely.
3. Draw tickets — held for bottlenecks nothing else can solve.
4. Relic investment — surplus only, after the tribute is locked.

The logic is asymmetry: a run that reaches the next cycle can rebuild anything, but a broken qualifying blade rebuilds into nothing. Survival options come before growth options every time.

Tribute-Support Relic Routes

Tribute-support relics lower the opportunity cost of reserving a blade — they make the protected blade cheaper to produce and safer to hold. They are strongest in the mid game, when targets are known but deadlines are still approaching, and they pair naturally with safe-forging effects.

A common support plan: one relic that reduces the cost of reaching the target, one that reduces break risk on the blades headed for reservation, and only then value-scaling relics. The order mirrors the priority list above — support first, scaling last.

The Failure Playbook

When a deadline arrives and the reserve doesn't qualify, the community playbook gives an action per situation:

• Blade nearly qualifies → one planned strike, then stop — the single best risk-reward trade in the game.
• Blade far from qualifying → preserve value and accept the setback; chasing the target is how snowballs start.
• Multiple blades held → risk only secondary blades.
• Risk-reducing relics held → apply protection before striking, not after.
• Nothing qualifies → lock value for the next cycle and plan around the penalty rather than gambling the run.

The playbook's theme is sequencing under stress: choose the smallest sufficient risk, apply it once, and re-plan. Panic striking is how a missed deadline becomes a dead run.

Measuring Progress the Right Way

The community's progression benchmark doubles as the planning goal: finish a run having paid every tribute and kept your relic investments intact — even without a record-breaking blade — and you are progressing correctly. Stability compounds faster than variance.

The full planning checklist: set value targets per blade, track risk on every strike, keep one spare tribute blade, invest in the relic machine only by plan, hold at least one ticket, test on cheap blades, and end every forging sequence at a named checkpoint. Each line is small; together they are the difference between a contract survived and a contract failed.