Article 1: Roles and Responsibilities

• Section 1: Upper Management

  ---

  Upper Management have full authority over their departments, but only their departments. They must contact the CEO regarding reports on Advisors and above from separate departments, and supervisors from separate departments if they wish to raise concerns. Directors are the last CoC and primarily focus on management & development, not administration.

  • Section 1A: President (“EXEC”)

    ---

    - The President is the leading man in charge of all operations. - Held by the owner of the Community.
  • Section 1B: Chief Executive Officer (“C.E.O”)

    ---

    - The Chief Executive Officer (“CEO”) is responsible for leading the execution of Definitive Network's long term strategy. - This position oversees all development of Definitive Networks. - This position is responsible for appointing Director positions, and leading the Board of Directors. - This position is responsible for appointing Supervisor positions. - This position is the last line of defence for unsettled disputes among departments. - This position has all authority to promote and demote without any reconsideration. - This position oversees all departments and their progress. - This position is responsible for approving of Advisor promotions and demotions.
  • Section 1C: Director of Infrastructure (“D.O.I”)

    ---

    - Oversees all Infrastructure of Definitive Networks (Website, Forums, Discord, Trello, Steam Group, etc.). - This position has a global rank on all servers. (Super Admin) - This position is granted development access to the website, Teamspeak, Steam Group, and other unmentionables. - This position is focused on management, development, maintenance, and delegation of moderation within all of the above. - This position oversees the Discord & Forum Moderation Teams, monitoring their internal activity. - This position may also assist in server development, and any tasks/projects assigned by the CEO. - This position is the Head Chief of Development if needed. - This position is assigned by the CEO & Board of Directors, and reports directly to the CEO.
  • Section 1D: Director of Personnel (“D.O.P”)

    ---

    - This position has a global rank on all servers. (Server Admin) - This position is tasked with the selection of Server Managers, Head Admins, and oversight of our in-game staff teams. - This position may promote and demote any staff below or equal to Server Manager. - This position can block a promotion given out by Head Administrators or Server Managers; if deemed necessary. - This position deals with the Human Relations with the Staff and all employees that are improved. - This position helps with the application process for server recruitment. - This position deals with the evaluation of Staff. - This position also enforces the initiative of staff involvement. - This position deals with staff policies and practices. - This position develops goals and functions to carry out through server management. - This position enforcement of the staff evaluation system. - This position is assigned by the CEO & Board of Directors, and reports directly to the CEO.
  • Section 1E: Director of Affairs (“D.O.A”)

    ---

    - Oversees all Affairs Departments of Definitive Networks. - This position has a global rank on all servers. (Super Admin) - This position deals with the Human Resources aspect of server innovation which involves the public. - This position also deals with server suggestions and determines if the suggestion is beneficial to the community. - This position is to advise community meetings and to make notes of all issues regarding the server. - This position needs to be active on the forums and to make feedback on server suggestions. - This position is to maintain relationships with different communities. - This position works with the CEO to advise a strategy regarding the server innovation and gives the CEO feedback. - This position deals with all Public Affairs, - This position may promote and demote any Affairs Department members. - This position is assigned by the CEO & Board of Directors, and reports directly to the CEO.
• Section 2: General Management

  ---

  Supervisors should only focus on their designated departments and must contact the proper supervisor of a separate department regarding concerns instead of dealing with it themselves.

  • Section 2A: Infrastructure Supervisor (“I.S”)

    ---

    - Infrastructure Supervisors assist the D.O.I in managing Definitive Network's infrastructure. - This position has a global rank on all servers. (Super Admin) - This position is responsible for overseeing the Definitive Support Team. - This position is granted extended Forum & Discord permissions. - This position's permissions are directly delegated by the D.O.I on a level of trust basis. - This position reports directly to the D.O.I.
  • Section 2B: Personnel Supervisor (“P.S”)

    ---

    - Personnel Supervisors oversee all server staff teams. - This position has a global rank on all servers. (Super Admin) - This position may authorize promotions and demotions of Head Administrators and below. - This position deals with all Staff Evaluations ordered by the D.O.P. - This person is the second to the Staff Human Resources. - This position deals with the training of Head Administrators and Server Managers. - This position makes sure that all staff roles are promoted throughout the server. - This position's goal is to enforce the regulations and the policies ordered by the D.O.P. - This position reports directly to the D.O.P.
  • Section 2C: Affairs Supervisor (“A.S”)

    ---

    - Affairs Supervisors assist the Director of Affairs with department management. - This position has a global rank on all servers. (Super Admin) - This position supervises and make sure that all community standards and policies are enforced. - This position reports directly to the D.O.A. - This position tries to meet mediums of public concerns. - This position is tasked with looking over the server suggestions and giving feedback. - This position is required to be active on the Forums. - This position follows what the D.O.A tell them to do and harnesses some power of the D.O.A when granted.
  • Section 2D: Advisor

    ---

    - Advisors are to assist the Lower Management and General Management. - This position has a global rank (admin) on all servers. - Who they report to is subjective, and based on the situation, but depending on the situation will speak with a supervisor, and that supervisor will speak with their director if needed.
• Section 3: Lower Management

  ---

  The Lower Management are the Server Managers or Head Administrators of their specific server. They are to focus on their server and its staff.

  • Section 3A: Server Manager (“S.M”)

    ---

    - Server Managers are responsible for overseeing one particular server and their staff team. - This position has the ability to update and/or change server rules. Any major rules must be consulted with the Affairs Department. - This Position has the ability to promote and demote Server Staff Members. - This Position must inform the D.O.P about all promotions given beforehand. - This Position must consult the P.S or the D.O.P with any major staff rules. - This position reports directly to the Personnel Supervisor. - Responsible for the recruitment of Staff. - Holds Weekly staff meetings to ensure server success and informs the P.S or D.O.P about the meeting. - Promoted by the D.O.P and must be recognized by the Board of Directors. - This Position must ensure high quality for themselves and all staff members under them. - This Position must try to enforce a positive work environment. - This Position must try to be professional at all times. - This Position tries to ensure happiness with the public.
  • Section 3B: Head Administrator (“H.A”)

    ---

    - Head Administrators are to watch over the entire staff team on their designated server. - This position may suggest updates to the server rules to their Server Manager. - This Position has the ability to promote and demote Server Staff Members. - This Position must inform the D.O.P about all promotions given beforehand. - This position reports to the Server Manager.
  • Section 3C: Head Developer (“H.D”)

    ---

    - This position can only be held by one person. - This position gets the Developer rank on all servers and can assign himself ranks for testing purposes and must consult with the S.M+ before switching to Super Admin. - They must work with server staff. - C.E.O and vote on Board of Directors can only appoint this position. - Chief of the Development department. - Anything that this position needs must be brought up first by the D.O.I, C.E.O, or President.
  • Section 3D: Developer

    ---

    - Hired by the C.E.O and Head Developer. - Must have knowledge of coding. - Receives orders from the Head Developer.
• Section 4: Server Staff

  ---

  The Server Staff team are tasked with being the active enforcers of in-server rules.

  • Section 4A: Senior Administrator (“S.A”)

    ---

    - Senior Administrators are to enforce server rules on the players. - First line of defence when it comes to solving Staff vs. Staff situations and Player vs. Staff situations. - Can do events if approved by the Head Gamemaster. - Senior Administrators are tasked with giving their input and opinions on staff applications. - This position reports to the Head Administrator.
  • Section 4B: Gamemaster/Trial Gamemaster (“GM / T.GM”)

    ---

    - Does events approved by Head Administrator+. - Tries to make the server enjoyable by fun events. - Has no staff influence but has all authority to do events.
  • Section 4C: Administrator

    ---

    - Administrators are to enforce server rules on the players. - Administrators are tasked with giving their input and opinions on staff applications. - This position reports to the Head Administrator.
  • Section 4D: Moderator

    ---

    - Moderators are to enforce server rules on the players. - Promoted from Trial Moderator when the Senior Admin that was training them thinks they are ready for staff. - First Responders for Staff Calls. - This position reports to the Head Administrator.
  • Section 4E: Operator

    ---

    - Trial-Moderators are newly accepted staff members who must be trained and mentored by a Staff Trainer for a total time of five hours. Once the Staff Trainer has completed this and feel confident in the Trial-Moderator. - Cannot Perma Ban. - Trains with the Senior Administrator assigned to them. - This position reports to the Staff Trainer and the Head Administrator.

Article 2: Schedules and Timetables

• Section 1: Meetings

  ---

  This includes the weekly schedules for Upper Management, General Management, and Lower Management.

  • Section 1A: Management Meetings

    ---

    Every Saturday @ 11:00 AM PST / 12:00 PM CST / 1:00 PM EST / 6:00 PM GMT / 7:00 PM CET
  • Section 1B: Staff Meetings

    ---

    Every Other Saturday @ 11:30 AM PST / 12:30 PM CST / 1:30 PM EST / 6:30 PM GMT / 7:30 PM CET
  • Section 1C: Community Meetings

    ---

    First Saturday of Every Month @ 10:00 AM PST / 11:00 AM CST / 12:00 PM EST / 5:00 PM GMT / 6:00 PM CET

• A. General Rules

  ---

  Rule A1. Self-defense is always a justifiable reason to kill or attack. Rule A2. FailRP is defined as exhibiting behaviors that break roleplay. (such as bunny-hopping, disrupting the gameplay of others, having an invalid name.) This is Determined by Staff.      Avoiding or breaking role play in any manner is not allowed in IC      Bhopping is to be categorized under FailRP and is thus not allowed      Firing upon someone during a /me and /roll scenario constitutes FailRP      Intentionally disrupting or ruining server events Powergaming and Metagaming are separately defined from FailRP. (Powergame is giving yourself an advantage over players and excluding yourself from certain processes and normal role-play standards - Metagame is taking info from OOC sources into IC.) Specific Examples of Metagame:     Using the voice, profile picture, or steam profile of an SU to determine they are an SU Specific Examples of Powergame:     Using your own combine character as a disguise     Killing someone before they can roll against you Tip: Using video evidence to catch out blatant metagamers is more often than not the best chance you have. Whilst it is tedious, it has more benefits than drawbacks. Rolling (/roll) is used as a means to determine the outcome of an RP action (a /me) that directly involves or affects other players in any manner. All RP actions taken that directly involve another player must be rolled against by the player it involves. RP actions that do not directly involve another player will be rolled against by staff members, which you must call for. All kinds of RP actions are allowed, except:     Actions explicitly stated to only be available to certain jobs/classes (E.g. hijacking, infiltrating, building, scouting, handcuffing).     Actions not based in the realm of practicality (E.g. pulling a C4 explosive out from your pocket when you obviously had no way of acquiring it).     Actions that cannot be counteracted by other players in a realistic manner.     RP actions that serve the same purpose as one that has already been attempted towards a specific player in a single life (E.g. Trying to escape from a player a second time after already failing to escape them.) Rule A3. No Random Deathmatch (RDM). RDM is defined as the unwarranted killing of other players (typically non-combatants or teammates).     Spawn-killing and base-killing are bundled together for the sake of simplicity.     Team-killing also qualifies as RDM and carries harsher punishments.     Team-killing may only be allowed in the context of training or tryouts. Rule A4. You may only hold one character in each faction. VIPs can have two. Jobs that don’t take a character slot are exempt. You may only hold a rank of CO+ on one faction at a time, and for only one character, regardless of VIP status. Each player is allowed to have one honorary character no matter the faction. Rule A5. Spawn-camping is prohibited. The definition of “spawncamp” has been defined as follows:     Preventing the passage of enemy units through their spawn/base border exits by any means, combat or otherwise.     Maintaining active weapon sightlines to the enemy spawn/base exits with the intent to fire upon them the moment they exit their protected areas.     Showing intent of any kind to prevent a competitive engagement over capture points within a reasonable distance of an enemy’s base. Note: Players are HIGHLY encouraged to screenshot anything they believe to be spawn camping and send the evidence to the unit's COs as soon as possible. Visual Representation: Rule A6. Toxicity is defined as disingenuous behavior that serves to antagonize, harass, or stir hatred about an individual in a coordinated manner beyond simple criticism. This kind of behavior is not tolerated in any way, shape, or form whether it be in an OOC or IC nature. Any behavior of this manner may be handled by either the offenders COs, or if the issue is severe enough, handled by Management. Rule A7. Server Raids are prohibited. This is defined as a group of players banding together to defy staff ruling or to interrupt regular server activity en masse. This will result in a 1 month ban of all players involved. Rule A8. Exploitation: The use of an unintended and unaddressed game mechanic or map feature, typically a bug, that would result in an unfair advantage over other players. Abusing an exploit for any reason is punishable, the more serious the exploit, the harsher the punishment. A basic example includes: Any attempt to climb on or out of the map boundaries Rule A9. Leave to Avoid RP (LTARP) is defined as using OOC means to escape/avoid an IC Scenario. Rule A10. Areas designated for events are not allowed to be tampered with in any way or form. Rule A11. Certain events or circumstances may alter or denounce MOTD rules in order to suit the map’s or event’s needs. These exceptions will be addressed by Management or Gamemasters if and when this occurs. Certain events may be labelled as ‘mandatory’ events by Gamemasters (requires Head Gamemaster supervision). Participation in these events is not optional, and intentionally defying or disrupting them is considered an obstruction of server staff. Rule A12. ERP (Erotic Roleplay) is strictly forbidden, this includes sexual harassment. Rule A13. When a player is kidnapped or imprisoned, that player may not be held for more than 10 minutes, however can be extended if the prisoner provides consent. The imprisonment timer starts as soon as the captured player is taken into their captor's base. This also applies to Stalkers/slaves, starting immediately after enslavement/transformation and can be extended if given consent. Rule A14. You may not kill anyone with props from the gravity gun. Rule A15. Neither faction may question/interrogate their captive after their enslavement/transformation. Rule A16. Staff member/officer authorization must be requested and accepted in-game. No other platform of communication is valid for these kinds of requests. Rule A17. Players are only able to spy on their own faction if convinced/forced to through roleplay. They cannot start spying for the enemy team unless they were captured beforehand. Being a spy only lasts for 1 life; and influences of the enemy faction are wiped from you upon death.

  ---

  If what you’re doing or are about to do isn’t listed here and you’re curious, ask a staff member. If one is not available, use common sense. For rules and explanations on specific situations refer to the main discord in #rules-erratum. If you do not see what you are looking for, contact an Head Admin+.
• B. Base Raid Rules

  ---

  Rule B1. Vehicles can not be deployed for either side at all to attack or defend during a base raid. However they can be used to transport troops as long as they (vehicles) do not cross base borders. Rule B2. Cooldown between base raids is 30 minutes. Cooldown is not universal for both factions. Rule B3. One life per raid. If you die during the raiding of an opposition base, you are not allowed to return and continue aiding in the base raid. Rule B4. You need at least 10 members in the raiding squad, CO and Admin+ permission, as well as a valid reason for you to begin raiding. Rule B5. Base raids cannot be exclusive to one division. Rule B6. Factions in DB or mid-tryouts cannot be base raided.
• C. Infiltration and Scouting Rules

  ---

  Rule-set C1: General Rules Rule C1a. Infiltration and Scouting missions are defined as:     Infiltration - Working within enemy base borders in a way that has a tangible effect on gameplay (for example, saving captives)     Scouting: Working within enemy spawncamp boundaries in a way that has no tangible effect on gameplay (for example, completing RP tasks) Both Infiltration and Scouting Missions remove movement restrictions within base borders. Rule C1b. Infiltrations and Scouting Missions MUST be granted by a NCO+ (IC rules may differ from this, so long as it is granted by a NCO+). Rule-set C2: Infiltration Rules Rule C2a. No more than four units may infiltrate a base at one time. (This does not include units that are currently captured). Rule C2b. Infiltrations must have a valid reason. Note: Synth Vehicles cannot be stolen Rule C2c. Once a task has been completed, the Infiltrating Unit(s) must attempt to escape, or die trying. They may only engage enemy units actively blocking their escape. They cannot ask for additional tasks. Rule C2d. Infiltrating Units may not interrupt debriefs, tryouts and trainings by any means (killing, causing chaos, etc). Out of base DBs and tryouts are fair-game. Rule C2e. Any player can be targeted for an Assassination Mission, however only one player can be chosen and assassinated only once, including if they’re revived. Rule-set C3: Scouting Rules Rule C3a. Only MACE/SU/CROSS/Scav can perform Scouting Missions. Rule C3b. Scouting Units must immediately exfiltrate once spotted.
• D. Building Rules

  ---

  Rule D1. Players may only build and spawn props when on a GRID or Engineer class. Rule D2. Constructed buildings must have a material appropriate to their faction.     Rebels use a rusted metal and scrap     Combine use a blue metallic colour Rule D3. Buildings must follow the laws of physics. Examples of Prohibited Structures:     Floating structures with no means of reasonable suspension     Bridges without supports     Invisible walls     Ramps without a reasonable slope Rule D4. Buildings that majorly disrupt player movement are not allowed. Rule D5. Buildings used for training, tryouts within a faction base are exempt from Section D, IF they do not disrupt the server, players or gameplay. Rule D6. No constructions involving moving props (Sling-shots, spinning traps, doors, vehicles, etc.). Rule D7. All props created must be removed when switching to a different class. Rule D8. Undoing/quick-deleting fortifications when enemies take over the area is prohibited. Rule D9. Crouch/Jump structures, obstacle course structures, “Puzzle Room” structures, and other such structures, are not allowed and are defined as follows:     Crouch/Jump structures: are when at some point within the base, you MUST crouch or jump to make some progress.     Obstacle course structures: obstacles such as stepping stones, parkour segments, mazes, etc, are a part of the structure.     “Puzzle Room” structures: when there is a hidden button, a button-based password, or an intentionally secretive entrance to a base for the purpose of fooling other units. Rule D10. You may not reinforce vehicles with props to prevent damage, or edit them in any way. Rule D11. Combat building (Building whilst taking fire) is prohibited. If you are killed while constructing you must delete props that do not form a defined structure, or that would break other building rules.

  ---

  Failure to adhere to these rules will lead to the deleting of said props, with or without warning. Repeat offenders/major offenders will be permanently stripped of their ULX perms.
• E. Class Specific Rules

  ---

  Rule-set E1: Vehicle Rules Rule E1a. Combine Manhacks must have a red light. Rebel Manhacks must have a green light. Rule-set E2: NPU Rules Rule E2a. NPU can ID check (or kill/arrest if they are deemed an imminent threat) anyone suspected of being an SU for any IC reason that does not fall under metagame. Arresting or killing someone without reasonable evidence is punishable under Metagame. Preemptively arresting a suspected unit without substantial evidence before ID checking them is not allowed, and is punishable under Powergame. Improper / random arrests are to be considered as both an IC and OOC issue. Evidence of breaking rule breakage must be sent to either NPU/MP or AIU/Council officials. Rule-Set E3: Grid and Engineer Rules Rule E3a. Only Grid/Engineers can hack player-controlled Manhacks and Rollermines, and can only be done while being held by a gravity gun. Rule E3b. Deployed vehicles are able to be scrapped by engineers/grids with the approval of the respective OVA/Tech officials in exchange for half of the vehicle’s original resource cost being granted back to the faction by a Staff member or Gamemaster.
• F. Civilian and Anarchist Rules

  ---

  Rule F1. Civilians or Civilian organizations spotted by combatants in possession of any contraband (openly carried weapons/tools of destruction) may be prosecuted by either faction. Rule F2. Citizens may be detained-and-prosecuted by the Combine and Rebels if they are non-compliant to orders Rule F3. Anarchists may steal and use any vehicle except air vehicles. Rule F4. Anarchists may not kill within faction bases without good reasoning. Rule F5. Anarchists can not kill civilians unless they are proved to be a threat. Rule F6. Anarchists belonging to an organization numbering 2 or more members, may kill members of the Combine or Rebels in their own base. Spawn camp and DB interruption rules still apply. Rule F7. Players who did not directly witness an Anarchist Civilian’s actions may not announce a KOS / AOS for said actions, for example, restating an Anarchist KOS previously stated by another player. Rule F8. Shops and neutral constructions cannot be attacked by Combine or Rebels if they are not proven to be hostile. The following are examples of hostile construction: Attacking non-hostile constructions in any way, including damaging their props, will result in a FailRP warning by staff members. Rule F9. Civilians do not carry IDs. While they may use the command /ID, forcing them to is powergame.