Skip to main content

Factions concept

Factions are shared player teams with their own identity, members, rights, money pool, and shared operational tools.

What a faction includes​

A faction includes:

  • name, color, optional visual identifiers (armband/flag)
  • member list with custom access rights for each member
  • shared treasury (faction balance)
  • faction places (shared coordinates)
  • faction spawns (items spawned by the admins)
  • optional faction-linked base alarms
  • optional faction-linked subscriptions

Two permission layers in faction workflows​

Faction behavior is controlled by two layers:

  1. Server-level staff permissions
  2. Faction member rights (inside one faction)

Server admins can bypass regular faction-member limitations through broader admin-level rights.

Faction member rights​

Faction member rights are managed per membership and are separate from global user/group access rights.

Common faction member rights:

  • Server Admin (all faction member rights)
  • shown_as_leader
  • edit_details
  • manage_members
  • treasure_withdraw
  • treasure_deposit
  • place_order — can place shop orders charged to the faction treasury
  • change_base_alarm
  • change_subscriptions
  • manage_places

Treasury concept​

Each faction has a shared treasury.

  • Members can deposit and/or withdraw depending on their faction member rights.
  • Transactions are logged as faction transactions.
  • Members with place_order can place shop orders charged to the faction treasury (see below).

For the full balance model across players and factions, see Transactions concept.

Faction shop orders​

Members with the place_order faction member right can place shop orders paid from the faction treasury instead of their personal wallet.

  • At checkout, a Pay from selector appears listing the player's eligible factions alongside their current balance.
  • The player selects a faction to use that faction's treasury as the payment source.
  • The order is created as a faction order (not linked to the player) so it does not appear in the player's personal order history.
  • Faction orders appear in the Orders tab on the faction detail page, visible to all members with place_order, treasure_withdraw, or treasure_deposit rights, or to users with factions -> access_all.
  • The faction transaction log records who placed the order for audit purposes.
  • Refunds for faction orders are credited back to the faction treasury, not to any individual player.

Shared coordinates and operational objects​

Factions can maintain shared places and shared spawn definitions.

  • Places are reusable faction coordinates for operational workflows.
  • Spawns define faction-related item spawn setup points.

This allows teams to operate with shared map references instead of individual personal places only.

Integrations with other systems​

Factions can be tied into:

  • Base alarms (faction alarms and related notifications)
  • Subscriptions (faction-owned subscription entries)
  • Discord role sync for faction members

For alarm mechanics and rights details, see Base alarms concept.

Typical faction lifecycle​

  1. Create faction and set identity details.
  2. Add members.
  3. Assign faction member rights.
  4. Configure shared places/spawns.
  5. Use treasury and optional linked systems (alarms/subscriptions) as needed.