Syndicates

Syndicates

No one takes the Fugari home planet alone. No one holds a Trade Lane corridor solo for an entire cycle. At a certain point in Fugari Wars, the ceiling on individual capability becomes obvious, and the question becomes: who do you trust?

Syndicates are the game's alliance structure. Seats are limited — 8 by default, and never more than 50. A shared vault, shared intelligence, collectively owned planets, and — if someone decides the vault looks more valuable than their reputation — the potential for a betrayal that gets narrated to the entire galaxy.

Where to Find Syndicate Controls

Everything syndicate-related is under the Syndicate tab at the Nexus. From there:

• View the faction directory — the three NPC open factions plus any player-founded syndicates with open slots
• Join an NPC faction instantly, or a player syndicate with one tap
• Found a new syndicate if you meet the requirements (and you're at the Nexus)
• Manage the vault — deposit credits from anywhere, or withdraw at the Nexus (per-role limits apply)
• View active bonuses and your current syndicate's member count, commander, vault balance, and upkeep status

Why Join a Syndicate

Before the mechanics, the reason: syndicates change the shape of what's possible in Fugari Wars.

Shared node visibility means scan data your syndicate members have gathered flows to everyone. If your Officer scouted a port Coreward two sessions ago, you have that intelligence without spending a turn. This includes planets: a teammate's active scan of a planet shows on your planet panel (marked with whose scan it is and how old), and the newest scan from anyone on your team wins. If a member leaves the syndicate, their scans stop being shared with it, and they stop seeing the team's. At syndicate scale, this creates a collectively maintained intelligence picture that no solo pilot can match.

Shared planet access means your syndicate can work planets together. The planet stays the owner's personal asset — sharing is a toggle the owner sets, not a transfer to the syndicate — and the owner keeps sole settlement rights. What sharing grants members is extraction (at the 20% non-owner tax, below), docking, and battery and scanner exemptions.

The collective power of a well-run syndicate is not modestly better than solo play. It is a different game entirely.

NPC Open Factions

Each cycle, three factions are seeded at the Nexus with no joining requirements:

• Beacon — trade & shared intel
• Vanguard — combat & node control
• Drifters — reconnaissance & scan pooling

Any pilot can join an open faction immediately — no rep threshold, no turn gate, no cost. They function like player syndicates (shared vault, shared scan data) with two important differences: the Commander role is vacant (no one has unlimited vault access).

Open factions are the entry point for pilots who want syndicate benefits without the social overhead of a player-led alliance. They're also where pilot-founded syndicates tend to recruit from — a pilot who's proven reliable in Drifters is already a known quantity.

Founding a Syndicate

Founding a syndicate requires:

• 50+ lifetime turns
• 300 credits
• Physical presence at the Nexus

The founding pilot becomes the Commander — the only role with unlimited vault access. You set the name, you set the structure, you carry the responsibility.

Roles

Syndicates have three roles with distinct vault withdrawal limits:

Role assignment is the Commander's decision. Promoting to Officer gives real trust — choose your Officers based on demonstrated reliability, not familiarity.

The Vault

The shared vault holds credits only. It buffers against individual bad luck, enables coordinated pushes, and keeps the syndicate's planets operational through upkeep cycles.

Deposits can be made by any member at any time, from anywhere in the galaxy. Credits are digital — no Nexus presence required, no minimum, no role restriction. Anyone can fund the syndicate.

Withdrawals work differently. You must be physically present at the Nexus, and your role determines how much you can pull per reset: the Commander is unlimited, while Member and Officer caps scale with your rank tier — 50⬡ and 200⬡ at tier 1, rising to 3,000⬡ and 10,000⬡ at tier 9. The asymmetry is intentional: anyone can fund the syndicate, but only trusted roles can drain it.

The vault is the syndicate's operational reserve and its greatest vulnerability — to outside heists, and to your own members, any one of whom can leave with 30% of it. Keep it stocked enough to matter. Don't keep it so stocked that it becomes the primary reason someone considers betrayal.

Syndicate Upkeep

Every epoch, an upkeep fee is automatically deducted from the vault. The fee scales with your holdings: base_fee + (planet_count × per_planet_fee). Both values are set by game configuration and visible in the syndicate panel.

If the vault can't cover it, the syndicate enters a deteriorating state:

Any successful upkeep payment resets the consecutive miss counter to zero. Planet ownership and vault access remain intact during Warning and Dissolving states — the syndicate is limping, not dead. But if no one funds the vault and the counter reaches ten, the outcome is the same as a Commander-initiated dissolution.

Keep an eye on the activity feed. A missed upkeep alert is the syndicate asking for a deposit, not a formality.

Syndicate Planets

In V2, planets have a single owner: either a player or a syndicate. The Commander initiates a Transfer to Syndicate action (must be physically present at the planet's node, costs 1 turn). From that point, the planet belongs to the syndicate, not to any individual member.

The Commander can also transfer a syndicate planet back — assigning it to a specific member, who then holds it as personal property.

What syndicate members can do on a syndicate-owned planet:

A few specifics worth noting:

• Extraction: Any member can extract drone surplus from a syndicate planet. The owner extracts tax-free; non-owner members pay a 20% extraction tax — see Planets & Citadels for the exact mechanics.
• Battery and scanner exemptions: Syndicate members are not fired upon by orbital batteries, and not flagged by orbital scanners, at syndicate-owned planets.
• Reactor install: Reactors are deposited by the planet's owner (any Hauler-or-higher hull can carry one). Sharing a planet grants members extraction, docking, and defense privileges — settlement deposits stay with the owner.

A well-placed syndicate planet is a forward supply point that every active member can use without routing back to a port. In late cycle, when turn pressure is highest, that advantage compounds.

Dissolution — The Chaos Mechanic

When the Commander dissolves the syndicate — or when ten consecutive upkeep epochs are missed — dissolution is instant. There is no grace period, no warning countdown at that final moment.

What happens:

• All syndicate-owned planets simultaneously lose their owner: owner_syndicate_id → null, owner_player_id → null.
• Garrison drones at those planets go autonomous. They now attack everyone — including former syndicate members.
• Orbital batteries on those planets fire on any player entering the node.
• Production continues ticking. Surplus accumulates with no one to claim it.
• Citadel features remain installed and operational. They simply have no owner.
• The vault is not distributed. Credits remain in the vault; access to them depends on whether any former member can claim the Nexus node.

The galaxy feed broadcasts: "[Syndicate] has dissolved — [N] planets have gone unclaimed."

Claiming a dissolved planet requires clearing the autonomous garrison through combat (no reputation penalty, no loot from garrison kills), then depositing cargo. The first player to deposit cargo asserts ownership and inherits everything: surplus, citadel improvements, orbital infrastructure.

This is an intentional design. A well-fortified tier 4 citadel that goes ownerless at dissolution is a contested event. Other syndicates will move on it. Former members may try to reclaim it. The chaos is the point.

Syndicate Activity Feed

The syndicate activity feed surfaces significant events to all members. Notable entries:

Betrayal — A Cautionary Note

Betrayal is an action available to any syndicate member.

It works like this:

1. You trigger the betrayal action.
2. 30% of the shared vault's credits are seized and transferred to your wallet — taken, not withdrawn. The transfer respects your wallet cap, exactly as a vault withdrawal does.
3. Every remaining member is alerted, and the alert names the amount you took.
4. You lose 100 reputation.
5. You are ejected from the syndicate instantly, and your betrayal count increases by one.
6. You cannot join any syndicate for 5 resets.
7. If you were the last member, the syndicate dissolves.
8. A SyndicateBetrayal event is enqueued for the Realm Report — Claude narrates it under your callsign, with the amount you took — and your defection is written to the public cycle feed.
9. Your betrayal count is public, on the betrayal leaderboard.

The Realm Report treatment is not a minor social consequence. Every active player reads the Realm Report. Your callsign will appear in a dispatch narrated by an omniscient voice that does not soften what happened. If your betrayal is particularly dramatic — Commander's vault drained at an unusual hour, a full syndicate dissolved — it will be the headline.

"RHEN emptied the Iron Passage Syndicate's vault at 03:14 UTC and vanished Trailward. The Commander's ship was last seen heading Coreward. No one is sure who's chasing whom."

This is not hypothetical. This is how betrayals get documented.

The question is never whether betrayal is mechanically possible — it is. The question is whether 30% of a vault, a rep crash of 100 points, and a 5-reset lockout are worth the galaxy's permanent record of what happened.

Some pilots decide it is. Some pilots decide it is at 03:14 UTC when they think no one is watching.

The galaxy is always watching.

Running a Syndicate Well

A few observations from cycles of collective play:

Activity is the primary metric. The intel and planet advantages only come from members who are actually playing. A syndicate with 50 enrolled members but only 5 active ones is not a 50-person syndicate in any meaningful sense. Recruit pilots who play regularly.

Upkeep maintenance is not optional. The vault needs to stay funded. Designate someone to monitor it, or set a norm where active members deposit after profitable sessions. A missed upkeep alert is recoverable; ten missed epochs is not.

The vault should serve operations, not accumulate. A large vault is a heist target — insecure vaults are drained galaxy-wide by vault heists, which is what the high-security toggle exists to prevent. Keep what you need for the next major push and upcoming upkeep cycles; distribute the rest to active members.

Planet strategy requires coordination. Syndicate planets are shared assets. Decide as a group which planets to hold, which to colonize fully, and which citadel tiers to invest in. A tier 4 citadel built by collective effort is a collective asset worth defending — and worth thinking carefully about in the event of dissolution.

Shared intel requires shared communication. The game shares scan data automatically across members. But the galaxy-level strategic picture — who's latched, where the GPI stands, which lane is being contested — needs active communication. Syndicates that talk play better.

The betrayal risk scales with vault value. If you've built the vault for a coordinated endgame push, you've also built the most tempting betrayal target in the game — 30% of it walks out with whoever decides to leave. Know your members. Promote slowly. Trust is not a given, it's a track record. High security protects against outside heists, not against the people already inside.

A Note on Rogue Syndicates

Syndicates require rep ≥ 0 to found, but members can slip below that threshold after joining. A syndicate can operate with members ranging across the rep spectrum, though deep-rogue members will face trade penalties and port refusals that may complicate syndicate operations.

Full rogue syndicates — where the Commander and most members are Hardened or Outlaw — function differently. They rely on coordinated raids and operate in contested territory without Accord protection. They're less stable (the rogue path's trust dynamics make betrayal more likely) but potentially devastating as a late-cycle raiding force. If a rogue syndicate coordinates an assault on the Fugari planet with Heretic-class hulls, they are among the most dangerous forces in the galaxy.

They're also the most entertaining entries in the Realm Report.