Sharing, Coalitions & Factions¶

Most things in Foxlogi can be shared — and the boundary where sharing stops is enforced by the server, not by trust.

What problem it solves¶

Foxhole is won by coalitions, not regiments. A frontline hex is usually held by three or four units who need to know each other's stockpile codes, cover each other's timers overnight, and avoid double-supplying the same bunker while another one starves.

But sharing logistics data is genuinely dangerous. Stockpile passcodes are the crown jewels; a leaked code empties a depot. And in a two-faction game, data reaching the other side is worse than useless — it's a weapon.

So regiments default to sharing nothing, coordinate badly, and lose hexes to logistics failures that were entirely avoidable.

Foxlogi's answer is granular, explicit, revocable sharing with a hard faction wall underneath it.

What can be shared¶

Object	Shareable	Notes
Stockpiles	✅	Per-regiment, with notify on expiry and exclude from planner toggles
Timers	✅	Per-regiment, with notify on expiry
Supply tunnels	✅	Per-regiment, with notify on expiry
Logistics requests	✅	Allies see the request and can fulfil it from their board
Bunker bases	✅	Or made public to the whole faction
Facilities	✅	Including which items they produce
Intel markers	✅	Public within your faction by default
Templates, action logs, member lists	❌	Always regiment-private

Every shareable object's form has the same control:

1 — Named regiments¶

Pick specific allied regiments from the dropdown. They see the object; nobody else does.

2 — Coalition, in one click¶

The + NC button shares with every regiment in your coalition at once. Coalitions are first-class in Foxlogi: a regiment belongs to one or more, and the quick-add button appears automatically. When a new unit joins the coalition, you don't go re-share fifty objects — but the sharing that already exists stays explicit and visible.

3 — Public¶

is_public makes an object visible to your entire faction. This is how public stockpiles and public bunkers work, and it's what lets Bunker Supply hand a brand-new member a runnable job from a pile they can actually open.

Note the precise meaning: public means public within your own faction, never globally.

Sharing isn't a single on/off. Each share carries its own options:

Notify on expiry — should this ally's Discord get the alert when the timer runs down? Useful for the ally covering your night shift; noise for one who just needs read access.
Exclude from planner — an ally can see your stockpile without Foxlogi counting its contents toward their own supply calculations. Prevents two regiments both assuming the same 200 crates are theirs to spend.
Notification group — which of the ally's channels and roles the alerts land in.

That last one is what makes shared timers actually work across a coalition: your battleship timer reaches their naval channel and pings their naval role.

Intel markers are the most collaborative object in Foxlogi — enemy sightings placed on the map, public within the faction by default, with a comment thread anyone can add to.

Spotted at — when it was first seen
Confirmed by / Last confirmed — the freshness signal that matters. Two-day-old intel that nobody has re-confirmed is a rumour, not a fact.
Comments — "Barge route blocked, use Loch Mor instead". Actionable context, not just a pin.
Confirm intel location toggle — re-confirming resets the freshness clock

Markers auto-expire so the map doesn't fill with ghosts: mine fields after 2 days, vehicles and other sightings after 5 days without confirmation.

Every intel modal carries the reminder: "Please use intel layer with responsibility, otherwise your regiment might lose access to it." Intel is the one shared surface where one regiment's bad behaviour degrades it for everybody, so misuse costs access.

The faction wall¶

Every regiment has a faction — Wardens or Colonials. This is the hard boundary:

Sharing targets are filtered to approved regiments of your own faction, server-side. Not hidden in the UI — rejected by the API.
is_public means public within the owner's faction.
The faction-wide Scoreboard only ranks your own side.
Item lists, vehicle names, ship names and map icons all follow your faction.
Templates record the faction they were built under and hide (rather than delete) if the regiment switches.

Changing faction¶

Regiments do switch sides between wars, so Foxlogi supports it — as a moderated request:

Faction changes are reviewed by Foxlogi moderators before being applied.

Requesting a change doesn't grant anything. A moderator reviews it. That's what stops the obvious attack — flipping faction mid-war to read the other side's shared stockpiles, then flipping back.

Regiments also have to be approved before they appear as a sharing target at all, which keeps throwaway accounts out of the picker.

Design summary¶

The pattern throughout is the same:

Nothing is shared by default.
Sharing is per-object and explicit — you always know what you gave away.
Shares carry settings, so "visible" and "counted" and "notifies" are separate decisions.
Shares are revocable at any time.
The faction boundary is enforced on the server, and crossing it requires human review.

That combination is what makes a coalition able to run shared logistics without any single regiment having to bet its stockpiles on everyone else's discretion.