The official Steam page says Bills Must Be Paid includes different piggy types: some run away, some are too lazy to move and some carry the game’s unusual “black money” joke. The developer page names examples such as Normalito, The Tourist, Woody, Piñata and El Loco. Those names are useful search terms, but their exact rewards, movement rules and availability can change.
Behavior categories
Think in behavior categories first. A stationary or lazy piggy is usually easier to line up, which can make it useful when stamina or bill timing is the problem. A moving piggy tests reaction and radius; it may be worth targeting when the current hammer handles movement well. A reward-marked or unusual type should be treated as an experiment until the current build confirms its drop. A rare label is not a promise of a fixed percentage.
A safe testing method
Before testing, note the game version, hammer, bill state and stamina. Target the same type over several ordinary runs, and record contacts, time spent, money or loot shown, and whether the target causes a detour. Do not use a lucky single drop as a rate. If the result affects a payment decision, test in a low-pressure window first.
Movement and radius
Moving piggies make hit radius and swing recovery more important. If you miss, ask whether you need a wider hammer, a faster swing or a better approach angle. Changing all three at once makes the result hard to understand. Read Hammer Comparison and Stamina and Controls before assuming the target itself is the issue.
Source and scope
The broad behavior comes from the [official Steam store page](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Official Steam listing” rel=“nofollow ugc”). The example names and player-facing descriptions come from [Rike Games](https://rikegames.com/bills-must-be-paid “Rike Games product page” rel=“nofollow ugc”). Exact movement, rewards and unlocks are live-check.
Target notes for a real run
When a piggy moves, observe whether it changes direction, crosses the useful field or forces a long chase. When it is lazy, observe whether a stationary position lets you maintain a clean swing rhythm. When its name suggests a special reward, inspect the resulting item and where it appears. These observations help choose a route without claiming every instance behaves identically.
Keep names and behavior separate
A type name can be confirmed by a developer page while its current reward remains unknown. A screenshot can show a behavior while failing to prove availability in the base game. Keep two fields in the index: identity evidence and current behavior evidence. This prevents a remembered demo target from becoming a permanent base-game rule.
When a type deserves its own page
Create a dedicated child page only when players have a distinct decision about movement, loot or payment value. Do not create empty pages for every name. A short verified index is better than a directory full of copied labels and missing drop data.
When evidence is sparse, keep the type in the index with an unknown field and link to the update tracker for future confirmation.
Never infer rarity from screen size, color or a single unusual reward; those visual clues need a current source.
If a type appears only in a teaser or demo discussion, list it as a lead rather than as a current base-game entry.
That distinction prevents an exciting preview from becoming a false roster claim.
Keep the preview date beside the lead until the base-game screen confirms it.
This avoids false certainty and keeps the index honest when new builds add or remove behavior.
Record behavior without overclaiming
For a current observation, write the product, build, target name, movement, number of contacts, stamina state and reward screen. Repeat the check before describing a pattern. A useful type note tells the reader what to watch for while leaving unverified rarity, drop rate and persistence clearly unknown. Include the observation date when a new type appears. This makes the page auditable and easier to update safely.