Knight record
Silgur
Sovereign Tower Silgur is a Groveshire hunter connected to the Beast branch and the Dragon Heart outcome.
Silgur Record
Community Tested- Identity
- A Groveshire hunter connected to the Beast branch and a later Dragon Heart route.
- Recruitment
- Missable route
- Traits
- Hunter · Forester · Patient · Poacher
- Romance
- Not established
Recruitment planning
Choose the Silgur outcome during the Groveshire Beast route if you want his candidacy. Preserve the branch before resolving the hunt.
Kill the Beast without sending the wrong helper
Silgur is the ordinary kill outcome in the Groveshire Beast storyline. The supplied recruitment guides agree on the two variables that matter: choose to kill the Beast rather than tame or cure it, and do not send Angelica if you want Silgur rather than the Beast/Wolf-style result. After Groveshire’s ruler pledges the county, Silgur later asks for an audience and can join the Round Table.
The exact cycle varies by playthrough. One walkthrough recruits Silgur later than the concise Act I table, after additional Groveshire and Dragon Knight setup. That difference is not a contradiction by itself; it shows why the page uses “Act I route” and “community-tested timing” rather than promising a single cycle. Preserve a save before the Beast quest and before the Angelica assignment.
Hunter profile and quest strengths
The stable roster profile describes Silgur as a famous Groveshire hunter who later becomes associated with Beaconsbury. His visible attributes are Hunter and Forester, both useful in Woods-related work. The hidden Patient trait is reported to reward longer quests and to add value in Hunt, Help, and People Involved contexts, while Poacher can improve merchant satisfaction but penalize Dragon.
The Dragon penalty is an important tension, not a mistake to hide. Silgur’s later story asks him to plan a Dragon Knight ambush, yet the supplied data gives Poacher a Dragon downside. Send him based on the current quest pressure and equipment, not on a simplified “hunter always wins” rule. The strongest walkthrough recommends using his Wits and Agility while compensating for lower Strength.
Dragon Knight, Dragon Heart, and achievement evidence
A supplied Cycle 8 walkthrough records Silgur proposing an ambush against the Dragon Knight. Choosing the ambush over a direct confrontation produces a Great Success and a Dragon Heart in that playthrough, with additional Knights assigned to the quest. Other sources connect Dragon Heart with Silgur’s later personal route and the official achievement A Big Heart, but the archive does not prove that every reward state or timing is identical.
This is why Silgur’s page separates recruitment from transformation. The Beast branch can place him at court; the later Dragon material asks the player to preserve him, read his proposal, and resolve a high-pressure quest. Keep the current route’s assignment screen as evidence, because one walkthrough’s cycle-seven or cycle-eight sequence is not a universal script.
What remains Unconfirmed
Silgur’s official spelling, hunter framing, Beast-kill branch, and recurring trait set are well supported. Exact recruitment cycle, every Dragon Heart prerequisite, hidden score formulas, and whether all rewind combinations can share the same roster are community-tested. The adjacent Wolf and Rufus outcomes should be read as branch comparisons, not as extra Silgur requirements.
For a clean run, choose Kill the Beast, check that Angelica is not assigned, save before the county pledge, and then verify the audience. Later, compare the Dragon Knight options and record which reward actually appears. This produces a useful evidence trail without inventing a fixed number where the supplied walkthroughs only show one route.
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 Silgur route spoilers
Later material links Silgur to a Dragon Heart outcome. Exact quest timing and every reward effect vary across reports, so this record avoids a false turn-by-turn guarantee.