FIELD NOTE 01

Evidence comparison by system

The table separates what the demo or demo-era update can establish, what developers have explicitly confirmed for the full game and what must be checked on release day. It deliberately uses no invented counts.

SystemDemo evidenceFull-game evidenceRelease-day check
Core loopClean, collect or mine, refine, earn, upgrade, unlock and complete quests.The official full-game store describes the same connected loop.Confirm balance and tutorial order.
Levels & areasA limited map and level set demonstrates navigation and unlock flow.New levels confirmed; the store says players unlock new areas.Verify names, count, order and unlock rules.
ResourcesDemo resources demonstrate collection and processing.New resources are developer-confirmed.Verify exact names, acquisition and refinery relationships.
ToolsVacuum, jackhammer and air-filter concepts appear in official release messaging.More tools and equipment are developer-confirmed.Verify controls, stats, upgrades and current roles.
UpgradesUpgrade tree, Multi-barrel example and economy balancing are documented.New upgrades and continued balance work are confirmed.Verify nodes, costs, effects, prerequisites and caps.
Power-upsThe Next Fest update names the Magnet power-up.Additional power-ups are developer-confirmed.Verify unlocks, effects, duration and upgrade paths.
QuestsDemo updates mention new quests in the playable build.The full game adds quests and more content.Verify names, objectives, rewards and progression effects.
ControllerDemo updates document tool, map and upgrade-tree navigation improvements.No blanket launch-device claim is made before unlock.Test current devices and separate historical issues.

FIELD NOTE 02

What demo knowledge remains useful

System relationships remain the most durable lesson. Learning where cash, collected resources, refinery processing, upgrades, quests and the map connect helps you diagnose a bottleneck without relying on a specific number.

The site's ROI calculator is also resilient because it uses values entered from the player's current build. The progress tracker accepts custom names rather than loading an unverified launch checklist.

An official Sludgineers demo-era cleanup scene.
Official Sludgineers press-kit media · documented in the site manifest

FIELD NOTE 03

What should not be carried forward automatically

Costs, rates, recipe ratios, area thresholds, quest rewards, energy balance, bugs and controller edge cases can change. A familiar name or screenshot is not enough to mark a demo value current.

When advice depends on those details, check the live build and record the source date. Historical problems stay in a separate evidence bucket until reproduced or acknowledged after release.

  • Upgrade values and order
  • Refinery formulas
  • Level-completion threshold
  • Energy capacity or recharge
  • Current bugs
  • Achievement requirements

FIELD NOTE 04

How release-day promotion works

Prepared pages are scored for reliable current sources, distinct intent, unique useful content, actionable answers, internal-link fit and unresolved terminology risk. An 8/10 score plus required evidence is necessary for indexable publication.

A score alone cannot open the refinery calculator. That route additionally needs a validated current recipe dataset capable of producing correct conversions without defaults or guessed modifiers.

EVIDENCE LOG

Sources