Tasks and contracts
Tasks and contracts are different kinds of commissions: contracts revolve around dungeon objectives and conditions, while tasks are narrative commissions with contacts, stages and outcomes. This page separates them using same-release data and explains contract condition selection, situation modifiers and common entry points.
Contents
Two kinds of commissions
Contracts are commissions around dungeons and caves whose objective, conditions and deadlines can change with the contract; tasks are narrative commissions with their own issuer, progress and delivery roles and stage outcomes. They are registered separately: a task's requirements are not a contract objective, and a contract's objective does not replace a task's story.
Contracts and condition selection
Dungeon conditions follow the verified order: an explicit argument first, a contract override next, and tier-random only as the fallback (tier 2: 10%, tier 3: 25%, tier 4: 50%, tier 5: 100%, tier default: 0%; the tiers are dungeon tiers, not player levels). A contract override is consumed after use so it does not apply repeatedly.
Settlement situations modify contract deadlines and contract reputation gains (currently verified: Competition). See each situation article for values and other effects; the full reputation formula is in the reputation article.
Contract service entries
Contract services are provided by characters: verified person service tables list 'contracts' as its own service (for example Reynold in Denbrie and Knud in Mannshire); see the related task articles for specifics. This page does not list every provider's contract templates as verified.
Task articles
Narrative tasks appear as independent articles with clickable flows: issuer/progress/delivery roles are registered separately and stages and outcomes follow verified actions. Task articles cover rewards, failures and branches, and link related people, places and the map.
Unverified details
The per-character contract template lists, the full set of contract objective kinds and baseline deadline values are not yet closed in the same-release data and are not asserted here (documented gap).