The short answer
Sovereign Tower does not ask you to select a male, female, or nonbinary protagonist at the start. In a developer reply from the Demo period, Wild Wits explained that the Sovereign is intended to remain gender-neutral wherever the language allows. Romance is therefore presented around the ruler's relationships rather than a chosen player-gender setting.
Current full-release guides provide route evidence for these love interests:
| Evidence status | Characters |
|---|---|
| Direct route or relationship-event evidence | Angelica, Gideon, Gwendan, Ligia, Oliver, Rufus, Ursula, Victoria |
| Flirting or possible endgame content, but not a confirmed complete route in reviewed sources | Chester, Dulahan |
| Marked unavailable or not supported by the reviewed route guide | Alwena, Ari, Arron, Childeric, Edith, Tarcus, The Wolf |
| Still TBA or insufficiently documented | Other named knights not listed above |
How Sovereign gender works
There is no initial pronoun or body-selection menu for the ruler. The developer said this avoided multiplying writing and translation work while preserving a gender-neutral Sovereign where grammar permits.
This means:
- you do not need to restart to pick a different protagonist gender;
- the absence of a selector is intentional, not a missing settings option;
- localization grammar may express neutrality differently between languages;
- controller, platform, or character appearance settings do not change romance eligibility.
The same developer response specifically excluded Arlin, describing him as married and a happy father. It should not be generalized into a complete final list because it predates the full release.
Step by step
1. Recruit and keep the character available
Romance grows from the same branching campaign that controls recruitment, deaths, resignations, and regional outcomes. A character cannot progress through later relationship events if that timeline never recruited them or removed them from play.
Start with the all knights recruitment guide, then check the target's personal conditions in a current character guide.
2. Build Affinity through supported decisions
Use favorable audiences, personal conversations, and quest choices that respect the character's stated values. Favorite meals can supply +1.5 Affinity to one knight and a current quest-score bonus, but they do not unlock romance by themselves. The favorite meals table is support, not a romance code.
3. Watch for character events
Relationship routes progress through character-specific events rather than one universal “romance” menu. Angelica's direct guide, for example, documents multiple relationship stages before the romantic commitment. Other characters use their own personal conflicts and choices.
Choose responses that fit the route you are actually pursuing. We do not publish invented exact Affinity thresholds because the reviewed official sources do not provide them.
4. Protect the timeline
A romance target can become involved in Act II's variable murder event. The victim and culprit can change with relationship state, so high investment in one character may change the cast of that scene. If it fires, use the Act II murder guide instead of assuming one fixed victim.
5. Treat achievements as confirmation, not instructions
Steam lists romance-related achievements such as Love Is All and A True Love Kiss. They confirm that relationship outcomes exist, but their public descriptions are not a complete route walkthrough and do not reveal every love interest.
What the current sources say about routes
Angelica has the clearest independent walkthrough reviewed for this page, with staged relationship events and romance-directed dialogue.
Gideon, Gwendan, Ligia, Oliver, Rufus, Ursula, and Victoria have romance notes in the current all-in-one character guide. Those notes are enough to support route availability, but not enough to claim identical requirements or publish unverified numerical thresholds.
Chester can flirt, but the reviewed guide does not establish a complete romance route. Dulahan has possible endgame material that remains unconfirmed in that source. They are separated from confirmed routes so a playful line is not mistaken for a guaranteed ending.
The guide marks several other characters as not romanceable or still TBA. “TBA” means the public guide had not verified the path—not proof that the game permanently forbids it.
Common mistakes
- Looking for a protagonist gender selector that the game does not provide.
- Treating the developer's Demo-era intention as a final full-release romance roster.
- Assuming one flirt line confirms a complete ending.
- Copying an exact Affinity threshold from an unsourced page.
- Using a favorite meal as though it bypasses the character's personal decisions.
- Ignoring recruitment conflicts, deaths, or resignations that close the relationship route.
Evidence limits
This guide was checked for Sovereign Tower 1.0.8 on August 12, 2026. Gender handling comes from a developer reply on the official itch.io page. The romance shortlist combines official achievements with current direct character and Angelica walkthroughs. Because the broad developer statement predates release and the character guide still contains TBA entries, this page deliberately does not claim a final exhaustive list.
Sources
- Developer gender and romance response — official explanation of the gender-neutral Sovereign and early romance intent.
- Steam global achievements — official evidence that romance outcomes exist.
- All-in-one character guide — current per-character route and availability notes.
- Angelica romance guide — direct staged route evidence.