Bills Must Be Paid Upgrades

Upgrades in Bills Must Be Paid are choices about the next run’s bottleneck. The official Steam listing describes a skill tree with grip strength, caffeine, gym, wrist and luck branches, plus abilities such as rock rain and an electrified hammer. The launch announcement adds longer-term systems around bankruptcy, prestige points, rings and bracelets. This hub keeps those layers separate so a temporary run upgrade is not confused with a permanent or post-bankruptcy system.

Choose by pressure

Use Skill Tree when you need to decide what to buy during ordinary progression. Ask whether the problem is stamina, missed contact, weak damage, slow clearing or inconsistent loot. Use the Hammer Comparison page when a weapon’s speed, crit chance, damage or radius is the limiting factor. Use Prestige, Rings and Bracelets after a reset or when the current build exposes the post-bankruptcy menu.

Why a fixed tier list is unsafe

An upgrade can be excellent in one field and awkward in another. A large radius may protect stamina by reducing misses, while a smaller radius with a higher critical chance can reward accurate targeting. Luck may be more valuable when your route depends on random loot, but less valuable when bills are due and you need reliable cash. A current build, player aim and objective all change the ranking.

Test one change at a time

Keep a short experiment log. Record the starting build, the upgrade, the problem it was meant to solve, and what changed. Avoid changing the hammer, skill branch and bill timing simultaneously; otherwise a lucky loot roll can look like a permanent improvement. Update this wiki when a dated official post or live-game screen confirms a new system, but keep observations labeled as community-tested rather than official.

Source boundaries

The skill-tree vocabulary is confirmed by the [Steam store page](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Official Steam page” rel=“nofollow ugc”). Prestige, rings and bracelets are described in the [Steam Community launch post](https://steamcommunity.com/app/4421010 “Official Steam Community hub” rel=“nofollow ugc”). Costs, unlock order, percentages and optimal builds require a current version check.

Build a testable upgrade plan

Start with a hypothesis: “I lose this run because the hand tires before the next payment,” or “I miss moving targets and waste swings.” Choose one branch or ability that could address it. Run the same broad route, then compare stamina remaining, contacts needed, payment status and the quality of the next choice. This is more reliable than measuring only money because a lucky piggy drop can hide a poor route.

Separate immediate value, repeat value and prestige value. Immediate value helps this run clear targets or pay a bill. Repeat value changes how often a problem appears in later runs. Prestige value matters after a reset and may unlock a different layer. A node can be strong in one layer and irrelevant in another. Keep notes beside the current build and date.

Upgrade language to watch

When the UI says a node affects grip, caffeine, gym, wrist, luck, rock rain or an electrified hammer, copy the wording exactly before summarizing it. Do not translate a flavor name into a numeric promise. If a patch adds a desk gadget, hammer or perk, place it in the correct layer and record the source. New content belongs in Updates first, then here once its purpose is stable.

A layered upgrade map

The first layer is the current run: stamina, contact quality, target clearing and bill payment. The second layer is repeat play: a branch or perk that makes a common problem less frequent. The third layer is post-bankruptcy progression: prestige points, rings, bracelets or a shop that the active base-game build exposes. A recommendation should name its layer because a player cannot spend a permanent accessory at the same moment as a run-only perk.

When a player asks for the “best upgrade,” ask one follow-up question: what ends the run? If the answer is exhaustion, test stamina or control changes. If the answer is missed movement, test radius or speed. If the answer is low reward variance, test a luck route without promising a drop. If the answer is collector pressure, test payment timing before buying a more expensive branch. This turns a vague query into an auditable decision.

Update handoff

New nodes, gadgets and perks should first appear in the Updates tracker with a source and date. Once the system is stable, link it here with current wording and a confidence label. This avoids silently turning a launch teaser into a complete guide.

Upgrade evidence record

For each purchase, record the product, build, branch or node name, cost shown, effect text, hammer, bill state and result of one controlled run. Keep the record qualitative when the UI omits a value. A dated record can be revised after a patch without rewriting the stable decision principle.

Upgrade advice should always state whether the purchase affects the current run, the next ordinary run or post-bankruptcy progression. That single label prevents a player from saving for an accessory when the immediate problem is a bill, or from spending a temporary perk as if it were permanent. It also gives the Updates page a clear place to record new systems before they become evergreen guidance.

If an upgrade looks weaker after a patch, compare the same hammer, target type, bill state and stamina window before rewriting the recommendation. A changed stat may be intentional balance, while a changed result may come from a different route or random drop. The hub can keep the decision principle stable and send the exact value to a dated update note.