Quick answer
First separate four things: the settlement's current Cohesion, passive upkeep consumption, whether supplies reach the affected Pirate Camp, and the current cost and reward shown by an event choice. The publisher FAQ says Cohesion is gained primarily from events, while the official Resources page explains that upkeep consumes stock passively and stable supply needs stockpiles plus net production that outpaces consumption.
That means a supply fix does not itself promise a Cohesion gain, and an event opportunity does not repair a failing production or delivery system. Stabilize the visible upkeep bottleneck, then use suitable event opportunities for Cohesion. Do not rely on a hidden threshold or guaranteed mutiny-prevention number; the approved sources do not provide one.

Original guide diagram — not in-game UI. Cohesion recovery and upkeep delivery are related pressures, but they are not the same diagnostic.
The progression or diagnostic path
- Read the Cohesion state. Treat it as the settlement problem you are trying to recover, not as a physical upkeep item.
- Inspect upkeep stock and trend. If a consumed resource is falling, determine whether production is below consumption or the stockpile is too small for current demand.
- Inspect the affected camp. The official Buildings page currently says a Pirate Camp houses and supplies its workers, while resources can be transported from elsewhere on the island. Because that detail comes from one official page, use it as a patch-sensitive delivery check rather than a guaranteed fix.
- Review available events. The publisher FAQ currently says events are the primary Cohesion source. That is a single publisher FAQ statement, so recheck after event-system patches.
- Read the live event choice. Compare any cost shown by the event with current reserves. This guide does not publish fixed event costs or outcomes that are absent from the evidence package.
- Make one recovery change and observe. Separate a supply improvement from an event-based Cohesion change so you can tell which problem moved.

Original guide diagram — not in-game UI. Stop at the first visible bottleneck instead of changing every system at once.
Decisions, unlocks, or fixes
| Observed problem | What the source set supports | Bounded recovery action |
|---|---|---|
| Cohesion is the visible concern, but upkeep is stable | Events are the documented primary Cohesion channel | Review available events and choose only after reading the current cost and effect |
| An upkeep stockpile is shrinking | Passive consumption must be covered by stock and net production | Reduce new demand and improve production before relying on the buffer |
| Production exists, but the affected camp still lacks supply | Camp supply and island transport are separate checks in the official Buildings page | Inspect the camp's supply state and the route bringing resources to it |
| An event is available but its cost threatens reserves | The evidence does not support a fixed “always take it” rule | Skip or delay the choice when the live cost would deepen the active shortage |
| Several indicators changed together | The source set cannot identify the cause from a single snapshot | Change one variable, observe, then continue the diagnosis |
The publisher FAQ also currently says advancing produces more frequent and varied events. Because this is one official FAQ record, it is useful context—not a promise that a specific event will appear on demand. Keep a settlement stable enough to wait for opportunities without assuming an exact schedule.

Original guide diagram — not in-game UI. Recovery is a sequence of observable checks, not a guaranteed one-click cure.
Common mistakes
- Treating low Cohesion and an empty upkeep stockpile as the same variable.
- Assuming more production solves delivery to the camp without checking whether the resource reaches it.
- Spending reserves on an event without reading the current cost shown in the live choice.
- Publishing or following a fixed event cost, Cohesion threshold, or guaranteed mutiny rule that the approved sources do not establish.
- Expanding crew or buildings while passive upkeep consumption already exceeds supply.
- Changing production, routes, camp demand, and event decisions together, then losing the ability to identify the real bottleneck.
FAQ: Frequently asked questions
How do I increase Cohesion?
The publisher FAQ currently identifies events as the primary source. Because that statement is carried by one official FAQ, treat it as version-sensitive, inspect the current event text, and avoid assuming a fixed gain or schedule.
Will fixing food, drink, or another upkeep item automatically raise Cohesion?
The evidence package does not establish an automatic one-to-one increase. It supports a separate upkeep model: resources are consumed passively, and stockpiles plus sufficient net production keep supply stable. Fix the shortage because it is a settlement bottleneck, while handling Cohesion through its documented event channel.
What event should I choose to stop a mutiny?
No universal choice or numeric threshold is supported here. Read the live cost and effect, compare the cost with current reserves, and avoid an option that worsens the supply failure you are already trying to repair.
What to do next
- Use the population management guide to check camp reach, housing, jobs, and local support before adding more crew demand.
- Follow the logistics guide when the main problem is moving upkeep resources between production, storage, and the affected camp.
- Return to the progression roadmap only after the settlement is stable enough to take on another Deed or Compass objective.