Founding Charter · Community Policies Rev. 1.1 · Aviation Manual 1.0

Rules & Charter.

Everything that governs One State Network, on one page: the Founding Charter, the community rulebook, and the Aviation Operations Manual. They apply to every member, every rank and every department, in the city and on Discord. Read it once, properly. “I didn’t know” isn’t a defence.

7charter articles10policy sections59rules
AuthorityFounding Charter, §3.4
Enforced byCommunity Staff & above
Golden ruleRoleplay first. Always.
  1. 1Founding Charter
  2. 2Community policies
  3. 3Department SOPs

One State Network is governed by its Founding Charter. This rulebook is issued by the Directorate under Charter §3.4 and applies community-wide.

Department standard operating procedures sit beneath it and may be stricter, never looser. If a department policy and this rulebook disagree, this rulebook wins; if this rulebook and the Charter disagree, the Charter wins.

Membership is a privilege earned through the whitelist and kept through conduct. Holding rank, in a department or in the community, means more accountability under these rules, not less.

Supreme governing document

Founding Charter

Founding Charter & Governance Structure

Preamble

One State Network was founded as the successor community to One State Roleplay, carrying forward the standards, culture, and lessons of a community that grew into one of the most recognized names in its space.

This Charter exists to ensure that One State Network is built on a foundation stronger than any single individual: a clear structure of shared leadership, defined responsibility, and accountable decision-making. This document establishes how the community is governed, who holds authority, how decisions are made, and how disputes are resolved.

It is the supreme governing document of One State Network. All community rules, department policies, staff guidelines, and standard operating procedures derive their authority from, and must remain consistent with, this Charter.

Name, Purpose & Identity

§1.1

Name

The community shall be known as One State Network, hereafter referred to as “OSN” or “the Community.”

§1.2

Purpose

OSN exists to operate a whitelisted, vMenu-based FiveM roleplay server that delivers serious, immersive, and high-quality roleplay. The Community is committed to maintaining a welcoming, mature environment where creativity, realism, and mutual respect define the player experience.

§1.3

Core Principles

  • Quality over quantity. Membership is a privilege earned through the whitelist process and maintained through conduct, not a right.
  • Fairness. Leadership decisions, rule changes, and disciplinary standards are applied consistently and transparently.
  • Accountability. Every member of leadership, from the Directors down, is accountable to this Charter and to the Community it serves.
  • Community first. The Community’s health always takes priority over any individual’s position, preference, or convenience.

Governance Structure

§2.1

Overview

One State Network is governed by two bodies working in concert: the Directorate, composed of the two Directors who serve as the executive leadership of the Community, and the Board of Directors, composed of the Directors together with each Head of Department. The Directorate holds final executive authority; the Board serves as the deliberative body relied upon for decisions that affect the Community as a whole.

§2.2

Hierarchy

  • The Directorate. The two Directors (100 and 101), equal partners in the ownership and executive leadership of the Community.
  • The Board of Directors. The Directors and all Heads of Department (HoDs), convened to deliberate and advise on community-wide matters.
  • Heads of Department. Leaders appointed to run individual departments, holding a seat on the Board by virtue of their office.
  • Staff & Membership. Staff members, department leadership beneath the HoD level, and the general whitelisted membership, governed under the policies established by the bodies above.
§2.3

Community Ranking Structure

All members of One State Network hold one of the following community ranks, listed in ascending order of authority. Community rank is not held separately from departmental rank; it is determined by a member’s rank within their department under the equivalency system established in Section 2.4.

  • Community Member. The foundation of the Community: whitelisted members in good standing. Community Members are entitled to participate fully in roleplay, community events, and community life under the rules of OSN.
  • Community Staff. The first tier of community leadership. Community Staff enforce the rules, moderate the server and Discord, handle reports and player issues, and serve as the primary point of contact between the membership and leadership.
  • Community Senior Staff. Experienced staff entrusted with elevated moderation authority. Senior Staff handle escalated issues, mentor and oversee Community Staff, and assist Administration with day-to-day staff operations.
  • Community Administration. The senior operational leadership of the staff team. Administration oversees the staff structure as a whole, manages staff recruitment and discipline, resolves escalations that exceed Senior Staff authority, and implements the policies set by the Board and the Directorate.
  • Board of Directors. The Directors and all Heads of Department, as established in Article IV. The Board deliberates on community-wide matters and carries the responsibilities set out in this Charter.
  • Community Directors. The two Directors (01 and 02), holding final executive authority over One State Network as established in Article III.
§2.4

Department Rank Equivalency

Departmental rank and community rank are one and the same ladder: a member’s rank within their department determines their community rank. Each department is free to structure, name, and order its own ranks in whatever manner suits its identity and operations, provided its rank structure contains the following allocation of community-rank slots:

  • One Head of Department, seated on the Board of Directors.
  • Two ranks equivalent to Community Administration.
  • Three ranks equivalent to Community Senior Staff.
  • Three ranks equivalent to Community Staff.
  • Three ranks equivalent to Community Member.

Each department shall publish its rank structure and the community-rank equivalency of each rank, subject to approval by the Directorate. For example, a department may designate its Captain rank as equivalent to Community Senior Staff; a member promoted to Captain thereby holds Community Senior Staff rank, with all of the authority and responsibility that rank carries.

Promotion or demotion within a department automatically carries the corresponding change in community rank. A member serving in more than one department holds the community rank of their primary departmental equivalent. The Directors hold the rank of Community Director at all times, irrespective of any departmental character or rank held under Section 3.7.

Because departmental promotion confers community authority, departments must apply their promotion standards with the understanding that they are appointing community leadership, not only departmental leadership. The Directorate may set community-wide prerequisites for promotion into ranks equivalent to Community Staff and above, and may veto or reverse any promotion that would place an unsuitable member in a position of community authority.

At every tier, higher rank carries greater responsibility and accountability, not exemption from the rules; every rank, including the Directors, is bound by this Charter and the rules of the Community.

§2.5

Primary Department Membership

Upon joining One State Network, every member is assigned to one primary department. A member’s primary department is their home within the Community: it holds their community rank under Section 2.4, and their membership in the Community is held through it. Members may additionally serve in other departments in a secondary capacity under policies set by the departments involved, but every member has exactly one primary department at all times.

A member may change their primary department only by transfer. A transfer requires the acceptance of the receiving department and is processed under policies set by the Directorate; membership remains continuous through an approved transfer, though the member’s rank in the receiving department, and therefore their community rank, is set by the receiving department.

Resignation from a member’s primary department without an approved transfer constitutes resignation from One State Network as a whole. The departing member relinquishes their whitelist status, community rank, and any positions held in secondary departments. A member who resigns in good standing may reapply to the Community through the normal whitelist process.

If a member is involuntarily removed from their primary department, they shall have seven days to secure a transfer to another department willing to accept them. If no transfer is completed within that window, their membership in the Community lapses. This provision does not limit the Community’s ability to remove a member outright for conduct warranting removal from One State Network itself.

The Directorate (100 & 101)

§3.1

Composition

The Directorate consists of exactly two Directors, designated 100 and 101. The designations 100 and 101 exist for identification and operational clarity only; they do not confer seniority, superiority, or any difference in authority. The Directors are 50/50 partners in the Community in all respects.

§3.2

Equal Partnership

Neither Director may act unilaterally on any matter reserved to the Directorate. Each Director holds an equal, undivided share of executive authority, and each is entitled to full visibility into all aspects of Community operations, finances, infrastructure, and administration at all times. No information relevant to the governance of OSN may be withheld by one Director from the other.

§3.3

Unanimity Rule

All decisions of the Directorate require the unanimous agreement of both Directors. If the Directors cannot reach agreement on a matter, the decision defaults to no: the proposal fails, the action is not taken, and the status quo remains in effect. There is no binding tiebreaker, no deferral to a third party, and no mechanism by which one Director may override the other. A deadlocked matter may be referred to the Board for non-binding counsel under Section 6.3, but the decision remains the Directors’ alone.

This rule is intentional. It ensures that every executive action taken in the name of One State Network carries the full confidence of both of its leaders, and it protects the Community from division at the top.

§3.4

Powers Reserved to the Directorate

The following matters may only be decided by unanimous agreement of both Directors:

  • Amendments to this Charter.
  • Appointment or removal of any Head of Department.
  • Creation, merger, or dissolution of any department.
  • Control of Community finances, including donations, expenditures, and any financial commitments.
  • Control of Community infrastructure and assets, including the server, Discord, domains, branding, social media accounts, and administrative credentials.
  • Community-wide rules and the global rulebook.
  • Permanent bans and their appeals at the final level.
  • Partnerships, affiliations, and public representation of the Community.
§3.5

Delegation

The Directors may jointly delegate operational authority to Heads of Department, staff teams, or individual members as they see fit. Delegated authority may be revised or withdrawn at any time by unanimous decision of the Directorate. Delegation of a task does not transfer ownership of the decision; final responsibility always rests with the Directorate.

§3.6

Vacancy & Succession

If a Director voluntarily steps down, becomes permanently unavailable, or is otherwise unable to serve, the remaining Director shall assume interim sole executive authority strictly to maintain continuity of operations. A replacement Director may only be seated by written agreement of the remaining Director and, where possible, the departing Director. Until a second Director is seated, matters listed in Section 3.4 that are non-urgent should be deferred, and the Board of Directors shall be consulted on any significant action.

§3.7

Director Participation In-Game

Each Director holds a standing right to create and operate in-game characters within any department of One State Network, at any time, at any rank of that department, up to and including command-level ranks. This right exists so the Directors may participate in, observe, and support roleplay across the Community without administrative barriers.

When operating within a department, a Director is expected to roleplay within that department’s standard operating procedures and to respect its internal chain of command in-character. A Director’s departmental character does not displace the Head of Department’s authority over the department’s roster, structure, or internal affairs; executive authority is exercised through the Directorate, not through an in-game rank.

§3.8

Directors and Department Leadership

The Directors shall not lead departments. No Director may hold a Head of Department position except on an interim basis, and only in the following two circumstances: to fill a vacancy in an existing department when its Head of Department position is unoccupied, or to establish and stand up a newly created department until a permanent Head of Department can be appointed.

When an interim vacancy arises, the Directors shall decide between themselves, by unanimous agreement, which of them will assume the vacant Head of Department position. Service as an interim Head of Department is temporary by definition: the Director serving in the role is expected to identify, develop, and appoint a permanent Head of Department, through the normal appointment process under Section 5.1, as promptly as the circumstances reasonably allow.

A Director serving as an interim Head of Department does not gain an additional seat or vote on the Board of Directors; they continue to sit on the Board solely in their capacity as Director. Interim service does not diminish a Director’s duties under this Charter, nor does it extend Directorate authority into the department beyond what this Charter already provides.

The Board of Directors

§4.1

Composition

The Board of Directors consists of the two Directors and every sitting Head of Department. Each Head of Department holds one seat on the Board by virtue of their office and vacates that seat upon leaving it.

§4.2

Role

The Board is the deliberative body of One State Network. The Directorate shall lean on the Board for decisions that affect the Community as a whole, including but not limited to: major rule changes, community events and initiatives, cross-department policy, whitelist standards, staff structure, and the general direction of the Community. The Board exists to ensure that community-wide decisions are informed by the leaders closest to the membership.

§4.3

Authority

The Board’s recommendations are advisory in nature and carry significant weight, but final authority on all matters reserved under Section 3.4 rests with the Directorate. On matters the Directorate expressly delegates to the Board, a majority vote of the Board shall decide, with each member, including each Director, holding one vote. In the event of a tie on a delegated matter, the motion fails.

§4.4

Meetings

The Board shall convene at a regular interval set by the Directorate, and no less than once per month while the Community is active. Either Director, or any two Board members acting jointly, may call a special session of the Board with reasonable notice. Minutes or a written summary of each Board session shall be recorded and retained.

§4.5

Conduct & Confidentiality

Board deliberations are confidential unless the Board or the Directorate releases them. Board members are expected to speak candidly in session and to support the final decision publicly once it is made, regardless of their personal position during deliberation. A Board member with a personal stake in a matter must declare the conflict and abstain from any vote on it.

§4.6

Vote of No Confidence

As a safeguard of last resort, the Board of Directors may remove a Director from the directorship by a vote of no confidence, subject to all of the following conditions:

  • Written cause. The motion must be filed in writing, state specific cause, and be signed by at least two Heads of Department.
  • Right of response. The Director who is the subject of the motion must be given the motion in full and a reasonable opportunity to respond to the Board before any vote is taken.
  • Unanimity of the HoDs. Only Heads of Department vote; neither Director votes on a motion of no confidence. The motion passes only if every sitting Head of Department votes in favor. A single abstention or opposing vote defeats it.
  • Protection of the Board. From the moment a motion is formally filed until it is resolved, no Head of Department may be removed, suspended, or replaced. Any attempt to alter the Board’s composition during a pending motion is void.
  • Cooldown. If a motion fails, no new motion of no confidence may be filed against the same Director for ninety days, absent new and materially different cause.

A successful vote of no confidence removes the Director from the directorship and all executive authority under this Charter. It does not, and cannot, divest that individual of any ownership interest in Community assets, finances, or infrastructure; the disposition of those interests must be resolved by agreement between the partners outside the scope of this Charter. Upon removal, the vacancy provisions of Section 3.6 apply.

Heads of Department

§5.1

Appointment

Heads of Department are appointed by unanimous decision of the Directorate. Each HoD serves at the pleasure of the Directorate and may be removed by unanimous decision of the Directorate at any time, with or without cause, though cause and documentation are expected as a matter of good governance.

§5.2

Responsibilities

Each Head of Department is responsible for the following within their department:

  • Day-to-day leadership, structure, and internal chain of command.
  • Department-level policies and standard operating procedures, consistent with this Charter and the global rulebook.
  • Recruitment, training, and internal discipline of department members, within Community-wide standards.
  • Representing the department’s interests and its members’ concerns on the Board of Directors.
  • Reporting the department’s status, needs, and issues to the Board and the Directorate.
§5.3

Limits of Authority

A Head of Department’s authority extends only to their own department. HoDs may not set community-wide policy, discipline members outside their department, commit Community funds or assets, or speak on behalf of One State Network as a whole unless expressly authorized by the Directorate.

§5.4

Departments

One State Network is organized into the departments enumerated in Appendix A of this Charter. Each department is led by a Head of Department holding a seat on the Board of Directors. Departments may be created, merged, renamed, or dissolved only by unanimous decision of the Directorate, and Appendix A shall be updated to reflect any such change.

Decision-Making Process

§6.1

Classes of Decisions

  • Directorate decisions. Matters listed in Section 3.4. Decided solely by the Directors, unanimously. Board input may be sought but is not binding.
  • Board matters. Community-wide matters brought before the Board under Section 4.2. The Board deliberates and recommends; the Directorate decides, or the Board votes where authority has been delegated.
  • Department decisions. Internal department matters under Section 5.2. Decided by the relevant Head of Department within the limits of this Charter.
§6.2

Default to No

Wherever this Charter requires unanimous agreement and that agreement is not reached, the answer is no. A failed proposal may be revised and brought back at a later time, but no action shall be taken, and no policy shall change, on the strength of a divided Directorate.

§6.3

Advisory Referral on Deadlock

When the Directors are deadlocked on a matter, either Director may refer the question to the Board of Directors for an advisory vote. Upon referral, the Board shall hear the matter, with each Director presenting their position, and shall vote by simple majority of the Heads of Department; the Directors do not vote on an advisory referral.

The Board’s advisory vote is non-binding. Its purpose is to inform the Directors of the judgment of the Community’s department leadership, not to decide the question. Following the advisory vote, the Directors shall reconsider the matter in light of the Board’s counsel. If the Directors still cannot reach unanimous agreement, the decision defaults to no in accordance with Section 6.2. Nothing in this section creates any obligation for either Director to conform to the Board’s recommendation.

§6.4

Emergencies

In a genuine emergency threatening the security, integrity, or safety of the Community, such as a compromised account, an active exploit, or serious member misconduct in progress, any Director may take immediate protective action alone. Such action must be reported to the other Director as soon as possible, and any lasting policy arising from the emergency must then be ratified through the normal unanimous process. Emergency authority is protective only; it may not be used to make permanent decisions unilaterally.

Amendments & Ratification

§7.1

Amendments

This Charter may be amended only by the unanimous written agreement of both Directors. The Board of Directors shall be given the opportunity to review and comment on any proposed amendment before it is adopted, except in cases of minor clerical corrections. All amendments shall be dated and recorded in an amendment log appended to this document.

§7.2

Supremacy

In any conflict between this Charter and any other Community document, rule, policy, or practice, this Charter prevails.

§7.3

Ratification

This Charter takes effect upon the signature of both Directors and remains in effect until amended or dissolved by their unanimous agreement.

Departments of One State Network

The following departments are established under Section 5.4 of this Charter. Each is led by a Head of Department who holds a seat on the Board of Directors.

  • SASP
    San Andreas State Police

    The state-level law enforcement agency of One State Network, responsible for statewide patrol, highway enforcement, and state-jurisdiction investigations and operations.

  • LSPD
    Los Santos Police Department

    The municipal law enforcement agency serving the city of Los Santos, responsible for city patrol, crime response, and community policing within city limits.

  • BCSO
    Blaine County Sheriff’s Office

    The county law enforcement agency serving Blaine County, responsible for county patrol, rural operations, and law enforcement services throughout the county’s communities.

  • SAFC
    San Andreas Fire Command

    The fire and emergency medical services agency of One State Network, responsible for fire suppression, rescue operations, and emergency medical response across the state.

  • SAECC
    San Andreas Emergency Communications Center

    The emergency dispatch agency of One State Network, responsible for call-taking and dispatch operations across all emergency services, coordinating law enforcement, fire, and EMS response, and maintaining the standards and training of the Community’s communications personnel.

  • CivOps
    Civilian Operations

    The department responsible for the civilian side of roleplay, including civilian character standards, businesses, criminal roleplay oversight, events, and the overall quality of non-emergency-services roleplay.

  • SADA
    San Andreas Development Authority

    The development and infrastructure department of One State Network, responsible for building, maintaining, and securing the Community’s technical foundation, including the game server, resources and scripts, Discord and bots, websites, and related systems. SADA operates out-of-character; its members are recognized as a department of the Community with a Head of Department seated on the Board.

This Charter takes effect upon the signature of both Directors and remains in effect until amended or dissolved by their unanimous agreement.

Director 100Director 101

Issued under Charter §3.4 · Rev. 1.1 · September 2026

Community Policies

The global rulebook of One State Network. It applies to every member, every rank and every department, in the city and on Discord. Read it once, properly. “I didn’t know” isn’t a defence.

General conduct

How we treat each other, in and out of character.

  1. 1.1

    Respect everyone out of character.

    Your character can be a villain; you cannot. Harassment, hate speech, slurs, discrimination and targeted toxicity are never “just RP” and are removed on sight.

  2. 1.2

    Be 18 or older.

    One State is an adult community running mature, serious storylines. Accounts found to belong to anyone under 18 are removed until they are of age.

  3. 1.3

    One person, one whitelist.

    Sharing accounts, alt accounts to dodge punishments, or impersonating staff, department command or other members is a permanent removal.

  4. 1.4

    No cheats, mods or exploits.

    Menus beyond the server-provided vMenu, macros, crosshair overlays, altered game files, and any bug that gives you an advantage. Report the bug to staff; don’t use it.

  5. 1.5

    Use vMenu responsibly.

    Spawn only what your character would realistically have, in the department and rank you hold. Spawning restricted vehicles, weapons or peds you’re not cleared for is treated as an exploit.

  6. 1.6

    Use the in-city voice.

    A working microphone is required. Voice changers are fine when they fit a character; soundboards and music through your mic are not.

  7. 1.7

    Keep drama out of the city.

    Disagreements are handled through a ticket to Community Staff, not in-game, not in a public channel, and not on someone else’s stream.

  8. 1.8

    Staff decisions are final in the moment.

    Comply first, then appeal through the ladder in Section 9 if you disagree. Arguing with staff mid-scene ends the scene.

Roleplay standards: RDM, VDM & FailRP

Every action needs a reason your character would have.

  1. 2.1

    RDM (Random Deathmatch).

    Killing or attacking another player without meaningful roleplay leading up to it. “He looked at me funny” isn’t initiation. Give people a chance to respond before shots are fired.

  2. 2.2

    VDM (Vehicle Deathmatch).

    Using a vehicle as a weapon, ramming people or cars, without a roleplay reason. Accidental collisions happen; a second pass doesn’t.

  3. 2.3

    FailRP.

    Acting in a way no real person would in your situation: breaking character in voice, ignoring injuries, talking while downed, refusing to react to a gun in your face.

  4. 2.4

    Value your life.

    If you’re outnumbered or outgunned, your character fears death. Fear RP applies whenever a weapon is drawn on you at close range.

  5. 2.5

    Stay in character.

    Out-of-character talk belongs in /ooc or a ticket. Use “in my head” phrasing only when a mechanic genuinely breaks, never to negotiate a scene.

  6. 2.6

    No combat logging.

    Leaving during an active scene, arrest, pursuit or while downed is treated as an admission. Crashes happen: rejoin and return to the scene promptly, and tell staff if you can’t.

  7. 2.7

    Some stories are off the table.

    Sexual assault, torture for its own sake, real-world tragedies and suicide are not roleplayed here. Any extreme scene requires the consent of every player in it, and staff may still stop it.

New Life Rule

Death has consequences. Respawning is one of them.

  1. 3.1

    When you respawn, the scene is over for you.

    Your character forgets who downed them, why, and where. You may not return to the location or seek revenge.

  2. 3.2

    If SAFC treats you on scene, you remember.

    Being revived keeps the storyline alive; you may continue the story, but you’re injured and should act like it.

  3. 3.3

    Fifteen-minute rule.

    After respawning you may not return to the area of your death or re-engage the same players for 15 minutes.

  4. 3.4

    No NLR abuse.

    Respawning to escape an arrest, a hostage situation or a debt-collection scene is combat logging by another name.

Metagaming & powergaming

Your character only knows what your character has learned.

  1. 4.1

    Metagaming.

    Using information from outside the game, such as Discord, streams, third-party voice or a friend’s screen, inside it. Watching a stream to find someone is an immediate removal.

  2. 4.2

    No third-party voice during play.

    If you’re in the city, your only comms are in-city: phone, radio and proximity. Discord calls with players you’re roleplaying near are metagaming. Department radio channels run by SAECC are the exception, used in character.

  3. 4.3

    Character knowledge stays separate.

    Your second character doesn’t know what your first character knows, and never shares assets, money or grudges with them.

  4. 4.4

    Powergaming.

    Forcing an outcome on another player without giving them a fair chance to respond: “I knock you out instantly”, unrealistic stunts, abusing mechanics, vMenu spawns or game physics mid-scene.

  5. 4.5

    Realistic limits.

    You can’t carry six rifles, survive a 200 ft fall or sprint away from a wreck. Roleplay your injuries and equipment realistically.

  6. 4.6

    No stream sniping.

    Locating or targeting a player because you know they’re live is metagaming and harassment combined.

Combat & firearms

Guns are a storytelling tool, not the story.

  1. 5.1

    Initiate clearly.

    Before hostilities, make your intent obvious in a way the other player can hear and react to. A demand, a threat, a drawn weapon, not a silent shot from a rooftop.

  2. 5.2

    No shooting from vehicles at speed.

    Drive-by fire is permitted only from a stationary or slow-rolling vehicle, with realistic accuracy expected.

  3. 5.3

    Safe zones.

    No crime, weapons or hostile actions at hospitals, fire stations, police and sheriff stations or the courthouse, unless law enforcement pursues you there.

  4. 5.4

    Heavy weapons need a story.

    Explosives, LMGs and military hardware are restricted. Spawning or using them without a CivOps-approved storyline is a removal.

  5. 5.5

    Downed players stay down.

    No talking while downed, no crawling to cover, no calling friends. When you’re up, roleplay the injury.

  6. 5.6

    Hostage rules.

    One hostage per scene, never a friend or a fellow gang member, and never as a shield for a shootout. Demands must be reasonable; law enforcement must be given real room to negotiate.

Vehicles & driving

Drive like the car is real and you’re inside it.

  1. 6.1

    Realistic driving.

    No ramping off hills, driving up mountains in sports cars, or treating a wreck as a speed bump. A serious crash means you stop and roleplay it. AI traffic sometimes does things no real driver would, pulling out in front of you or stopping dead on a highway. Use common sense about when an AI-caused accident can be disregarded. Never disregard an accident in view of other players; wait for them to leave the immediate area first.

  2. 6.2

    Spawn appropriately.

    Civilians spawn civilian vehicles; emergency vehicles, liveries and equipment belong to the department and rank that’s cleared for them. No supercars in a pursuit without a storyline that earned one.

  3. 6.3

    Pursuits.

    Fleeing law enforcement is fine; fleeing forever is not. Give the pursuit an end, a bail-out, a hide, a stop, within a reasonable time. Swapping or respawning vehicles mid-pursuit is powergaming.

  4. 6.4

    Aircraft.

    All flight, civilian and departmental, is governed by the One State Network Aviation Operations Manual below. Read it before you leave the ground; it applies alongside this rulebook.

  5. 6.5

    Emergency vehicles are not toys.

    Stealing a marked unit is a serious crime with serious in-character consequences, and impersonating a department member out of character is a removal.

Streaming & content

You’re welcome to broadcast One State. Represent it well.

  1. 7.1

    You may stream and record.

    No permission needed. A short stream delay is recommended, especially if you’re in a department or an active criminal storyline.

  2. 7.2

    Your stream is still in the city.

    Every rule applies on air. Talking to your chat is fine, but not while you’re in a scene and audible in-game; breaking character on the in-city voice to address chat is FailRP. Reading chat to learn what’s happening in the city is metagaming.

  3. 7.3

    Don’t broadcast reports or staff scenes.

    Tickets, staff conversations and evidence are confidential. Clip them for a report; don’t publish them.

  4. 7.4

    Viewers aren’t your crew.

    Instructing viewers to join and back you up, or to report someone, is metagaming and brigading. Both are removals.

  5. 7.5

    Clips as evidence.

    Reports involving another player should include a clip. Recording software is strongly recommended for everyone, and mandatory for Community Staff and department command.

  6. 7.6

    Branding.

    You may use the One State Network name and logo in your content. You may not claim to speak for the Community; public representation is reserved to the Directorate.

Discord

The Discord is part of the Community. So are its rules.

  1. 8.1

    Same standards as the city.

    Section 1 applies in full. What gets you removed in-game gets you removed on Discord, and the other way round.

  2. 8.2

    Use the right channel.

    Reports and appeals go through tickets. Department business stays in department channels. Keep general chat general.

  3. 8.3

    No leaks.

    Department channels, Board business and staff channels are confidential. Screenshotting them elsewhere is a removal.

  4. 8.4

    No advertising or poaching.

    Promoting other servers, or recruiting OSN members for them, is a permanent removal.

  5. 8.5

    Display names.

    Use a recognisable name and the tag format your department sets. Impersonating another member or a rank you don’t hold is a removal.

  6. 8.6

    Leaving the Discord is leaving the Community.

    Your whitelist and department membership are held through it.

Punishments & appeals

Consistent, documented, and appealable, as the Charter requires.

  1. 9.1

    Staff use judgement.

    The tiers below are a guide. Intent, history and honesty all count. Owning a mistake in a ticket goes a long way; lying in one doubles the outcome.

  2. 9.2

    Every action is logged.

    Warnings, kicks and bans are recorded with the rule, the evidence and the staff member. You may request a copy of your own record.

  3. 9.3

    Department discipline is separate.

    Your Head of Department may discipline you within your department under its SOPs. Community-level punishments are issued only by Community Staff and above.

  4. 9.4

    Removal and your department.

    If you’re removed from your primary department, you have 7 days to secure a transfer to another department willing to accept you. If none is completed, your membership lapses (Charter §2.5).

TierTypical offencesTypical outcome
Tier 1MinorFailRP, breaking character, minor VDM, unrealistic driving, wrong channel on DiscordVerbal warning → written warning → 24 h ban
Tier 2SeriousRDM, VDM, NLR breach, combat logging, powergaming, safe-zone breach, unapproved restricted spawns, disrespecting staff3-day ban → 7-day ban → 30-day ban
Tier 3SevereMetagaming, stream sniping, harassment or hate speech, leaking confidential channels, ban evasion, impersonation30-day ban → permanent removal
Tier 4Zero toleranceCheats or exploits, advertising or poaching, doxxing or real-world threats, brigading, under-age accountsImmediate permanent removal

Appeals ladder

  1. 1
    Community StaffWarnings and bans up to 24 h. Open a ticket within 7 days with your clip.
  2. 2
    Senior StaffBans of 3 to 30 days, and any appeal of a Tier 1 decision.
  3. 3
    AdministrationEscalations, disputes about staff conduct, and 30-day bans.
  4. 4
    The DirectoratePermanent removals, decided unanimously by both Directors (Charter §3.4). Final.

Appeals are reviewed by someone other than the staff member who issued the punishment. Permanent removals may be appealed once, after 90 days. A rejected appeal at the Directorate level is final.

These policies are issued by the Directorate of One State Network under §3.4 of the Founding Charter and may be amended only by unanimous decision of both Directors. They take effect on publication. The Directorate may take immediate protective action in an emergency under Charter §6.4.

Director 100Director 101

Activity, leave, transfers & resignation

Staying active, time away, a new department, or leaving.

  1. 10.1

    Play at least one hour a week.

    Every member is expected to spend at least one hour a week on the server. This isn’t actively monitored, and nobody will chase you over a quiet week. It’s the standard your department’s command will hold you to if your inactivity becomes an issue, and it may then be handled as department discipline (9.3). Repeated inactivity can lead to removal from your department, with the usual 7 days to secure a transfer (9.4). If you know you’ll be away, request leave (10.2) and the time won’t count against you.

  2. 10.2

    Ask for leave on the website.

    Leave is requested from your profile, in whole days, between 3 and 30 days per request. You may start it up to 7 days back if life got there first, and up to 30 days ahead.

  3. 10.3

    Short leave needs no approval.

    Leave of 7 days or less is recorded as soon as you ask, and your command staff are told. Longer leave waits for your department’s command: its head, its command staff, or a rank the head has trusted with requests. A Head of Department’s own leave goes to the Directors.

  4. 10.4

    Leave ends on its own.

    You get a reminder two days before your leave ends and are back on duty the day after it. Come back early from your profile any time. If you’re still away a week after it ends with no time on the server, your head is told so they can check in. Nothing happens automatically.

  5. 10.5

    On leave, you can still play.

    Being on leave does not lock you out of the server unless the Directorate turns that on. It keeps you off the inactivity list, and your 30 days of activity start again when your leave ends.

  6. 10.6

    Transfers are the receiving department’s call.

    Ask to transfer from your profile. The department you want to join decides and sets your new rank; the department you leave is told but has no veto (Charter §2.5). Your membership stays continuous.

  7. 10.7

    Resigning ends your membership.

    Resigning from your primary department without a transfer is resigning from One State Network. Your departments, rank and callsigns are released and your Discord rank roles are removed. You may reapply through the whitelist application. A Head of Department hands over first; Directors resign through the Directorate.

Annex · Official server guidance

Aviation Operations Manual

Flight paths · Pilot operations · Airspace safety

Version 1.0Effective 19 September 2026Approved by OSN Admin

This manual establishes the standard aviation operating procedures for One State Network. The purpose of these rules is to organize aircraft traffic, reduce unnecessary conflicts, and provide pilots with simple and consistent expectations while operating within the server.

One State Network does not utilize Air Traffic Control (ATC). Pilots are therefore responsible for maintaining separation from other aircraft, following designated flight paths, monitoring aviation communications, and using sound judgment during flight.

A1

General flight rules

  • Pilots are responsible for operating their aircraft safely.
  • Pilots must maintain control of their aircraft at all times.
  • Do not intentionally fly into buildings, vehicles, crowds, or other players.
  • Avoid unnecessary low-altitude flying over populated areas.
  • Use designated flight paths when practical.
  • Pilots should monitor the appropriate aviation radio channel while operating near busy airports or flight corridors.
A2

Airport operations

  • Use the designated runway when taking off or landing.
  • Takeoffs and landings should generally be made in the same direction as other aircraft using the airport.
  • Give way to aircraft already on the runway or established on final approach.
  • Do not take off when another aircraft is landing or occupying the runway.
  • Aircraft should announce their intentions over the appropriate aviation radio channel when operating at busy airports.
  • Pilots should check the runway and surrounding area before entering or departing the airport.
A3

Designated flight paths

One State Network will establish recommended flight paths to help organize aircraft traffic and reduce the chance of aircraft conflicts. These routes are recommended unless a specific restriction or emergency situation requires otherwise.

Recommended VFR routes
RoutePathRecommended altitudePrimary use
VFR-01 Northern RouteSandy Shores → Grapeseed → Paleto Bay1,500–2,000 ftNorthern travel
VFR-02 Western RouteLos Santos → Chumash → Paleto Bay2,000 ftWestern and coastal travel
VFR-03 Eastern RouteLos Santos → Harmony → Sandy Shores → Grapeseed1,500–2,000 ftEastern travel
VFR-04 Coastal RouteLos Santos → Vespucci → Chumash → Paleto Bay1,000–1,500 ftCoastal travel
A4

Helicopter operations

  • Helicopters may operate at lower altitudes when necessary.
  • Avoid unnecessary hovering over populated areas.
  • Do not intentionally fly directly over active roadways at extremely low altitude.
  • Emergency helicopters may deviate from designated routes when responding to calls.
  • Police, EMS, Fire, and Search & Rescue helicopters may land outside airports when reasonably necessary.
  • Helicopter pilots should use additional caution around fixed-wing aircraft and airport traffic.
A5

Recommended altitudes

The following altitudes are recommended operating guidelines. They are not intended to restrict reasonable emergency operations or require an aircraft to fly unsafely.

Recommended operating altitudes
OperationRecommended altitude
Airport traffic1,000 ft
Local helicopter operations500–1,500 ft
City-to-city flight1,500–2,500 ft
Long-distance flight2,000–3,500 ft
Emergency operationsAs necessary
A6

Right-of-way

  • Aircraft approaching an airport have priority over aircraft preparing to depart.
  • Aircraft already on the runway have priority over aircraft attempting to enter it.
  • When two aircraft are approaching each other, both pilots should alter course as necessary to avoid a collision.
  • Aircraft being overtaken should maintain their course while the overtaking aircraft passes safely.
  • Give way to emergency aircraft displaying emergency lights or otherwise indicating an active emergency response.
  • When in doubt, the pilot should take the safest available action to avoid a collision.
A7

Restricted airspace

Certain locations may be designated as restricted or no-fly zones. Examples include:

  • Military installations
  • Prison facilities
  • Government facilities
  • Active crime scenes
  • Major public events
  • Temporary emergency areas

Aircraft may not enter designated restricted areas unless specifically authorized by One State Network staff or the appropriate department.

A8

Temporary no-fly zones

One State Network staff may establish temporary no-fly zones during major incidents or special events.

  • Active police operations
  • Aircraft crashes
  • Large fires
  • Major events
  • Search and rescue operations
  • VIP movements

Temporary restrictions should be announced through the appropriate server communication channels and remain active until they are officially lifted.

A9

Emergency flight operations

Emergency aircraft may deviate from normal flight paths when reasonably necessary.

  • Police, EMS, Fire, and Search & Rescue aircraft may leave designated flight paths.
  • Emergency aircraft may operate at lower altitudes when necessary.
  • Emergency aircraft may land in non-airport locations when reasonably necessary.
  • Emergency aircraft may enter restricted areas when authorized.
  • Emergency pilots should use aviation radio communications whenever practical.
  • Safety remains the priority during all emergency operations.
A10

Pilot responsibility

There is no ATC in One State Network. Pilots are responsible for maintaining separation from other aircraft, following designated flight paths, monitoring aviation communications, and using good judgment while operating their aircraft.

Failure to follow these guidelines may result in administrative action when a pilot’s conduct creates unnecessary risk, disrupts other players, or violates server rules.

Read it? Good.

Now pick your path.

Sign in with Discord, choose a department, and submit your whitelist application. Staff review every one by hand.

Apply to join