Factions are the established player-facing organization type for persistent role membership, ranks, permissions, duty, internal chat, and shared funds. Faction membership belongs to the current character and is separate from casual employment, ordinary door or vehicle keys, and informal player groups.

Join through an invitation

LSPD and LSFD do not accept ordinary faction invitations. Apply privately through Discord and claim an approval on the exact character as described in Applying to LSPD or LSFD.

For other factions, an authorized faction member starts an invitation while near the intended character.

  1. Both characters should remain nearby and available.
  2. The inviter uses /invite for the intended character.
  3. The recipient reviews the displayed offer and accepts or declines it.
  4. Wait for the final membership result.
  5. After success, use /members and /ranks to understand the faction and entry rank.

A character already in a faction must leave it before joining another. Joining starts the character at the faction’s entry rank; it does not inherit another character’s membership or rank from the same account.

Invitations can expire or fail if either player disconnects, moves too far away, membership changes, or the inviter loses authority. Restore the scene and request a fresh invitation rather than assuming an old prompt still applies.

Use faction membership commands away from business premises. Some shared organization commands can select a business context while a character is standing at one.

Review members, ranks, and permissions

/members shows online members of the selected faction together with their rank and current duty marker. It is not a complete offline roster.

/ranks shows the current rank ladder and the capabilities assigned to each rank. A capability represents permission to perform an organization or role action. Seeing a command in help does not mean the current character’s rank is authorized to use it.

Capability identifiers are implementation-owned permission labels rather than a public promise that every related system is available. Use the owning feature guide for what an authorized action actually does.

Use faction chat

/f sends an internal message to online members of the same faction. The message identifies the speaker and rank within that faction.

Faction chat is not local speech, department radio, or a server-wide announcement. Keep character knowledge and appropriate channel use aligned with Roleplay and chat fundamentals.

Go on or off duty

Entering duty always requires the current rank’s duty permission. A faction that runs an armory, and any rank allowed to wear a service uniform, adds the armory conditions: be on foot at an active armory owned by that faction, in an ordinary controllable state, with an eligible uniform selected. A faction with no armory and no uniform permission enters duty from anywhere. The faction receives a visible update, /members marks the temporary state, and a service uniform is applied without replacing the saved civilian outfit.

Use /duty again to leave duty from anywhere. Exit remains available if the entry permission is later removed. Duty also ends with the session or membership and during hospital recovery; the saved civilian appearance returns without moving issued equipment. The draft organization duty and uniforms guide covers the current workflow and verification boundary.

Invite or remove members

Authorized ranks can invite eligible nearby characters through the offer flow. Always confirm the intended target and wait for acceptance before treating them as a member.

An authorized member can use /uninvite to remove an online lower-ranked member. Peers and higher-ranked members are protected from this subordinate-management flow. Recheck /members after the final response rather than relying on the command being sent.

Membership removal ends that character’s faction rank, capabilities, duty state, and internal chat access. It does not automatically alter unrelated job employment or separately granted keys.

Assign an existing rank

Use /rank to place an eligible online subordinate into an existing lower-authority rank. Review /ranks before selecting the destination and again after the final result.

Faction leaders with the required authority can use /orank for the currently registered rank-management actions, including adding a bottom rank, renaming an existing rank, changing its payday amount, and changing capabilities on eligible lower ranks. Rank removal is not supported.

A configured rank amount is considered during an eligible payday, but funding policy, duty requirements, and other memberships can affect whether it pays. The self-funded and public-duty payroll paths still await their real-client walkthrough, so do not treat a configured amount as guaranteed income. The draft ATM, payday, and earnings guide records the current verification boundary.

Rank changes affect the permissions inherited from that rank. They do not create ordinary entries in /keys and should not be used as a substitute for the access flow owned by another system.

Use the shared faction bank

/obank can show the selected faction account balance from anywhere. At the configured bank counter, deposits move funds from the member’s personal bank account into the faction account; any member can contribute. Withdrawals there move funds back to the acting member’s bank and require the appropriate rank authority. Configured active ATMs can also provide the transfer context when available.

Faction banking does not use carried cash. If a transfer result is unclear, compare /obank with the personal bank balance before trying again. Do not issue repeated withdrawals or deposits while a previous result is still unresolved.

Leave a faction

A non-founder can use /leave away from business premises to end their own faction membership. There is no invitation or confirmation prompt, so use it only when ready and recheck /members after the response.

A founder cannot abandon the faction through the ordinary leave flow while still responsible for it. Follow the refusal and arrange a formal leadership resolution before retrying.

Leaving removes the character’s faction rank, capabilities, duty, and faction-chat access. It does not return after reconnecting. Use /leavejob, not /leave, when changing a casual job.

Recover from common refusals

  • Invitation fails: confirm that this is not LSPD or LSFD. For another faction, keep both players close and available, confirm the inviter still has permission, and create a fresh offer.
  • A character is already in a faction: they must resolve that membership before accepting another faction invitation.
  • A command reports the wrong organization context: move away from the business premises and recheck the faction before retrying.
  • A member cannot use an action: review /ranks; membership, rank, capability, and sometimes duty are separate checks.
  • Removal or rank change is refused: confirm the target is online, in the same faction, and below the acting member’s authority.
  • Duty is refused: confirm the rank has duty permission. Where the faction runs an armory, also return on foot to an active armory it owns with an eligible uniform; incapacitation, restraint, an outfit preview, or unresolved duty state blocks entry there.
  • A bank result is unclear: recheck both organization and personal bank balances before another transfer.
  • Leaving is refused for the founder: do not repeat the command; resolve leadership responsibility first.
  • A mutation result is unclear: reopen /members or /ranks and confirm the authoritative state before repeating it.

For inter-agency radio and public official communications, continue to Department and government communication.