Contracts Guide (Quests and Bounties)

Quest System

Quest System Guide

Quests are the rhythm of your survival story: each offer pulls you onto a route, each objective tests your judgment, and each clean return turns risk, distance, and preparation into steady progress.

Core Structure

Quest flow follows a standard loop:

1. a settlement contact makes an offer
2. you carry the objective through real conditions in the field
3. the contract resolves: completed, failed, cancelled, or declined before acceptance

Your active quest capacity is strictly limited to three, so each slot should serve a travel plan and survival goal, not just a tempting payout.

Quest Portfolio Planning

With only three active slots available, think in routes, not impulse picks. Build a quest mix instead of random stacking:

• one dependable local contract you can finish even on a rough day
• one objective that pushes your route outward for better overall return
• a third only when it complements your current direction and time budget

Because some contracts can carry deadline pressure, opposite-direction objectives can quietly turn a full quest log into a failure chain. If your map plan starts fighting itself, your portfolio is overloaded.

Time and Deadline Discipline

In Last State, time is a real enemy: active contracts with deadlines can fail the moment the hour window is missed.

Treat every timed contract like a field operation:

1. estimate route time before you accept
2. reserve margin for fights, detours, and repairs
3. keep enough buffer to return without gambling your whole run

When a deadline is active, delay is not neutral, it is risk accumulating by the hour. Do not take distant timed work as a "future me" problem unless your route is already prepared for it.

Risk Matching by Build

Quest offers are shaped by who gives them (healer, trader, scout, guard, and others), so treat every offer as a match test against your current build and loadout:

• combat-ready runs: favor hunt, clear-bandit, defend, and escort pressure
• utility/trade runs: favor deliver, retrieve, gather, and resource-order contracts
• exploration-ready runs: favor explore routes and objectives that naturally chain with discovered points

When your contract type and your preparation align, momentum compounds. When they clash, the map taxes you with detours, missed windows, and preventable failures.

Reputation Synergy

Reputation is not flavor text in Last State, it is contract access. If your standing drops too far, NPCs can stop offering quests; if it stays non-negative, bounty boards remain open.

Reliable completions create a steady social runway:

• quest completion can raise settlement reputation
• missed deadlines and failed contracts can pull reputation back down
• stronger standing keeps more settlement interactions viable when pressure rises

Failure and Cancellation Mindset

In code and in play, contracts are tracked by outcome: complete, failed, or cancelled. A bad contract forced too long can cost more than a controlled reset.

Use cancellation as a tactical tool, not a reflex:

• cut early when route collapse is obvious
• stabilize with reliable nearby completions
• remember that failed or cancelled bounty-side contracts can trigger stricter consequences than ordinary quest setbacks

Common Mistakes

• locking all three active slots too early and losing flexibility when conditions change
• stacking distant timed contracts until deadline pressure outruns your route
• accepting before checking sustain basics (healing, ammo/tools, food/water, carry room)
• treating every offer as equal value instead of filtering by current loadout and direction
• pushing on after a run has clearly gone unstable instead of cutting losses and resetting locally

Practical Rule

A quest is truly "good" when it survives contact with reality: it fits your current route, your active-slot pressure, your loadout, and your recovery margin before the clock turns against you.

Bounty Board Quests

Bounty Board Guide

Bounties are the settlement’s hard contracts: high reward, high scrutiny, and little room for sloppy execution. Boards rotate on a longer cycle, acceptance depends on your local reputation, and every bounty still competes for the same limited active slots as regular quests.

System Traits That Change How You Play

• bounty boards refresh on a fixed 10-day in-game cycle, and posted offers expire on that clock
• your active contract ceiling is three total, so every bounty occupies real quest bandwidth
• failed or cancelled bounty-side contracts can trigger stricter repost/cooldown pressure and reputation setbacks

In practice, bounty play is less about grabbing everything and more about timing one clean contract you can finish before the board turns over.

When to Take a Bounty

Take a bounty when all four are true:

1. your settlement reputation is non-negative (board acceptance stays open)
2. your active contract count is below three (you still have slot bandwidth)
3. your loadout can survive expected contact
4. your route includes both entry and extraction without deadline panic

If one condition is missing, run stabilizing contracts first and come back when the board and your position are aligned.

Bounty Run Preparation Checklist

• healing depth for at least one ugly fight, not just ideal-case damage
• weapon readiness checked before departure (condition, ammo, backup plan)
• food/water margin that covers route time plus delay risk
• carry room reserved so objective and reward handling do not break your return
• a fallback extraction line if contact intensity spikes or timing slips

Board contracts are unforgiving by design: if you prep for the best case only, the timer, the route, or the fight will collect the debt.

Contract Selection Strategy

Prefer bounties that:

• fit routes you are already prepared to run
• match your current combat and sustain profile
• can be finished inside the board/offer time window without crowding your other active contracts

Because bounty offers expire and slots are shared across all contracts, selection discipline beats greed: take the contract you can close cleanly, not the one with the loudest payout text.

Failure Management

If a bounty goes unstable:

• decide early whether the run is still recoverable or whether to disengage before deeper loss
• avoid panic overextension that turns one failing contract into a wider health, inventory, and timing collapse
• remember that missed, failed, or cancelled bounty-side outcomes can hit reputation and contract availability
• rebuild local trust with reliable completions before stepping back into high-risk board work

Common Mistakes

• auto-accepting board offers just because they spawned
• stacking a bounty on top of long-route timed pressure until your three-slot log becomes a trap
• stepping in without a clear extraction line if contact, weather, or timing turns
• treating bounty contracts like disposable experiments instead of tracked commitments with social consequences

Practical Rule

In bounty play, clean execution beats contract volume: one controlled completion inside your slot, route, and time limits is worth more than two rushed attempts that end in failure state and lost trust.