Cycle by cycle

Sovereign Tower Gameplay Walkthrough

Use the same planning rhythm in every cycle: collect information, inspect the schedule, assign for the complete quest profile, resolve consequences, then update your record before advancing.

Direct answer

In Cycle 1, collect audience information, inspect every quest deadline and Knight, preserve Treasury flexibility, and record the first debrief. Later Acts build on that repeatable system rather than one rigid list of dialogue answers.

Audience before assumptionsPlan the full quest calendarDebrief every resultSave before major Act transitions

Cycle 1 in order

Audience scenes introduce requests, pressure, and hidden context. Move to the Round Table only after noting what changed, then compare quest deadlines with the complete roster and resource state.

  • Morning: finish every Audience and record new quests.
  • Before deployment: compare deadlines, full attributes, and available party size.
  • After results: read the debrief, repair armor, and investigate traits.
  • Before advancing: record fixed costs and roster gaps for the next cycle.

Act 1 route map

Act 1 is easier to understand as four save groups rather than one perfect run: Goose, the Groveshire beast, the Gavault revolt, and the Dragon Knight. Each group changes the later roster or regional state.

  • Goose: Angelica first, Gwendan in the follow-up, egg description, and Chester.
  • Groveshire: compare the Beast or wolf, Rufus, and Silgur outcomes.
  • Gavault: compare Brunhilda, Tarcus, territory, and the lion mount.
  • Dragon Knight: prepare the assigned team, complete support objectives, and keep a separate save for Silgur's alternative.

Act checkpoints

Before an Act transition, preserve a save and record unresolved personal quests, faction pressure, Treasury commitments, injured or absent Knights, and any story clue you may want to test in another timeline.

  • Keep the main save before entering the next Act.
  • Keep a route save before a major recruitment or character Audience.
  • Keep a battle save before selecting support for a major fight.

How to document a quest

For each route, capture the quest name, cycle, requirements, assigned Knights, equipment, visible traits, result tier, Unexpected Outcome, damage, relationship change, and follow-up. This creates a walkthrough that survives balance patches better than a bare answer list.

Review every result before advancing

After a quest, check injuries and roster changes, armor and equipment, Affinity, the next cycle's visitors, regional state, and any Unexpected Outcome. Store the result beside the earlier choice that caused it so a rewind remains understandable.

  • Roster: recruitment, dismissal, injury, or death.
  • Resources: gold, equipment, armor, and support.
  • Relationships: Affinity, personal scenes, and invitations.
  • Timeline: new knowledge, rewind points, and follow-up visitors.
FAQ

Frequently asked questions

How many Acts does Sovereign Tower have?

Use every visible Act transition as a hard checkpoint. Keep one save before the transition and another before the last major personal quest in that Act.

What should I do in Cycle 1?

Collect audience information, review quest deadlines and the full Knight roster, preserve Treasury flexibility, and record what the first debrief reveals before committing to a rewind.

Is there one correct order for all quests?

Quest order depends on deadlines, full requirements, roster availability, and knowledge carried from prior runs. Resolve the least flexible deadlines first.

What should I save before an Act ends?

Save the roster, equipment, unresolved quests, faction state, Treasury, and important dialogue clues so you can compare later branches.

Patch 1.0.11

Plan your next cycle

This guide follows Patch 1.0.11. Keep a save before major Act transitions and compare outcomes after each rewind.