FIELD NOTE 01

What quests can tell you

Quests can point toward a tool, system, area or objective that the game expects you to understand. If progress feels directionless, check the current objective before repeating work without a target.

This is a progression framework, not a claim that every quest unlocks the same type of content.

An official Sludgineers region map with objectives visible.
Official Sludgineers press-kit media · documented in the site manifest

FIELD NOTE 02

Record a quest accurately

Capture its exact current name, prerequisite, objective text, reward if shown and what happens when it completes. Mark the build and date.

A historical demo name should stay labeled as demo evidence until the same quest is re-observed in full release.

  • Exact name
  • Prerequisite
  • Objective
  • Reward
  • Progression effect
  • Current verification

FIELD NOTE 03

When a quest needs its own guide

A standalone route is justified when players need steps, an unlock explanation, a stuck-state fix or a choice analysis that a table cannot answer.

A one-paragraph page that repeats the objective adds no value. Until the 8/10 promotion gate is met, quest child routes remain 404 and out of the sitemap.

FIELD NOTE 04

New quests and the release registry

The official full-release announcement says the full version adds new quests to complete. Historical Demo updates also mention new quests, but the launch announcement is the current evidence that the system expanded in the live game.

Neither source publishes the complete launch names, objectives, rewards or dependencies. The quest registry still requires exact name, prerequisite, objective, reward, progression effect, source, build and verification date before any child route can leave 404.

EVIDENCE LOG

Sources