ANNEX / CRAFT / FIELD NOTE

Sovereign Tower Forge & Annex Upgrade Guide.

The forge is a planning decision. Name the next failure you want to prevent, compare the available upgrade paths, and keep a small ledger so a rewind does not erase the lesson.

Answer: spend only when the bottleneck is clearUpdated today3 min read

QUESTION

Answer: spend only when the bottleneck is clear

EVIDENCE

Updated today

NEXT MOVE

Patch 1.1.1: equipped items missing in Forge storage

LAST CHECKED

September 19, 2026
01upgrade ledger
03checks before crafting
02alternatives to compare

Patch 1.1.1: equipped items missing in Forge storage

Official fix: equipped items could be absent from Storage while viewing the Forge. The patch also fixes a sold-equipment display issue. Neither fix establishes crafting prices or an optimal upgrade order.

Start with the failure you want to remove

Before crafting, write one sentence: 'This upgrade should help with ___.'. If the blank is a stat gap, assignment choice, resource shortage, or recovery problem, you have a testable reason to spend.

  • Which upcoming quest or bottleneck does this address?
  • Could the same resource unlock a wider court option?
  • Will the upgrade still matter if a rewind changes the route?
  • What result would prove that the upgrade paid for itself?

Use a two-option comparison

Compare the selected upgrade with the best alternative you can afford. Record immediate effect, first useful quest, and whether the benefit applies to one knight or the whole run. This keeps the guide practical without inventing a permanent tier list.

When to wait

If you cannot name the next decision the item improves, hold the resource. A little friction now is cheaper than locking the run into an upgrade that does not match the current court.

Baseline source: official Sovereign Tower page on Steam. Additional reference: official Patch 1.1.1 notes. This note is an independent editorial guide; evidence status is shown where it matters. Last checked: September 19, 2026.

September 19: added the relevant official 1.1.1 fix; old-save recovery and wider route conditions remain unverified.