Stamina is the boundary around every active decision in Bills Must Be Paid. The official Steam description says smashing costs stamina and that the run ends when the hand gets tired. That means control comfort, target distance and hit consistency are part of the economy. A player who spends stamina on missed swings may need a control adjustment or a wider hammer before buying a raw damage upgrade.
Check controls before optimizing
Open the current settings and control hints, then test a target without a bill deadline. Confirm how you aim, how the hammer swings, how you pause and how the game displays stamina. Do not assume a demo binding or a keyboard layout applies to every platform. If a control is remappable, choose a position that lets you read the bill and stamina UI without losing the field.
Spend stamina deliberately
At the start of a run, use a few safe targets to learn the field. When stamina falls, reduce travel and avoid a target that requires repeated misses. A fast hammer can help recover from mistakes; a wide radius can reduce them; a stronger strike can shorten the number of contacts. Use Hammer Comparison to test that trade-off. The goal is not maximum swings; it is enough value to pay the next bill and keep the route stable.
Read stamina with bill pressure
Healthy stamina supports a short delay before payment when income is reliable. Low stamina makes a bill more urgent because there is less time to recover from bad loot. When the collector is already taking a cut, stop treating a risky target as free. How to Pay Bills explains the decision layer.
Accessibility and troubleshooting
If the cursor, input or screen behaves unexpectedly, capture the platform, product, visible build and reproduction steps before reporting it. The Steam Community hub includes demo bug-fix reports, but a demo fix is not automatically a full-game rule. Check the current store and community posts for updates.
Sources
The stamina rule comes from the [official Steam page](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Official Steam listing” rel=“nofollow ugc”). Exact controls, stamina values and accessibility options are live-check.
A stamina audit
At the start of a test, note the current stamina display and take a small number of controlled swings. Check whether a miss costs the same as a hit, whether movement or waiting changes the bar and how the run announces exhaustion. Repeat with a different hammer only after the first behavior is understood. If the display is unclear, call the result unknown rather than estimating from a screenshot.
Input problems versus strategy problems
An input problem can look like weak damage because the hammer is not landing where expected. A strategy problem can look like a control problem when the target requires a different radius or approach. Reproduce the issue on a stationary target, then a moving one. If only one type fails, read Piggy Types. If every target fails, inspect controls and platform input first.
Reporting a reproducible issue
Include platform, base or demo AppID, visible version, input device, control setting, target type and exact expected versus observed result. Avoid account details or private screenshots. A clear report helps the developer and keeps the guide from treating a one-off issue as a universal mechanic.
Use the same minimum fields in a translated issue report so a player can reproduce the result across locales without changing the facts.
If the report concerns the demo, keep its AppID in the title and do not let the page imply that the base game is affected.
A short control test
Use one stationary target and one moving target with the same hammer. Check aim, contact response, stamina loss and the ability to read the bill screen. If the stationary test works but movement does not, investigate target behavior or radius; if neither works, investigate input and platform settings before changing the build. Record whether the test used the base game or demo.