Knight record
Goberto
Sovereign Tower Goberto is a distinctive early Knight connected to unusual quest and transformation outcomes.
Goberto Record
Community Tested- Identity
- An eager Naoned Knight whose survival creates a meaningful roster branch.
- Recruitment
- Route-dependent candidacy
- Traits
- Inattentive · Cheese Lover · Extremely Clumsy
- Romance
- Not established
Recruitment planning
Recruiting and keeping Goberto alive preserves his own route; losing him opens the connected Dulahan branch. Save before the Great Duel and Almor decisions if you want to compare both outcomes.
Preferences
- Audacious Sovereign
Recruit Goberto before planning his branches
Goberto is a scheduled early Act I candidate from Naoned. The supplied guides describe an audience in which he introduces himself as Sir Goberto and offers to help with monsters; accepting places him on the Round Table immediately. If the audience is declined or missed, the sources report a Map Room invitation instead, but the exact fallback cost belongs to the source that recorded it and is not treated as a universal rule here.
His survival matters because Goberto is one half of a connected roster branch. Multiple sources link his death to Dulahan appearing later, while other reports keep Goberto alive for an Almor transformation. Save before the Bloody Magpie, the Great Duel, and the Almor decisions if you want to compare both routes without rewriting the entire timeline.
Character profile and assignment use
The stable profile describes Goberto as inattentive, a cheese lover or cheesemaker, and extremely clumsy. The supplied database reports a strong Strength opening with very low secondary values, while a separate guide presents the same general “strong under the armor” idea. Because those values can be version- or state-sensitive, use the in-game sheet for the current run and use this page for the route logic.
Goberto likes Audacious rule and the collected quest notes favor Hunt, Duel, and Relic Recovery while disliking Diplomacy. Cheese-related scenes are not just comedy: the cheese clue can help with Chester’s Clean Keeper Goose chain, and the character archive repeatedly uses family, letters, and his large extended family to explain why the early audience feels unusually open and enthusiastic.
Supra Goberto and the Dulahan choice
The strongest transformation report sends Goberto on The Great Duel at the end of the Almor competition questline. That route is called Supra Goberto in the supplied material and is described as improving several attributes and armour. The exact bonus table is preserved in the research archive, but this page avoids presenting a single numeric promise when other sources describe different states or equipment effects.
The alternative is the death route. Field Notes and community discussions describe protecting Goberto or allowing his death as a meaningful split, with Dulahan arriving after the loss. Neither outcome is automatically “wrong”; one keeps Goberto’s direct character route open, while the other opens the spectral Knight’s body and helmet branches. Make the decision after checking which ending or roster experiment the run is testing.
Romance and evidence boundaries
The supplied Goberto guide documents a one-heart kitchen scene in which he writes a letter and talks about family, recent events, and the Sovereign’s loneliness. One branch raises affinity. The material does not establish a complete romance route with the same confidence as Gwendan, Ursula, Brunhilda, Gideon, or Oliver, so this page keeps romance status separate from the documented affinity scene.
Official material strongly supports the Goberto–Dulahan promotional pairing, but official promotion does not prove every gameplay trigger. Treat exact cycle numbers, transformation totals, and the full romance conclusion as community-tested or Unconfirmed. The most dependable checklist is therefore short: recruit early, save before Almor and the Bloody Magpie, and record whether the current branch preserves Goberto or turns toward Dulahan.
How to read this Knight record
Facts repeated by an official announcement, a patch note, or more than one independent roster source are presented as the stable profile. Recruitment steps, affinity choices, and transformation claims are separated because they come from different evidence classes. A community-tested label means the supplied material describes a repeatable player result; it does not mean the developer has published the rule.
When a page says Unconfirmed, keep the claim visible but do not build an entire run around it. The safest comparison is to note the cycle, county or city state, living roster, current quest text, and whether Demon Power has been used. That record lets you compare two saves without turning a route report into a promise.
A practical save plan
Make one save before the first recruitment gate, one before any quest that can kill, dismiss, transform, or relocate the Knight, and one before a romance or political commitment. Read the next audience after the cycle advances before loading an older file: several supplied routes depend on what the game remembers, not only on the choice that appears on screen.
This approach also protects the evidence boundary. If your result differs from the route report, record what changed instead of silently correcting the page in your head. The wiki can then distinguish an official fix, a high-confidence repeated result, and a single-run observation while still giving you a usable next step.
Show Goberto route spoilers
Goberto’s death is repeatedly linked to Dulahan’s later appearance. The route can therefore exchange one roster outcome for another rather than simply marking a failed quest.