FAST ANSWER / BRUNHILDA
Treat the recruit route as a lead and keep a rewind before her region.
Recent community replies describe a people-focused regional route and an alternate information-based rewind route. Both are leads, not guaranteed recipes: the reported audacity or Reason gate is uncertain, and the community has not supplied a confirmed answer for preventing her death.
- Create a checkpoint before the first quest in her region and record the visible response options.
- Test either the people-focused route or the omniscient-information route, changing no other variable on the first comparison.
- Record the exact audacity or Reason requirement, recruitment result, and whether Brunhilda survives the branch.
Two reported ways to reach the recruitment choice
A recent community reply describes a route through Brunhilda's region: choose 'people' on the first quest, invite her, complete her quest, and on the second meeting offer her the chance to give up and join. The reply suggests an audacity requirement, possibly level 1, but does not establish that number as a universal gate.
- Save before the first regional quest
- Capture the exact wording of the first response
- Complete the follow-up before testing a different branch
- Write down the audacity value shown in your build
Official Patch 1.0.11: assignment fix, not a full recruit recipe
The official 1.0.11 notes fix an issue where Brunhilda was not automatically assigned to the Brunhilda Testimony quest. That removes an assignment blocker, but it does not confirm the reported regional choices, audacity or Reason threshold, or the separate question of how to keep her alive.
- Fixed: automatic assignment to Brunhilda Testimony
- Still test: the first regional choice and second-meeting recruitment option
- Keep the reported audacity or Reason gate under verification
- Record whether the quest appears and whether Brunhilda survives the follow-up
- Evidence state: official assignment fix / route and save outcome remain unverified
The alternate information route is still a lead
A second community reply describes using knowledge carried through a rewind at the first countess meeting to reveal the rebellion leader, bring Brunhilda to the tower earlier, and attempt to convince her to join. The reply suggests a Reason requirement, but does not establish the exact threshold or whether every build exposes the same option.
- Record the dialogue state before using omniscient information
- Check whether Brunhilda arrives before the regional quest chain
- Capture the visible Reason requirement and the resulting branch
- Keep this route separate from the people-focused route until both reproduce
Recruitment is not the same as saving her
The recent discussion also contains a player asking how to save Brunhilda because she keeps being killed. That is a separate, higher-risk question. The current public exchange does not prove whether her death is caused by a missed choice, a timing condition, a quest result, or an unavoidable branch, so this page does not promise a save route.
How to test without losing the route
Keep the regional response, quest assignment, party, audacity, and day in a small log. Change one variable per rewind. If the same death or recruitment result repeats from the same preceding state, record it as a reproduced branch; if it changes, keep the prerequisite open rather than guessing.
- Before-state: day, region, party, audacity, active quest
- Choice-state: exact dialogue option and invitation timing
- Outcome-state: recruitment, death, follow-up quest, or no change
- Confidence: community report, reproduced, or still unknown
What will change when it is verified
When the route is reproduced, add the exact build, prerequisite values, dialogue wording, and the first safe checkpoint. If the route fails in another build, keep the page split by version instead of silently turning one player's outcome into a universal rule.
Baseline source: official Sovereign Tower page on Steam. Additional reference: recent community discussion on Brunhilda recruitment and death. / official Patch 1.0.11 notes. This note is an independent editorial guide; evidence status is shown where it matters. Last checked: August 28, 2026.