Upgrade desk · Evidence split

Choose upgrades by the job they do

A system-by-system reasoning guide that keeps confirmed features separate from editorial strategy.

Quick answer

Confirmed Buying upgrades is part of the core loop. Developer notes The full version includes desk gadgets and expands piggies, perks, and hammers. Strategy inference Prioritize the upgrade that relieves the current bottleneck while keeping the bill viable.

What is confirmed

SystemEvidence statusWhat we can safely say
Skill treeConfirmedIt exists; demo reports also referenced its interface.
Desk gadgetsDeveloper notesListed among full-version additions.
Piggies, perks, hammersDeveloper notesOfficial notes say the full version adds more of them.

Exact values, unlock orders, and a universally optimal build are not established by the supplied evidence, so this manual does not fabricate them.

A four-question priority framework

  1. What action repeats most?

    An improvement to a frequent constraint may be easier to observe than a situational benefit.

  2. What is limiting progress now?

    Name the bottleneck before comparing categories.

  3. Will the bill remain viable?

    An attractive improvement can be mistimed if it consumes needed runway.

  4. Can you observe the result?

    Make one legible change, retest, and update your priority.

Strategy inference This is editorial decision support, not an official formula.

Questions for each category

Skill tree

Which available choice targets the active constraint? Avoid assuming deeper always means immediately better.

Desk gadgets

What part of the desk loop changes, and can you notice that effect during normal play?

Piggies

Does the option change the earning task you currently perform most?

Perks

Is the benefit reliable in this run, or dependent on a condition you rarely reach?

Hammers

Does the choice improve the action that is actually slowing the loop?

Avoid false precision

  • Do not treat an unlabeled community tier list as confirmed game math.
  • Do not compare effects using values from an unknown version.
  • Do not let a long-term improvement erase awareness of the immediate bill.
  • Do not assume a full-version addition behaves exactly like a demo-era implementation.

Evidence used