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. FailRP is defined as exhibiting behaviors that break roleplay. (such as bunny-hopping, disrupting the gameplay of others, having an invalid name.) Determined by Staff.      Avoiding or breaking role play in any manner is not allowed in IC.      Unprofessional and immature behavior such as “Trolling” or “Meming” whilst in an IC (talking, fighting, etc.) situations will fall under FailRP.      Bhopping is to be categorized under FailRP and is not allowed.      Powergaming and Metagaming are separately defined from FailRP. (Powergame is giving yourself an advantage over players and excluding yourself from certain processes and standard role-play standards - Metagame is taking info from OOC into IC.) Rule A2. No Random Deathmatch (RDM).      Spawn-killing and base-killing are bundled together for the sake of simplicity.      Team-killing also qualifies as RDM.      Team-killing may only be allowed in the context of trainings or tryouts. However, trainings must be officially announced beforehand, and a medic must be present.      Team-killing is also acceptable when killing an ally who is cuffed/captured by the enemy. Rule A3. You may only hold a rank of CO+ on one faction at a time, and for only one character. Rule A4. Areas designated for events are not allowed to be tampered with in any way or form. Rule A5. Factions may only enter and exit their own “base” unless a base raid is occurring. Rule A6. Training may be done by a NCO+ or any enlisted given permission by an CO+. Rule A7. Certain events may alter/denounce some of these rules to suit the map’s and event’s needs. These exceptions rules will be address by Staff if/when this occurs. Rule A8. Abusing an exploit for any reason is punishable at the staff's discretion, the more serious the exploit, the harsher the punishment.      Any attempt to climb on or out of the map boundaries is classified as exploiting. This includes when players fall under the map, and then proceed to shoot at players above them and such. Rule A9. ERP (Erotic Roleplay) is strictly forbidden on the server, and punishable at the Staff's discretion. This goes along with sexual harassment, even if said jokingly. Rule A10. When a player is kidnapped or imprisoned, that player may not be held for an excessive period of time. Maximum imprisonment time equals ten minutes, starting as soon as the captured player is taken into their captor's base. Rule A11. OOC Harassment is not allowed in any way, shape, or form. Toxicity towards players, whether In Character or Out of Character in any context, is prohibited. Failure to follow this result can result in warnings and a ban. Rule A12. Recruits may not leave the recruit room unless accompanied by a Trainer. Rule A13. FOB's and captured points are not considered to be "bases". All players are allowed to be in them Rule A14. NPU and MP are not allowed to sit or "camp" outside or anywhere near the opposing team's base to capture someone. Rule A15. Any form of purposely increasing your own player velocity and/or airtime from projectiles, explosives, or any other means is not allowed. This includes Rocket Jumping, Grenade Jumping, and using bullet impacts to give yourself a boosted jump or movement speed. Rule A16. Players are permitted only 1 character per side. VIPs are permitted 2. (not including any VIP jobs) Rule A17. You may not kill anyone with props from the gravity gun. Rule A18. Captives of either side can not participate in battle at any point. Rule A19. Once stalkerized/enslaved, captives may no longer attempt to escape their captors. Rule A20. Neither faction may question/interrogate their captive after their enslavement/transformation. Rule A21. Stalkers/slaves can only remain enslaved for a maximum of 10 minutes, starting immediately after enslavement/transformation. Rule A22. Ramming players with air vehicles (excluding manhacks) in any manner is prohibited. Rule A23. SU/MACE units may use vehicles they have stolen with CO permission from their faction's respective vehicular divisions. Rule A24. Vehicles (stolen or otherwise) cannot be 'stored', and any method of stockpiling vehicular assets is prohibited. Rule A25. Stolen vehicles must follow the same deployment rules as those bought from the respective faction's vehicle vendor. If a certain vehicle can only be spawned one-at-a-time, then it can only be used as such. Rule A26. Vehicular classes cannot transfer ownership of their vehicle to any other division. Rule A27. Staff member/officer authorization must be requested and accepted in-game. No other platform of communication is valid for these kinds of requests. Rule A28. No one shall discriminate another based on their race, color, religion, gender, or national origin. Rule A29. Only Grid/Engineers can hack Manhacks and Rollermines. 1 roll is required from both parties.      Manhacks and Rollermines can only be hacked in Captured friendly points, and home base.      Rollermines and Manhacks can only be hacked if they are suspended in the air by Grav Guns.      Rollermines may explode at whatever time, unless inside of a base, or mid hack rolls. Rule A30. 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. Rule A31. Only OVA/GRID/Techs/Engineers are allowed to be in gunner seats of vehicles, breaking this rule is an arrestable offense. SUs and MACE are allowed to use the gunner seats of vehicles they have stolen. Rule A32. Officers reserve the right to order units to perform specific tasks such as patrolling, formations, roleplay actions (within reason), missions, inspections, medical examinations or otherwise. Officers are allowed to excuse their units from such orders if such a request arises, but cannot excuse units permanently or preemptively, and must be on-site to excuse one of their units. Units who refuse to follow orders can be demoted at their Officer’s discretion. Units who have been proven (with evidence) to have used OOC means to escape orders (such as changing jobs, logging off, dying and refusing to respawn, etc) is LTARP and is punishable by staff. Running away from COs on the same character for example, would not be OOC means; which means it is to be dealt with via in-character punishment. Rule A33. MP/NPU COs can negotiate openly through /advert to ransom back captured units to the enemy team in exchange for resource points, weapons, or vehicles (Officers from both sides would of course have to agree on the terms, and once they agree the unit will be let loose and the payment will be given to the respective faction by Gamemasters/Staff) Units that are brainwashed to spy are not allowed to be sold back for ransom. Rule A34. Prisoners (who in OOC are willing to) can be brainwashed and turned into spies for the captor’s faction. They can then be released and until their next death are allowed to report enemy positions and information through /PM to the highest ranking MP/NPU on (depending on the respective team that captured them, of course). Once they die the brainwash effect is removed and they no longer can report this information. If the faction suspects one of their members of being a brainwashed spy, they can arrest and interrogate them. If the interrogators win the interrogation rolls, they can expose the unit as a spy and call in a medical unit to cure the brainwashing effects. Units cannot be punished for things they did while brainwashed. (This does not include offenses that violate OOC rules such as TK). A single player (no matter the character) cannot be brainwashed more than once every three days. NPU and MP units are required to log brainwashes and notify their COs when one occurs; in order to minimize cooldown overlaps and confusion. While units are brainwashed, they are not allowed to commit suicide or change jobs. If a brainwashed unit needs to log off for whatever external reason, they must notify their brainwasher. If a brainwashed unit suddenly crashes or disconnects not out of their own volition, they must join back as soon as they can; or make their brainwashers aware of their unintended leaving through some means of communication. Players who fail to adhere to these rules (provided proof) will be warned by staff members for FailRP. Rule A35. You may not shoot/be fired upon during an RP scenario involving /roll. Once a /me has been done, everyone involved must wait until all rolls from each party is complete, and the action is complete. Witnesses who are within the range of seeing the /me action may roll to assist but are not required to do so. Rule A36. Civilians do not carry IDs. While they may use the command /ID, Forcing them to is powergame. Rule A37. 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. If you disagree with a staff ruling or the outcome of a sit, please appeal or file a complaint on the forums; do not incite mass action.

  ---

  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.
• B. Combine Rules

  ---

  Rule B1. Only OVA Kilo and Foxtrot are permitted to use their own vehicles and assets, unless an event or a staff member says otherwise. Rule B2. Combine using Manhacks must keep their manhack light red. Rule B3. Helix may only stalkerize, the use of any other pill is prohibited. Rule B4. MACE units may infiltrate with authorization. Rule B5. Combine units carry ID cards with them, but they can only be read by fellow Combine units. Rule B6. Combine may not shoot teammates to check if they are SU. Rule B7. NPU can ID check (or kill/arrest if they are deemed an imminent threat) anyone suspected of being an SU for any reason, excluding steam profile information (Including profile picture) and their voice. Arresting or killing someone without reasonable evidence is grounds for a demotion by NPU COs. Preemptively arresting a suspected unit without substantial evidence before ID checking them is not allowed. Reasonable evidence is defined as:      Suspicious movements or movement behavior.      Not being in a division’s roster when they should be.      Being near the weapon locker after is has been stolen from.      Having equipment in their possession that they normally would not have (event rewards do not count; similar to this, units cannot be suspected through equipment they do NOT have. Ex: you cannot set up a checkpoint to find SUs and ask a medic to pull out their medkit to prove they aren't disguised.)      Ignoring officer orders.      Going into clearance areas they do not have authorization for. Rule B8. Synth Elite Soldiers are able to partake in NPU interrogations of prisoners, and get to add a bonus of +25 to interrogation rolls, up to 100.
• C. Rebel Rules

  ---

  Rule C1. Technicians are allowed to use air and ground vehicles. Rule C2. Rebels may not steal Synth Vehicles. Rule C3. MPs may make captured MPF into slaves upon applying a slave collar to them. Rule C4. Spectre units may infiltrate with authorization Rule C5. Resistance units do not carry identification of any kind on them. Rule C6. Spectre Units may not disguise as their own Combine Character(s). Rule C7. Vortigaunts are able to partake in MP interrogations of prisoners, and get to add a bonus of +25 to interrogation rolls, up to 100.
• D. Citizen Rules

  ---

  Rule D1. Citizens should be considered non-combatants, but may carry a sidearm OR melee weapon.      This does not apply to official event characters. Rule D2. 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 D3. Citizens may be detained-and-prosecuted by the Combine if they are non-compliant to orders, or killed if an autonomous judgement is in effect. Civil Protection may detain-and-arrest any Citizen with legitimate suspicion of being affiliated with the Resistance. Rule D4. Anarchists cannot kill one another within their spawn. Rule D5. Anarchists may steal and use any vehicle except air vehicles. Rule D6. Anarchists may not kill within faction bases without good reasoning. Rule D7. Anarchists cannot kill Civilians, unless in self-defense.      Ex. The Civilian rats them out to either side. Rule D8. Anarchists can disguise as CWU, though they cannot get a CWU ID Rule D9. Anarchists and Civilians may create organizations.      Max of 20 Anarchists or Civilians. Rule D10. Anarchists and Civilian organizations may side with any faction to suit their own interests. Rule D11. Anarchists belonging to an organization of 2 or more people may kill members of their faction in their own base.      Spawn camp rules and DB interrupting rules still apply. Rule D12. All members of an organizations may be prosecuted as guilty by association for the actions of at least one member.      The "guilty by association" lasts for 1 hour.      Ex. "Sinon gang inc." commits mass murder of Combine. This causes the gang to have a high notoriety and be freely prosecuted until 1 hour is up. Rule D13. Engineers, Civilians, Anarchists and CWU can open any kind of shop (except ones selling weaponry) with the assistance of Gamemasters. Up to 5 props can be used for each shop; props spawned for roleplay purposes contribute to this count. Rule D14. The Site Administrator/CWU administration can set up and enforce business regulations with the help of the NPU, who can arrest violators of regulations. CWU business regulations must be made publicly available and the public must be notified when changes are made to regulation to minimize misunderstandings. Rule D15. Shops and neutral constructions (including shops) cannot be attacked by Combine or Rebels if they are not proven to be hostile. The following are examples of hostile contructions:      Selling blackmarket/outlawed items.      Researching technologies for an enemy faction (constructions such as labs).      Unprovoked attacks by the construction tenants on your faction. Attacking non-hostile constructions in any way, including damaging their props, will result in a FailRP warning by staff members.
• E. Base Raiding Rules

  ---

  Rule E1. No vehicles should be deployed for either side at all to attack or defend during a base raid. Rule E2. Cooldown between each base raid is 30 MINUTES. Rule E3. The faction which is raiding is NOT allowed to spawncamp. Rule E4. 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 E5. You need at least 10 members in the raiding squad as well as a valid reason for you to begin raiding.      This also needs to be brought to the attention of the COs as well as needing a Debriefing stage of sorts to plan your attack/base raid. Rule E6. For approval of the base raid you need CO permission alongside with Admin+ permission. Rule E7. Base raids are never division exclusive.      For example, MACE and SU may not purely send 10+ of their own in, as this classifies as mass infiltration.
• F. Infiltration Rules

  ---

  Rule F1. Infiltrations MUST be granted by a NCO+ (IC rules may differ from this, so long as it is granted by a NCO+). Rule F2. No more than four units may infiltrate inside of a base at one time. (This does not include units that are currently captured). Rule F3. Infiltrations must have a valid reason. These could be, but not limited to, as follows:      Stealing a vehicle / Item.      Assassination of a target.      Prisoner Rescue / Kill.      Spying in on Debriefing or troop deployments.      In search to do any of the above. Rule F4. Once a task has been completed, the Infiltrating Unit(s) must attempt to escape, or die trying. They may not then camp the enemy base, and may only engage units that are actively blocking exits. Infiltration units who are caught attempting to complete multiple infiltration tasks for which no specific permission has been granted will be warned for FailRP. Rule F5. Scouting missions are different to infiltrations in many ways, but still require NCO+ permission. They do not count towards the number of infiltrating units. Scouting rules are as follows:      You may not enter the enemy base.      You may not shoot or kill at all during a scouting mission. If you are spotted or get shot at, you retreat away to a safe distance and disengage the scouting mission.      If you wish to infiltrate during a scouting mission, you must ask for permission from a NCO, and state the reason. Rule F6. MACE/SU units may not interrupt faction debriefs by any means (Killing, causing panic, chaos, etc). Out of base tryouts and DBs are fair game. Rule F7. Only Mace/SU/CROSS/Scav can scout within base borders. Rule F8. All permissions must be granted in TEXT chat on the server so there is a log of the event occurring. Permissions granted over voice chat or over another platform are null and void, classifying any resulting infiltrations as FailRP. Similarly, COs must also report in team chat when they infiltrate with the task they are doing. Rule F9. Cases of SU metagame that do not involve the use of the suspected unit’s steam profile information (including their profile picture), their voice, and their Level are to be taken up with NPU COs, not staff members. Management members/faction leadership can be contacted if NPU COs fail to discipline a unit.

  ---

  Sabotage Rules 1. C4     a. MACE and SU have "C4" as part of their loadout. C4 is not to be taken from the unit upon capture.     b. C4 can be placed on any of the following:          Props (Such as walls of a fort, or the supports of a bridge).          Vehicles that are inactive within a base.          Artillery pieces.          Other entities spawned in by construction classes.     c. A roll is performed with a staff member. If the unit loses, they must wait 10 minutes before they are allowed to attempt a demolition on the same target/building. Important Note: If C4 is placed on the support of a bridge or building, everything supported by that beam collapses with it. Place C4 wisely. 2. Hacking     a. In order to hack, you must get an admin to /roll against any valid terminal, button/lever, or electrical equipment. Upon a failed hack, an alert will be sent out by the staff member. A successful hack may result in one of the following:          Firing the artillery to assist their faction (check Rule G18).          Accessing information on the system.          Jamming/disabling the system for 15 minutes.          Opening/closing the system. Important Note: A unit must wait 20 minutes after a successful hack before going for the same entity again.

  ---

  Rescue Rules 1. Captives may be untied while disguised or cloaked, though initiating this act is grounds for KOS. 2. Unless the infiltrating unit fetches the captives gear from a weapons locker before or after freeing the captive (Performed through a /me and calling staff, no roll required), the captive may not use any weapon or gear that they had before capture. 3. During a rescue, anyone may be killed freely if they are directly interfering with your mission or will otherwise respond with immediate force. This includes bodyblockers and anyone within the room. 4. Other units may be rescued during the process if they are captured at any point during the infiltration, but their rescue must be announced over team chat before or immediately after the action (no additional CO perms are required). Multiple rescues may be included within an infiltration request. This rule overrides Rule F4. 5. If no more units are captured, the unit must exfiltrate immediately.

  ---

  Assassination Rules 1. Any player can be targeted by an assassination, but that player can only be killed once per mission, including if that player is revived. 2. Only one player may be targeted by an assassination per infiltration. Attacking multiple targets is banned. (Unless those around you are directly interfering). 3. Failing an assassination means the unit must exfiltrate immediately. They may not stay in the base and request further targets. 4. Players cannot be killed directly in their spawn room. Once they are outside, wait around five seconds before firing. If the target doesn’t spawn in a room, wait fifteen seconds before firing (Or until they move a good distance away). 5. Consistently targeting the same person is a breach of the rules unless twenty minutes passes.

  ---

  Stealing Rules 1. Units may attempt to steal any enemy vehicle at any time, either out on the field or in the enemy base. It is however recommended that COs do not approve these missions when the enemy team is heavily beaten back, and is relying on mechanical support to prevent being spawntrapped. 2. In the event that a method of hijacking is broken or does not work, units may climb inside the vehicle if they are able to, and perform a /me, followed by a roll. The driver counter rolls, if he fails, he must leave/suicide. - PASSENGERS AND OTHER CREW MEMBERS MAY ATTEMPT TO ASSIST IN THE ROLL AGAINST THE UNIT. 3. Air vehicles may fill up all of their seats in order to help prevent hijackers. The best way to counter this is to disguise as CWU, NPU or OVA.
• G. Building Rules

  ---

  Rule G1. Buildings constructed from props must have a material appropriate to the faction.      Rebels would use a rusted metal, and the combine would have a blue-ish metallic colour. Rule G2. Bridges and such MUST be supported, or have a visible method of suspension. (Rope tool only does not count.) Rule G3. No floating props or props that defy reality. (Invisible walls, nocollided doorways.) - The only exception to this is when props are nocollided to prevent obstruction during construction. Rule G4. Ramps can not be too large, or too lengthy, must have a reasonable slope, and must be supported. Ramps may only be used by infantry, but may not be used as cover objects; as this incites headglitching. Rule G5. No constructions that involve moving props. (I.E: Slingshots, spinning traps, etcetera.) - This rule does not include moving doors and windows for fortification entry. Rule G6. Spamming props/Using minge props (Such as spawning footballs, etcetera) is prohibited. Rule G7. You are NOT to spawn props when you are not on your respective ULX classes (GRID/Engineer). Rule G8. Any and all props created by yourself must be removed when you switch to another class. Rule G9. Undo-ing or quick-deleting fortifications when enemies take over that area is prohibited. Rule G10. “Fingerprint Scanners” or “ID scanners”, or otherwise buttons that are made for the purpose of keeping the enemy from opening a door, are FailRP. Rule G11. Crouch bases, obstacle course bases, “Puzzle Room” bases, and other such bases, are not allowed and are defined as follows:      Crouch bases are when at some point within the base, you MUST crouch to make some progress.      Obstacle course bases are when someone makes obstacles such as stepping stones, parkour segments, mazes, etcetera as a section of the base.      “Puzzle Room” bases are when someone hides a button, makes a button-based password, or an intentionally secretive entrance to a base for the purpose of fooling other units. Rule G12. Construction of vehicles or methods of transportation out of props (Cars, trains, balloons, “battle bus”) is not allowed. Rule G13. You may not reinforce vehicles with props to prevent damage, or edit them in any way. Rule G14. Combat building (Building whilst taking fire) is prohibited. If you are constructing, and then you are killed, you must delete props that are out of place. Rule G15. Building classes can only build within the limits of small structures, and must not block key parts of the map that majorly disrupt player movement. Rule G16. Props & structures built must follow lore to some extent, and must be built in a realistic fashion.      Building/spawning illegitimate structures & props is considered FailRP, and is to be determined by Staff.         {Ex:} Includes but are not limited to large tubes/walls/platforms, ridiculously-huge prop bridges/ramps/buildings, some objects found in nature such as rocks, trees, and certain effects. Rule G17. Building classes cannot build structures or devices/utilities that infringe on another class/job's specialty (anti-vehicle, vehicle creation/driving, etc). Rule G18. Engineers/GRIDs can build artillery pieces with props. There is no limit to the number of props that can be used for an artillery piece. The guidelines for artillery use are as follows:      It must resemble an actual artillery piece.      Up to 4 shells can be fired in one session.      Cooldown on using artillery is 15 min, no matter the amount of fired shells.      Cooldown on building another artillery is 1 hour, if previous one gets destroyed (for each faction). Rule G19. Once a day, Engineers/GRIDs can work on “projects” where they complete a list of defined tasks through roleplay (scavenging a specific part from a machine, building a contraption, finding someone with a certain blood type, etc). After the tasks are complete, they roll against a staff member to determine if the project was a success. If it is successful, depending on the project a certain set of rewards such as a special vehicle, some high powered weapons, or a special unit may be granted to the faction. Whether the project is a success or failure, they cannot partake in a project until another 24 hours later. Engineers/GRIDs can send non-builder classes on the required tasks, and being sent on a successful tasking is valid grounds for a promotion. Up to 10 props can be used for a single project. Projects must be approved by Engineer/GRID COs and logged accordingly to prevent overlap or confusion. Project Blueprints: Ratmobile - 1x Rocket crate + 1x generic ammo crate + 2x Metal Sheets = 2x Ratmobiles     Method      GM gathers opposing side on a point and tells them to hold off the other side.      Locate the opposing-sides encampment.      Kill all opposing units and secure all materials within the event area.      Secure at base. Anti-Tank Mounted Vark - 1x Railcannon emplacement + 1x Vark = 1x AT Vark     Method      Opposing side has to prevent a Vark from being secured and brought back to base.      GM chooses a location that is closer to the opposing side’s spawn to a rail cannon and side doing the project needs to secure the rail cannon at base. AR3s - 2x Ammo Crates + 1x Energy Cell + 1x Antimatter Cell = 4x AR3s     Method      Locate the ammo crates within the city area.      Locate the antimatter cell & the energy cell at downed APC wreckage.      Secure all materials at base. Drones! - 3x Broken City Scanners + 1x Gas Can + 2x Metal Sheets = 3x City Scanners (Scanner Pills with 1000 HP)     Method      Locate the gas can and metal sheets at a destroyed jeep wreckage.      Find the three scanners throughout the city.      Secure all materials at base.

  ---

  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.
• H. Spawn Camping

  ---

  Attention: Players are HIGHLY encouraged to screenshot anything they believe to be spawn camping and send it to an officer as soon as possible. The reason Section H’s spawn camp rules are so comprehensive is due to the extreme subjectivity the term holds.

  ---

  Rule H1. The definition of “spawncamp” has been defined as follows:      Preventing the passage of enemy units through their spawn/base 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.      Refusal to fall back from an area near the enemy spawn/base if being ordered to do so by a superior, no matter the intentions for being close. Rule H2. Any evidence (circumstantial, material, or by overwhelming hearsay) is required to be submitted when reporting spawncamping, no matter what. Rule H3. Depending on the intentions of the reported unit or the circumstances of it occurring, the officer can perform a punishment ranging from a Verbal warning to a CK. After a first offense by the same unit, from then on the punishment will be at minimum a demotion. Rule H4. Refusal of the presiding officer to punish a unit accordingly will result in a CK of the offending unit by leadership, and at minimum a demotion of the presiding officer. Rule H5. Refusal of leadership to act on this themselves if such a situation arises will result in the demotion of the leadership individual in question by management, a CK of the officer they refused to reprimand, and a CK of the unit that officer refused to punish. Rule H6. If at any point a unit reporting camping believes their evidence is being ignored by an officer, they can send that evidence straight to leadership or management if need-be. If an officer is found to be intentionally ignoring or hiding evidence to defend an offending unit, they will be CKd on the spot and blacklisted from all officer positions in both factions. Visual Representation:
• I. Class Specific Rules

  ---

  I1. MACE Rules I1a. Using a flashlight, or using chat as a radar (holding down mic button/using /y to see nearby units) to find MACE units is metagame. I1b. MACE can change their names to be either be blank, or a rebel name to avoid being metagamed. Do not change it to another Combine name, it kinda ruins the point of you not arousing suspicion from metagamers. I1c. Incidentally bumping into a MACE is a good reason to shoot them. Deliberately trying to bump them, is not, unless they are already aware of your presence (via non-metagame means). I1d. If you feel that someone is metagaming, but aren't sure, call staff to observe. I1e. If you have been detected (Someone bumps into you, you have recently uncloaked and killed their squadmate, you speak through the mic OR if they see your chat), enemy players are permitted to “panic fire” (Shoot into random corners and whatnot) to try and flush you out. I1f. Kills made by MACE that show up in the killfeed (I.E. ones not made by suppressed weapons) are valid grounds for them to be hunted down and become known In-character that there is a MACE nearby. Tip: Always use video recording software when infiltrating for long periods. It is the best way of catching metagamers in the act.

  ---

  I2. SU Rules I2a. When disguising, SU may change their name to whatever is necessary for their class. I2b. SU must maintain the correct name formats indicative of the class they are disguised as (As Combine Units have visible ID that can be read by each other). - Failing to maintain this is a valid reason for suspicion. (When disguising as a civilian/anarchist, this does not apply). I2c. If you are disguising as another player, using incorrect ranks and squads is reason for suspicion (Ex: OTA SHIELD OFC III Phenix would be suspicious if Phenix was a CmD of SHIELD), and in most cases KOS. I2d. Disobeying orders from superiors, or acting suspiciously (hanging back from your squad and being seen to be taking aim at them directly, using climb swep as a class that doesn’t have it, pulling your crowbar out, using your DMR as a class that doesn’t have one, etc.) is enough reason for action to be taken against the unit. - If you do not behave like one of them, expect to be treated with suspicion. I2e. Using Quartermaster weapons is not reason for suspicion, ‘nor is your player level, nor is how your voice sounds. (“Oh you sound like an SU I’ve met before. *bang* - Is metagame). I2f. Pretending to be deaf to bait enemies into typing out demands for ID and then shooting them, is powergame. If you are deaf, fix your audio. I2g. Unless under imminent threat, non-NPUs are not to shoot suspected SUs without authorization from an NPU or a CO. I2h. Kills made by disguised SUs that show up in the killfeed (I.E. ones not made by suppressed weapons) are valid grounds for them to be prosecuted as suspected SUs. 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.