Identity
Name & background
Worldbuilding and future expansion hooks. A distinctive name does not currently guarantee a private ruleset.
Guild finance · v2.0.7
A patron is a relationship, not a loot rarity
Rare and Unique did not vanish. In the current design they describe deeper mandate tiers reached through the relationship. The person you choose establishes a type and preferences; the value of the arrangement grows when you satisfy what they ask without letting the guild's books destroy their confidence.
Mechanical
Type & preference
The current meaningful differences are the patron type and racial preference attached to the named patron.
Progression
Mandate relationship
Completing demands advances the relationship into stronger tiers that give more and ask more.
The mandate loop
Read every demand as a trade
Receive
The patron presents a mandate shaped by the relationship.
Price
Check the roster, deadline and next settlement before committing.
Deliver
Fulfilment advances the relationship rather than changing a nameplate rarity.
Escalate
Later Rare or Unique tiers improve the return while raising the demand.
The developer confirmed this relationship model in the current-version discussion. Exact mandate rewards and requirements vary, so this page does not invent a universal tier table where the game does not expose one.
The six-day ledger
Confidence sits inside your operating economy
Patron stipend, roster wages and guild upkeep settle every six days. Confidence helps the stipend; debt erodes confidence at settlement, and the risk of losing the patron rises sharply once confidence falls far enough. That makes a mandate decision an economy decision even when the mandate itself looks like roster or story content.
Steady inflow
Patron stipend
Recurring outflow
Wages + upkeep
Relationship buffer
Confidence
Choosing at the start
Choose the constraint you can serve
Do not hunt a dramatic name expecting a hidden legendary ruleset. Read the patron type and racial preference, then ask whether they fit the guild you intend to build. A preference that matches your available recruits is easier to honour; a reward profile that supports a thin opening roster can be more valuable than one aimed at a later-season plan.
During the season
Protect the relationship from the books
Before accepting a costly demand, project the next settlement without assuming another optional delve will pay for it. If the guild is already running a recurring deficit, a reward that arrives later may not stop confidence from bleeding now. Preserve enough operating room to fulfil the mandate and keep the patron.
What is not live yet
Challenge Ledgers are roadmap, not current rules
The developer has discussed future Challenge Ledgers built around particular guilds. That idea helps explain why named patrons carry extra setting detail, but it is not a feature of v2.0.7. Do not choose a patron expecting a named challenge campaign to unlock today.
Quick answers
Three misconceptions to drop
“I cannot find a Rare patron.”
Rare is a later mandate tier in the relationship, not necessarily a special starting name to reroll for.
“Every named patron has a secret passive.”
Current differences centre on patron type and racial preference; names also support worldbuilding and future expansion.
“A mandate reward can rescue any deficit.”
Recurring settlements continue. Price the relationship against wages, upkeep and confidence, not a single reward screen.
Continue at the guide desk
01Survival routeFirst Season8 min · Current systems + community pain points02Bundle verifiedTraining & Hero Growth7 min · Verified in current build03Contract deskOaths & Renewals7 min · Verified in current build04Roster marketRecruitment & Poaching8 min · Verified in current build05Roster analysisRace & Class Selection9 min · Current extracted weights + transparent method06Hall ledgerGuild Hall Operations8 min · Verified in current build07Support deskTroubleshooting5 min · Developer fixes + labelled community reports