FIELD NOTE 01

Start with the bottleneck, not a tier label

Classify the current constraint as cleaning, collection, capacity, movement, refinery throughput, cash, quest access or another visible system. An upgrade in a different system can be strong but badly timed.

This step creates a conditional order: fix the constraint stopping the next useful action, measure again, then reassess. It avoids pretending every save follows one mathematically optimal line.

  • Name the blocked action
  • Identify comparable upgrades
  • Record current and next values
  • Check unlock or quest alternatives

FIELD NOTE 02

Rank comparable rate upgrades

For upgrades using the same unit, calculate gain as the new rate minus the current rate. Divide cost by positive gain for a payback measure. Shorter payback can lead the comparison when the system is actually active.

Do not combine unlike units into one score. Movement utility, capacity, new access and automation may need a qualitative decision beside the numeric ranking.

An official Sludgineers upgrade tree used to classify branches and dependencies.
Official Sludgineers press-kit media · documented in the site manifest

FIELD NOTE 03

Build-dependent upgrade order

A practical order can branch: a field-speed purchase makes sense when cleanup is slow; processing deserves attention when inputs accumulate; capacity matters when repeated interruptions dominate; access can outrank payback when it opens a required system.

The current ROI calculator supports manual comparisons without embedding demo presets. Any launch recommendation added here must name the build, alternatives and reason the order changes.

  • Field bottleneck → compare field gains
  • Input backlog → compare refinery throughput
  • Repeated capacity stop → compare capacity
  • Required access → evaluate unlock value

FIELD NOTE 04

Promotion evidence still required

The full current upgrade tree must be verified with enough node names, effects, costs or qualitative dependencies to support recommendations. Magnet and Multi-barrel are officially named, but their current behavior is not yet enough for a ranked order.

Until those conditions pass, this useful framework remains PREPARED_NOINDEX and outside the sitemap. There is deliberately no separate upgrade-order URL.

EVIDENCE LOG

Sources