Terror AustraliZ Roleplay Lore Rules Characters

Terror AustraliZ RP Rules

Updated 2026-10-07: clarified FailRP

Introduction

Welcome to Terror AustraliZ RP. By joining this community, you are stepping into a shared story where immersion, respect, and fairness are essential. To keep the experience enjoyable for everyone, all players are expected to follow the rules outlined in this document.

These rules are mandatory, and violations will result in disciplinary action under our Two-Strike Policy:

By playing here, you agree to uphold these rules and respect both the staff and your fellow survivors. Repeated or severe misconduct will not be tolerated.

Above all else, it is expected that people who participate in this community are engaging in good faith to play a 15 year old game that we all adore.

We just expect you to be someone who is fun to be around.

Discord Rules

1. Respect the Community

Treat all members with respect. Harassment, hate speech, discrimination, and or toxicity will not be tolerated. If you are seen as a detriment to the community or if you are known as a toxic or unliked person, you will be removed from the community. In the event that you are a toxic member of the community, staff will privately discuss the matter and will permanently ban you if necessary.

2. Follow Discord's TOS

Any violations of the Discord TOS will resort in a permaban from the Discord, and by extension, the PZ server.

3. Separate In-Game Roleplay (IC) and Discord Chat (OOC)

4. Staff Authority

5. Have Fun

This is a collaborative story. Respect your fellow players, contribute positively, and enjoy the experience.

In Game Rules

NOT KNOWING THE RULES IS NOT AN EXCUSE FOR BREAKING THEM.

1. Absolutely No AOGM (Abuse of Game Mechanics)

Do not exploit game mechanics to gain unfair advantage. Do not loot horde, do not loot cycle, and in particular, do not abuse PZ's isometric camera and the use of Z levels to shoot other players in PvP when they cannot shoot back.

Please ensure that when engaging in PVP combat, that you are able to be targeted by the other player in order to ensure fairness. All players involved in PvP must be able to fight back.

2. No Metagaming

Do not use OOC knowledge to benefit your character IC.

Example: Acting on information you only saw in Discord or streams, not discovered in-game.

If you believe a staff member is metagaming, please open a ticket. If you believe it is necessary, please DM a higher admin to resolve your issue after making a report ticket.

3. No Powergaming

Do not force actions on other players without their consent.

Example: "I tie you up instantly, you can't resist" = not allowed. Always allow counterplay.

If you believe a staff member is powergaming, please open a ticket. If you believe it to be absolutely necessary, please elevate your issue to a higher admin via DM to resolve your issue after making a proper report ticket.

4. No Cheating

Third-party hacks, scripts, or macros that give unfair advantages are strictly forbidden. This includes ESP, aim-assist, item spawning, or speed hacks.

Other examples: Clipping through walls, item duplication, or using exploits to benefit your character or disadvantage others.

5. ERP (Erotic Roleplay) is Forbidden

Explicit sexual roleplay is not allowed in-game. Any ERP will be met with an instant, permanent ban.

6. KOS (Kill on Sight) is Forbidden

7. RDM (Random Deathmatch) is Forbidden

8. Character Continuity Must Be Respected

9. Showing No Value For Life (NVFL) is Forbidden

10. Do Not Destroy World Tiles Without Staff Permission

You may not destroy, dismantle, or bypass any tile or structure not owned by a player without prior approval via a lore ticket. See the full rule under Tile Destruction & Structure Access Rules.

11. Don't Argue With Staff

Staff have the right to pause or overrule RP if rules are broken. Players may query rulings to senior staff or the server owner, but should do so in a ticket or DM and not during a scene or publicly in Discord.

12. Don't FailRP

FailRP is a catch-all term for when players don't engage with the roleplay in good faith and or have their characters do things in game that would cause other players to be unable to suspend their disbelief. Stay in character. Be realistic, react to the world around you, don't ignore RP, and embrace your character having limitations or flaws. See the full rule under FailRP.

13. No Ruleplay / The Catch-All Rule

Ruleplay, or a ruleplayer, is defined as someone that consistently drags people into tickets without caring whether a rule was broken or not. Players that seek only to report other players after player interactions will be warned and banned if their actions are considered toxic or a detriment to the community.

This rule is also in effect for players who seek to use the words of the rules in order to circumvent the spirit of the rules by technicality. Players are expected to abide by not only the letter of the rules, but the spirit of the rules as well.

Staff are volunteers and this server is run for you for free! Please keep that in mind and we all will have fun.

Communication & Roleplay Rules

This server is a mixed VOIP and text RP server.

Players must not ignore or downplay interactions initiated through TextRP.

All communication within the game world is required to be In-Character (IC) at all times, with the exception of communication using OOC chat, which is accessed using the /ooc or /o command.

In-game OOC communication must be used sparingly. /ooc has a very wide radius and so it can be very disruptive.

In-Character Communication

When Is OOC Permitted In Game?

Permissible examples of OOC use:

A. Real-Life Emergencies: medical emergencies, family emergencies, fire, evacuation, or immediate danger.

B. Consent & Safety Checks: OOC must be used to seek consent for sensitive RP content such as torture.
Example: /ooc Are you okay with a torture interrogation scene? Once consent is given or denied, all RP must immediately return to IC.

C. Advising About Bugs Requiring a Relog, etc.: OOC may be used to advise that you are experiencing gameplay issues (e.g. /ooc I'm desynced, /ooc I need to relog). If you need to step away from your computer, it's acceptable to use OOC to advise this, but please also walk your character out of a room where possible, and log out if you'll be AFK for more than 10 minutes.

Discouraged in-game OOC discussions (these belong on Discord instead):

Excessive OOC-fests in game may be punished.

Character/OOC Bleed

Character bleed is when what happens IC starts to affect you OOC, or conversely, when your OOC feelings start to affect your character's IC actions. If character bleed is affecting you negatively, you should take a break.

Staff May Use OOC

Staff may interrupt RP for rule enforcement or emergency moderation. If staff speak OOC in-game, listen to them. If you disagree with a staff decision, do not argue in-game; open a ticket.

Torture Rules

Torture is the deliberate infliction of severe physical or mental pain, typically used to punish, extract information, coerce a confession, or intimidate. Torture RP is not explicitly banned, however consent should be sought before broaching what could be a triggering concept.

ERP is never permitted.

Agreeing to "blackscreen" through a violent scene is acceptable and serves as a safety tool for managing comfort levels and graphic content; the players acknowledge a violent act occurs, but deliberately skip the graphic details and go straight to the aftermath.

  1. Consent First, Always: Torture RP requires OOC consent from all involved players, including bystanders (confirmed in text chat, e.g. /ooc hey, Jack. Do you consent to your character being beaten?). Either side may open a general ticket for moderator overview.
  2. Boundaries & Respect: Players may withdraw consent at any time. Preferring to blackscreen content is always acceptable (e.g. /ooc I'd like to blackscreen Jack's beating.). Torture RP must immediately stop if consent is revoked; blackscreen it instead. No ERP (sexual torture) of any kind is permitted.
  3. Narrative Purpose: Torture must serve a narrative or roleplay function (interrogation, intimidation, psychological warfare). Do not use torture as an excuse for griefing.

FailRP

FailRP (Failure to Roleplay) occurs when a player breaks character or acts in ways that are inconsistent with roleplay expectations.

Examples of FailRP include:

Staff Response to FailRP: addressed case-by-case depending on severity and frequency. Minor incidents may result in a warning and guidance; repeated or severe FailRP may result in more serious consequences, including loss of lives or even character death.

Character Death & Zombie Bites

In Terror AustraliZ, if something causes your character to respawn or mechanically die, you do not necessarily have to kill your character off; you can choose to respawn as the same character (assuming you still have lives left, see below). A mechanical death is also known as being downed.

Being Permanently Killed (PK'd) means your character is permanently dead and you have to make a new character. If your character is PK'd, post in the #obituaries channel in Discord as soon as possible so other players know the death is IC.

Any new character must be completely unrelated to previous characters. Your new character has no knowledge of what previous characters knew and cannot benefit from your previous character (don't loot your old stuff). You cannot rejoin the same faction without staff permission, and typically staff will only permit this after 2 OOC weeks.

Zombie Bites / Infection

This season, a mechanical bite will be treated as an IC bite (unless a result of desync or other bug; open a general ticket if so).

If bitten, you must open a lore ticket in Discord. The outcome will be determined in the ticket per the season's lore.

The Two Lives System

Each player character has two lives mechanically; you can respawn once for any reason without losing the character.

A life is lost every time your character is downed, regardless of cause (zombie bite, PvP, accident, etc.), unless you receive MedRP (see below). In addition, IC actions that show No Value For Life (NVFL) may be reviewed, and staff may determine a character should lose one or both remaining lives.

Lives are not lost due to characters downed by confirmed server bugs, exploits, or griefing by another player; open a general ticket for staff review if this occurs. It's recommended that players record their sessions where possible so mechanical deaths can be reviewed.

After losing two lives, that character is permanently killed (PK'd) and cannot be played again, unless MedRP is received. Players must create a new character to continue playing.

Medical RP (MedRP)

If a player character would have lost a life but instead receives Medical RP from a player character with a background such as a doctor, nurse, or other character with relevant medical training in their backstory, a lost life can potentially be restored or death/PK prevented.

A lore ticket should be submitted including who performed the MedRP, evidence of the MedRP (screenshots/video clip), and confirmation that the injured character is treating what occurred as a near-death experience. The MedRP should be performed as soon as possible, but if that means waiting OOC for player availability, that's acceptable as long as the RP supports it.

Character Death Conditions

A character is considered PK'd and permanently dead only under one of these circumstances:

  1. All Lives Exhausted: the character has been downed twice through normal gameplay.
  2. RP-Enforced Death: the character is involved in a situation deemed impossible to survive (e.g. bitten without cure/treatment, certain event scenarios, overwhelming combat, or narratively enforced consequences).
  3. Player's Choice: the player voluntarily chooses to permanently kill off their character, for story or personal reasons.

New Life Rule (NLR)

NLR only applies to characters downed as a result of PvP.

Respawning after PvP: unless the death is to be disregarded due to a bug, you should not return to the area you died for 1 OOC hour unless you receive MedRP. MedRP may be given by an ally or an enemy; if an enemy is present, an ally cannot give MedRP unless they realistically could. If MedRP cannot be given and the downed character isn't PK'd, it can be assumed they fled or otherwise escaped.

Players must not RP that they've killed a player character without confirmation that a PK has been made, typically from the downed player posting in #obituaries.

Being downed in PvP causes memory loss, even with MedRP. A downed character always has no memory of:

Example: "60 minutes before I was downed I was at Twiggy's bar so I could go there and ask what happened. 60 minute before I was shot the bartender, Billy Joe, was there as well as a few other people. OOC I know that the bartender shot my character, but IC my character doesn't remember that the bartender shot me or why."

A downed character may always remember:

If a downed character finds out about the attack from someone else (a third party who witnessed it, or the attacker tells them), they now know what they were told.

PvP Revenge Restrictions: you cannot seek immediate revenge for being downed or killed, and cannot use OOC knowledge of who killed you to target those players specifically. Unless your character was told by a witness, any future conflict with those players must be based on new IC reasons, not previous death circumstances.

Investigation Limitations: your character cannot immediately investigate the PvP, since they don't remember anything. Others may tell your character about it, and then you may investigate. If your character is PK'd as a result of PvP, you may never investigate the deaths of your prior character, and you may not use previous hostilities from a prior character as a reason to initiate hostilities.

Combat Rules

It's recommended that aggressors in hostilities use screen recording software. Without a recording, if combat is disputed, staff will likely rule in favor of the person making the complaint.

1. Initiation & Justification

You're expected to demonstrate escalating roleplay with another person prior to combat even being considered, and may be expected to justify OOC why your character was violent toward another person. If you cannot, this is likely to be found as FailRP or Random Deathmatching.

Initiation is the process that must happen before hostilities can progress to PvP. Before initiating on someone, you must have a roleplay reason (and roleplay interactions) with that individual to justify attempting to start combat with theirs.

An initiation is a statement delivered via text RP indicating an OOC intent to begin PvP. It must always contain a clear demand, a clear threat, and must be able to be heard by the "victim."

Because VOIP is buggy, while the escalating RP prior can be via text RP or VOIP, PvP initiations must always be delivered via text RP. Players are typically encouraged to initiate via /yell, since it ensures the target hears and understands the demand/threat. Initiating via /whisper or /say is permitted as long as the other party is within the appropriate distance to hear it, but is discouraged.

When you initiate on someone, you must give adequate time for them to react to your demands before you shoot; a countdown IC is fine, but make sure the other party is accommodated (time to type a response, etc.). If the other player complies and isn't a threat, you may not shoot them. However, if they take an overtly non-compliant action (such as attempting to run) or a hostile action (drawing, pointing, or shooting a weapon), you may freely engage.

Remember that when placed at gunpoint, FearRP/NVFL rules still apply; your character should fear for their life when a weapon is pointed at them, or suffer the consequences.

Examples of Valid Initiations:

(All of the above have a clear demand and a clear threat.)

Examples of Invalid Initiations:

The one exception to initiation rules is KOS Zones; see the KOS Zone Rules section.

2. No Combat Logging

Logging out during combat, capture, or while being pursued counts as combat logging and is strictly prohibited. If you disconnect due to technical issues, return as soon as possible and inform staff. If you have an IRL emergency and must disconnect, try to communicate that via /ooc or Discord as soon as you safely can.

3. Fair Engagement

4. Downed or Captured Players

5. Looting Player Characters / Corpses

6. Respect PvP & PvE Balance

Zombies are part of the environment and should factor into combat decisions. Reckless fighting without regard for infected threats may count as No Value for Life (NVFL) and lead to consequences, including PK.

KOS Zone Rules

KOS (Kill-On-Sight) Zones are areas designated by staff where standard initiation rules don't apply; players don't have to initiate or have RP buildup to open fire. Even so, this is still a roleplay server and your actions may have roleplay consequences.

KOS Zones are only created by server staff and may be added, removed, or altered at any time; keep up to date via Discord. Not knowing the zones is not an excuse.

In KOS Zones, the rules on Abuse of Game Mechanics (AOGM), FearRP, and NVFL still apply. Reckless characters are still subject to No-Value-For-Life consequences.

Base Raiding / Theft Rules

Staff will only investigate theft of items inside player bases and lore locations. A player base is marked by a note outside indicating it's a player base. Items outside player bases and lore locations are "fair game" for looting; that said, common sense applies.

It's recommended that screen recording software is used when initiating hostilities, since without a recording staff may err on the side of the "victim."

1. To Raid, You Must First Scout

2. Raid Initiation

Raids don't need to be announced in advance, but should be roleplayed. Before breaching a wall/door, a max-range text RP emote must be made; this counts as an initiation for PvP purposes if combat happens at the walls. All combat rules apply during raids (no combat logging, no AOGM, no RDM).

3. No Offline Raiding Without Staff Present

At least one of the following must be true:

4. Base Looting / Theft Rules

The point of a raid should be roleplay, not loot. Excessive looting or griefing is prohibited. Do not empty an entire base of all items, or destroy structures/containers without RP reason. Take what your raiding party can realistically carry and justify IC. Leaving a base stripped bare is considered griefing and will result in staff action. Vehicles may be stolen during a raid, as long as it isn't excessive relative to the other items taken.

5. RP Standards During Raids

Raiding must always be conducted with roleplay; breaking into bases silently without RP context ("ghost raiding") is not allowed. Capture, hostage-taking, or negotiations are encouraged if defenders are present. Torture/interrogation rules apply if captives are taken.

6. Staff Oversight

Staff reserve the right to intervene in raids that break rules or show clear bad faith. Players who feel unfairly targeted by repeated raids may request staff review.

Vehicle Rules

Players should not hoard an unreasonable number of vehicles. You may only have one vehicle and one trailer protected by a claim (a player-edited item, such as a piece of paper or bag, with your character's name on it). Unless you have OOC permission, stealing a claimed vehicle requires opening a ticket; theft of a claimed vehicle is only permitted if the car has been abandoned, unless following raiding rules.

To prevent empty cars littering the street, players may swap parts from unowned vehicles outside of bases, but may not remove them unless scrapping the vehicle entirely. To remove parts (not swap) and leave a wreck without parts, you must bring the vehicle back to your base; same goes for scrapping an abandoned car found on the street or in a town.

Vehicles are considered part of a base if parked on a property classified as a safehouse/base. It's a violation to remove vehicles from owned property, even unclaimed ones, unless following base raiding rules. You may not scrap parts from a vehicle you don't own unless it's present at your own base.

Vehicles can be considered abandoned if they're not near a base and have no note inside indicating ownership. If a vehicle has signs of being claimed, open a ticket.

Base Building / Player Safehouses

All players may request tilepicking and assistance with keys, though there may be material costs involved, and staff may place other IC requirements depending on what's requested.

Definition of a "player base": any location with a note outside indicating it's claimed is protected under raid rules as a player base. Players may open a general ticket to request their claim note be upgraded to an admin note. If players have blocked the first-floor windows with objects/barricades, they may also request a mechanical safehouse be placed over the building.

Base Building Rules

  1. Realism First: all bases must follow realistic physics. No floating structures, "sky bases," or designs that defy structural integrity. No building on water without staff permission.
  2. Size & Megabuilds: build size should be proportional to the number of players using the base. Bases attempting to contain large clusters of buildings (e.g. a wall three tiles wide surrounding an entire town) are prohibited unless approved. Megabuilds must be pre-approved by staff with a proper blueprint and RP justification. Staff reserve the right to stop or modify bases that are too large or immersion-breaking. Bases should typically fit within a 60-tile radius (the range of a /yell).
  3. Fortress Rights: players and groups have the right to build fortresses and heavily defended bases. Accessibility for outsiders isn't required. However, fortresses must still follow realism standards and may not abuse exploits.
  4. Defense Standards: realistic defenses only, no "impossible to breach" fortifications, and no structures that break zombie pathing. Fortresses should be tough but not rely on game-breaking mechanics.

Creating a Base

All bases must have a sign easily accessible to other players outside the base; at minimum a piece of paper that says "Claimed" or similar. Personalize it as you like (e.g. "John's House", "Anna's Abode", "Claimed", "Occupied"), as long as the message conveys the base is occupied. Reach out to staff when creating a base, as they may place unmovable markers or papers to prevent tampering. If you have compound walls or high fences, the sign must be outside them at a gate or entrance, even if no gate or door exists. All signs must be placed by the front gate or door; you're welcome to have multiple signs at multiple entrances, as long as the "main" entrance has one too.

Players are unable to base in locations significant to the lore or mechanics of the game, including high-value locations such as gun stores or hardware stores (this would disrupt the loot economy and cause unfair advantages), or locations important to a season's lore (typically marked with exclamation points, question marks, etc.). If uncertain whether a location is taken by lore, reach out to staff; you may not ask about lore locations preemptively, and you'll be required to post screenshots as proof your character has visited the location.

Players or factions may seek to make their base safehoused under vanilla PZ mechanics, provided they meet the minimum requirements: all first-floor windows (and sometimes doors) must be barricaded in a way that makes them inaccessible to players or zombies, via planks, bars, metal sheets, or blocking furniture (fridges, bookcases, etc.); cloth curtains or sheets don't qualify. Barricades must prevent entry without moving tiles or destroying barricades (itself illegal under these rules). An exception exists if the structure is fully surrounded by walls or high fences, in which case first-floor windows aren't required; but any such enclosure must be fully closed off via a gate or door, with no missing fences or walls. Low fences do not qualify for safehousing.

Road Construction

Road construction is permitted but regulated, to ensure fairness, visibility, and staff oversight, and to prevent griefing, unavoidable hazards, and immersion-breaking infrastructure.

Any player or faction intending to construct, modify, or obstruct an existing roadway must submit a construction request for staff review and approval before work begins. This applies to permanent, semi-permanent, or large-scale alterations affecting vehicle or foot traffic. Emergency or temporary barriers may be allowed at staff discretion, subject to review after the fact.

All approved road construction sites must include clear forewarning before the obstruction itself; visible signage, barriers, cones, or other reasonable in-world warnings placed far enough in advance to give approaching players time to react. Players aren't required to obey the warnings, but must be given a fair chance to see them.

Megastructure rules extend to road-based infrastructure: checkpoints, gates, toll points, fortified bridges, or integrated roadblocks count as megastructures, not standalone roadside builds, and must follow all existing megastructure limits, placement rules, and approval requirements.

Failure to follow these rules may result in removal of the structure, administrative action, or both. Repeated violations will be treated as deliberate disruption rather than ignorance.

Base Abandonment

Players wishing to claim an abandoned base should open a ticket for staff verification before taking action.

A base is considered potentially abandoned if it shows no signs of player activity for 14 consecutive OOC days. Staff will determine activity via a log check and reach out to the base's holder via ticket. If there's been no activity for 14 days and no response within 24 hours of the staff ticket, the base will be declared abandoned and any safehouse protections removed.

Tile Destruction & Structure Access Rules

If you can walk freely into an area, typically you can do so; this is true of player bases and lore sites, though common sense should apply. Any Discord announcement restricting play areas must be followed.

1. Do Not Destroy Tiles You Do Not Own

Sledgehammers and other tools capable of destroying tiles, walls, containers, or barriers may only be used on player-constructed builds. Base Raiding Rules apply when destroying player tiles you don't own. Do not grief.

2. Do Not Destroy World Tiles Without Staff Permission

Destroying, dismantling, or bypassing any tile or structure not owned by a player is strictly prohibited without prior approval via ticket. This includes staff-built structures, environmental barriers, any area that appears intentionally inaccessible, and breaking into gun stores and other high-value loot locations that are inaccessible without breaking tiles. If you believe an area should be accessible, open a lore ticket before attempting entry.

3. Do Not Break Windows or Remove Barricades at Lore Locations

If a location appears to be tile-picked or is marked as a lore site, you must not remove barricades to gain entry or exit without approval in a ticket. If there's any question about whether a location is a lore site, ticket it.

4. Do Not Pick Up or Alter Tiles at Lore Locations

Lore locations may use unique props, items, or tiles. Players are not allowed to alter, remove, or modify props at lore locations, though certain furniture (such as barricades) may be removable at certain locations; ask staff if unsure, and depending on scale, you may need to open a ticket.

5. Do Not Alter Loot Spawns

Players are not allowed to remove, alter, or destroy tiles or storage items (crates, lockers, etc.) at locations that spawn important loot, such as military spawns, gun stores, or large warehouses that spawn hardware loot. Minor locations (like home garages) are a good, acceptable source for these kinds of containers.

Looting Rules

Our server does not have loot respawn turned on permanently; staff determine when loot respawn may be necessary.

1. No Loot Cycling

Loot Cycling is repeatedly looting the same containers or areas to force items to respawn, and is prohibited. First offense is a warning; being caught again after being warned results in a ban, with length depending on severity.

Legitimate resource gathering instead: use Build 42's crafting to create new items, trade with other players, establish supply lines, and create RP-driven resource acquisition stories. Explore new areas for resources rather than repeatedly farming the same locations.

2. No Loot Hoarding

Loot Hoarding is the accumulation of large quantities of loot without genuine in-character purpose, intended usage, or meaningful roleplay justification; including hoarding solely to prevent others from obtaining valuable resources.

Loot hoarding isn't permitted unless there's valid RP-based justification (e.g. an established trader faction or trade caravan). No faction may possess a stockpile deemed "unscrupulously large" by an Admin vote. If found guilty of loot hoarding, the faction or player may be required to provide sufficient justification or face administrative action, including redistribution or enforced reduction; staff will set a realistic goal for "max capacity."

Social Structure Rules

Terror AustraliZ uses a three-tier system to organize player social structures, from independent survivors to large organizations.

Lone Wolves & Independent Survivors

A Lone Wolf is any player operating outside an established Group or Faction. Independent play is a supported and valid playstyle here.

A lone wolf may cooperate informally with groups or factions without being counted toward that group's player cap, as long as the relationship is genuinely loose and IC-driven rather than a deliberate attempt to circumvent faction limits (i.e. they haven't formally joined and aren't sharing resources/safehouses with that group or faction).

No faction or group may use repeated, coordinated targeting of an independent player as a means of griefing rather than RP. There's a difference between organic IC conflict and sustained harassment designed to make a player's experience miserable; staff assess repeated targeting case-by-case.

Player Groups

A Player Group is up to 6 player characters operating together informally, sharing resources and safehouses. Groups may ally with factions or other groups but cannot merge beyond the maximum player limits. No staff approval required.

Groups may not act as a de facto faction (coordinated base, shared resources, organized conflict) while avoiding the Faction approval process; staff may require a group to formalize as a Faction if their activity warrants it.

Once a player group reaches six players, they may either seek to become an official player faction to expand their capacity, or stay at six members as a group.

Player Factions

A Player Faction is a staff-approved organization of up to 12 player characters sharing resources and/or basing in close proximity.

Approval process: factions must be approved by both an Admin and a Lore Master. Approval requires:

Player limit & server balance: factions are limited to a maximum of 12 players. Splitting into "sub-factions" to bypass this limit is prohibited.

Responsibilities: factions are expected to contribute to server lore and RP events, and must maintain some form of base of operations (subject to Base Building Rules).

Benefits: factions receive a Discord channel with an IC noticeboard, and can request events.

Conflict & Alliances: faction wars do not require staff review and may happen organically through RP. Alliances, however, are subject to staff review if requested (e.g. if two or more factions combine forces in a way that could upset server balance, staff may step in to review it).

Lore Factions

Lore Factions are staff-created organizations that exist to drive server narrative, and aren't subject to standard player faction caps. They're defined by shared ideology, goals, or history, not shared basing; members are distributed across the map and generally shouldn't operate out of a single base.

Lore Factions are created and administered by staff. Players may join one through approved IC means (application, in-game recruitment, RP milestone), but can't control the faction's overarching direction or goals.

Membership in a Lore Faction doesn't exempt a player from any other rules, including base building limits, combat rules, or the NVFL rule. A player who's a member of a Lore Faction may also be a member of a Player Group, but may not simultaneously hold formal membership in a Player Faction unless specifically approved by staff.

Lore Faction leadership roles (lieutenants, spokespersons, etc.) are assigned by staff per lore, and positions may be removed if the character (IC) or the player (OOC) doesn't meet the role's expectations.

Last updated by 5tac3