Knight record
Chester
Sovereign Tower Chester is a jester with a multi-part Goose recruitment route and deliberately unpredictable stats.
Chester Record
Community Tested- Identity
- A mysterious jester recruited through the multi-part Clean Keeper Goose route.
- Recruitment
- Missable route
- Traits
- Jester · Happy To Be Here
- Romance
- Unconfirmed
Recruitment planning
Complete the Clean Keeper Goose sequence and read the current egg clue carefully. Reports describe shiny, smelly, and delicious variants rather than one permanent answer.
The Clean Keeper Goose is the whole key
Chester is recruited through the Clean Keeper Goose contract in Milkford during Act I. The supplied guides agree on the overall shape: resolve the first part, create a special outcome in Part 2, wait for Chester to return to the Tower, and answer his final conversation with the interpretation that the Goose is lonely and looking for company. Choosing a dismissive “you are welcome” style response is repeatedly flagged as a route risk.
Part 2 is a clue-matching exercise rather than a fixed “send Chester” step. The archive reports three routes: shiny or valuable eggs associated with unreformed Gwendan, a bad smell handled by a Knight carrying cheese, and a delicious aroma handled by a Knight with a Horse mount. Another concise guide mentions cheese or Gwendan, so preserve the clue text in your own run instead of assuming one helper is mandatory.
Why Chester’s stats cannot be a normal table
Chester’s roster entry is deliberately unusual. The supplied databases report Level 15 and Armour 6, but no fixed six-stat line: every stat is random and can reroll whenever the game checks it, with the guide reporting a 0–15 range. A screenshot from one audience is therefore not a permanent Chester build, and this page omits a fake “best stat” recommendation.
The Jester attribute is used to explain that randomness, while Happy To Be Here is reported as a hidden attribute that lets Chester enjoy all quest types. The meal table is similarly broad: the archive says he likes all six listed meals, with the database’s general affinity and quest-score effects. These facts make Chester flexible, but they do not make every random roll reliable.
Who Chester is in the supplied story material
Official promotion calls him Chester the Jester, and the local route material presents him as a Milkford resident caught up in a war goose and a public-bath problem. The Goose is not just an item puzzle: the chain establishes Chester’s need for company and his belief that a proper Knight must address the situation. The follow-up audience turns that social interpretation into his invitation to the Round Table.
The collected sources also list special outcomes involving the Great Duel and an Epicrates witness, but they do not support a single complete romance route. One community romance discussion exists, yet the supplied archive keeps it separate from the main recruitment evidence. That separation prevents an isolated comment from being mistaken for an official relationship system.
Practical checks and Unconfirmed details
Before sending a helper, write down whether the clue says shiny, smelly, or delicious, and whether your current Knight actually carries cheese or a Horse. Save before the Part 2 result and before the final conversation. If Chester fails to appear, verify that the special outcome completed and that the return dialogue was answered with the company interpretation.
The stable conclusion is simple: Chester is an Act I Milkford recruit with random stats, all-meal compatibility, and a Goose route. Exact special-outcome odds, later transformation rules, and romance completion remain community-tested or Unconfirmed, so this page keeps the random nature visible instead of forcing him into a conventional Knight spreadsheet.
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 Chester route spoilers
The changing clue is part of the route, while Chester’s numerical stats are intentionally unpredictable. Do not use a stat screenshot from another run as a fixed database value.