FIELD NOTE 01

What the official tree shows

Official media presents a connected, multi-branch upgrade interface. That structure matters because purchases may sit behind earlier nodes or serve distinct systems.

A single flat tier list loses dependency and timing context. Follow the branch that addresses the current constraint, then compare the visible next node against alternatives in the same role.

A full-screen official view of the Sludgineers upgrade tree.
Official Sludgineers press-kit media · documented in the site manifest

FIELD NOTE 02

Navigate with intent

The June official update names gamepad improvements for upgrade-tree navigation. That is evidence of supported interaction work in the demo cycle, not a guarantee about every controller on the launch build.

Before buying, note prerequisites, what the node changes and whether the benefit appears immediately or unlocks a later choice.

  • Branch purpose
  • Visible prerequisite
  • Current and next value
  • Cost
  • System bottleneck

FIELD NOTE 03

How this becomes a current database

After Steam confirms the live build, each node needs an exact current name, cost, effect, prerequisite, cap if any, source and verification date. A screenshot alone is not enough when a value cannot be read confidently.

Individual upgrade pages remain reserved unless a node has a real player problem and enough unique explanation to pass the promotion score.

EVIDENCE LOG

Sources