Bills Must Be Paid Piggies

Piggies are both the target and the source of uncertainty in Bills Must Be Paid. The official Steam listing says that different types behave differently, piggies spawn random loot and rare coins can be collected. The developer page adds player-facing names and examples, but neither source turns a short list into a fixed drop table. This hub helps you read the field and keep claims scoped to the current build.

Identify before committing stamina

Some piggies move, some are lazy and some carry unusual rewards. A moving target can cost more stamina if the hammer radius is small. A stationary target can be a safer payment route even when its reward is less exciting. Read Piggy Types for behavior notes and Random Loot and Rare Coins for variance, testing and collection decisions.

Random loot changes the route

The same piggy type can produce a different result, so one run cannot establish a guaranteed amount. Use the field to choose risk: when a bill is close, prioritize reliable contacts; when the bill is safe and stamina is healthy, a riskier target can be a reasonable experiment. Keep a note of the target, build and observed result instead of claiming an exact probability.

Pair targets with hammers

A wide radius may make moving piggies easier to hit, while speed helps recover from misses. A high-damage or critical hammer can reward deliberate targeting. The Hammer Comparison page shows how to test these pairings. The right choice is the one that creates enough value for the next bill without exhausting the run.

Source policy

Target types, random loot and rare coins are confirmed in the [official Steam listing](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Official Steam listing” rel=“nofollow ugc”) and expanded with terminology from the [developer product page](https://rikegames.com/bills-must-be-paid “Rike Games product page” rel=“nofollow ugc”). Drop tables, rare-coin odds and exact target values remain live-check.

Reading the field as a risk budget

At the beginning of a run, use a familiar piggy to establish how the current hammer and controls feel. Once the next bill is safe, use a different behavior as a controlled experiment. This matters because an unknown target can consume stamina before you understand its movement or hit response. If it drops something unusual, record the event without assuming the same type always does so.

Piggy behavior also affects where you stand. A moving target may require a shorter chase when the hammer has a large radius, while a narrow-radius weapon rewards a clear approach. A lazy target can be stable income when the hand is tired. The choice is not a permanent ranking; it is a trade between travel, accuracy, loot variance and bill pressure.

Index rules

Use one row per type with fields for behavior, reward wording, movement, current availability, source date and confidence. “Confirmed” should describe only what an official page or repeatable live screen supports. “Community-observed” is useful but not official. “Unknown” is better than an inherited value from a different game.

From index to decision

The index should help a player choose a target in the next minute. If a bill is close, surface the types that are easiest to contact in the current build. If stamina is low, surface the types that require the least travel. If a player is testing rare coins, surface the type names and collection screen without calling the route guaranteed. This is more useful than sorting piggies by an unverified reward number.

Avoid false completeness

The developer page may name only a sample of the piggies, while the full game can add more. Mark the index as partial when the source does not prove a complete roster. Do not create an empty “all piggies” table simply to capture a search phrase. Add a row only when identity or behavior has evidence, and leave missing values as unknown.

Cross-links that preserve context

Readers who need action should continue to Hammers or Stamina and Controls. Readers who need rewards should continue to Random Loot and Rare Coins. Readers who need a payment decision should continue to Bills. These links preserve the reason the target matters and keep the piggy page from pretending that behavior alone determines the best route.

A target decision in context

Choose a piggy by the task at hand. A bill may favor reliable contact, a low stamina bar may favor a nearby target, and a rare-coin test may favor observation over income. Write down the reason for the choice so the result is not mistaken for a universal ranking. This is also the safest way to compare a base-game screen with a demo observation.

When a roster changes, preserve the old note and add a dated current note. Do not replace a missing behavior with a guessed label, and do not use a visual asset as proof that a type is currently available. A small, evidence-backed index is more useful than a complete-looking list that merges teasers, demos and the full release.

For route planning, pair the piggy observation with the hammer, stamina and bill pages. The same target can be useful for income in one run and poor for a rare-coin test in another. If the field becomes unsafe, stop collecting anecdotes and protect the payment decision. A player can return to a target after the evidence is clear; a lost run cannot be replayed with the same random result. The index should make that trade-off visible before the player commits to farming.