Gmod Server Rules
Glossary
RDM means “Random Death Match” – This is shooting/killing someone without a valid roleplay reason.
RDA means “Random Arrest” – This is arresting someone without a valid roleplay reason.
LTAP means “Leaving to avoid punishment” – This is when someone leaves a situation to avoid receiving punishment e.g. Disconnecting the server whilst being in a staff sit.
OOC means “Out Of Character” – This is chats that have no relation to roleplay and can be accessed by typing “/OOC” or “/LOOC” in chat. Out of character chat is not a platform to be disrespectful.
IC means “In Character” – This is when acting or talking about things involving your character or another. Your character may have their own personality and should have feelings separate to your out of character self.
Metagaming is using any form of out of character communication or information in-character. This is using information received out of character to an advantage.
Minging means purposefully harming the roleplay of the server, breaking or attempting to break the server’s rules in any way and generally acting like an idiot.
If you have any questions about rules, speak to a staff member in-game or on the forums who can be identified by their tags.
Section 1: General Rules
1.1 – Staff word is final. If you disagree with a staff members judgment, report it on the forums or approach a HA+.
1.2 – No racist, sexist, homophobic or offensive language. This goes for IC & OOC.
1.3 – Do not Meta Game.
1.4 – Do not RDM another player. Even with consent, you should only kill a player during an event as long as you are an event enemy.
1.5 – Do not randomly fire a weapon. You must have an RP reason for firing a weapon.
1.6 – Advertising of any form will not be tolerated and will result in a permanent ban.
1.7 – Using Hacks/Cheats/Glitches/Exploits/Scripts is not allowed, this includes known bugs. If found using them, you will be given a permanent ban.
1.8 – FailRP is not tolerated. All situations should be handled in character until told otherwise.
1.9 – Mass breaking server rules with no intention of roleplaying will result in a permanent ban; to the staff member’s discretion.
1.10 – Do not go AFK for more than five minutes if the server has 75+ players online.
1.11 – Serious Roleplay is always in effect unless prior stated by a senior staff member.
1.12 – Under no circumstances are you to impersonate another staff member, this applies to everyone staff or not.
1.13 – Voice Changers may only be used for RP reasons, you must have your voice changer reviewed and approved by an Admin+ before using it.
1.14 – Excessive use of caps in OOC is a warnable offence.
1.15 – Do not mic spam.
1.16 – Do not LTAP.
1.17 – Spoilers on Star Wars films or TV shows within their first month of release will result in a minimum one week ban.
1.18 – Do not spam chat with messages.
1.19 – Do not complain about staff or their decisions in OOC chat, file a complaint on the forum or approach a Head Admin+.
1.20 – Loopholes in any way or shape won’t be tolerated, check with a Staff member if you’re unsure of your actions, and remember rule 1.1
1.21 – You may NOT use Acts or PAC3 animations during combat or immediately after, under any circumstance. Doing so will result in an instant warn. Continued use will result in bans.
Section 2: Discord Rules
Any discord relating to MVG must abide by MVG’s rules.
2.1 – Regimental higher-ups may hand out regimental discords however it is not a requirement for players to join them.
2.2 – Personal discords may not be advertised in-game or on any regimental discord.
2.3 – Any issue that is In Character should be dealt with on the server, deal with issues in game where possible rather than over DM.
2.4 – Discriminatory jokes and hate speech based on a person/groups: Race, ethnicity, nationality, gender, sexual orientation, religion or disability will not be tolerated.
2.5 – Explicit, NSFW content is not allowed (this includes detailed descriptions of explicit acts) at all in the Discord.
2.6 – Sharing personal information about another individual (including posting pictures of them) without their consent (doxing) will not be tolerated.
2.7 – Keep memes and gifs in the off-topic-and-memes unless directly responding to a message from another channel, but do not spam the channel.
2.8 – Do not use voice modifying applications or anything that changes the pitch and sound of your voice.
2.9 – Do not impersonate or change your name to that of other members.
2.10 – Any form of advertisement of another Discord or community without is NOT tolerated, and will result in a permanent ban on MVG platforms.
2.11 – Do not disrespect your fellow members. Treat everyone with respect and do not provoke, attempt to create, or actively take part in disrespect towards other members.
2.12 – Do not harass or @ staff & Management randomly, if you need assistance please use the help & support section and someone will assist you.
2.13 – Pinging staff/staff roles without valid reason will result in a warn, further pinging will result in a ban.
2.14 – All suggestions/bugs must be posted on the forum, do not DM members of Senior Staff or the Development Team regarding development.
2.15 – Admin permissions may be temporarily requested by a HA+ if required to handle a report. For example, if a HA+ receives reports of bullying/racism on one of the official discords they have the right to get temporary admin perms until the report has been completely resolved.
2.16 – Staff members have the final say on what is allowed. They have the right to remove any post as they see fit.
Section 3: Roleplay Rules
3.1 – The Grand Army of the Republic is a military as we all know, so behave appropriately as a Clone or military personnel would.
3.2 – Do not abuse your rank or your role and act within the guidelines.
3.3 – Do not use Comms Channels (/c /tc, etc) for non-IC matters, comms are in-character communication devices.
3.4 – For actions used in RP, use /me to describe the actions of your character. You should use /rp only for actions that affect the whole event/specops/training.
3.5 – Follow the three Brotherhood rules: Bronze, Silver and Golden.
3.6 – Do not misuse your Loadout, use it with common sense following RP, e.g. do not grapple to ships, do not fly with rocket boots outside the ship.
3.7a – You must have a valid RP reason and permission from staff to turn rogue.
3.7b – You may shoot/kill a clone who has gone rogue.
3.8 – Rear Admiral+ and Supreme General may execute with a valid RP reason (that needs to be provided upon staff request). Executing players without reason will be treated as if breaking rule 1.4.
3.9 – Do not attempt to break someone out of, nor break out of, cuffs without a valid RP reason.
3.10 – Dead men tell no tales. If you have been killed, you will have no memory of what occurred before you died.
3.11 – Promotions must be handled in-character and on the server.
3.12 – Do not disrespect or invoke beef with another regiment, this includes OOC chat.
3.13a – Players may only heal themselves if they have been out of combat for at least 10 seconds. Being out of combat in this context means not using any equipment to engage the enemy nor being actively engaged by enemies.
3.13b – Players may not heal other players that are actively being engaged unless the healer is not being fired upon and is healing with the medigun or bacta grenade. If the healer and heal target are both behind cover, the healer may still heal the friendly if they are actively engaging the enemy but must not be taking any damage.
3.13c – Players may defibrillate hostages, event characters, the OD and fleet when it is not important to the story, and unless told otherwise by the event host. The defribrilator can only be used when the medic is out of combat.
3.14 – When a player is using “active camouflage” or cloak while crouched or walking, your character cannot see them
3.15 – You must be out of combat for at least 15 seconds before cloaking.
Section 4: Regimental and IC Rules
4.1 – Regiment changes must be coordinated with your Executive officer or Commanding officer, major changes must be approved by the Generals team via an IC Suggestions.
4.2 – SGT+ may train cadets (a CPL may train a cadet with supervision from an LT+) LT+ may host training unsupervised.
4.3 – LT+ may host training unsupervised, SGT+ may host trainings with supervision.
4.4 – Specialist Equipment and Vehicles require Navy/OD permission to be deployed.
4.5 – You may only spawn vehicles at the briefing area of events or the main hanger/courtyard and must be granted by Navy/OD to take off and leave base/ship.
4.6 – You may only pilot ships/drive vehicles/use special regimental equipment if you have been trained IC to do so, are playing in an RP job which has access to that equipment and have had permission from a navy/general or staff member.
4.7 – Arrests may only be up to ten minutes upon entry to the brig.
4.8 – When arresting cadets take them to the cadet or training room, not the brig, they need to be trained not imprisoned.
4.9a – Roleplay names must be formatted as abbreviated regiment name e.g GC followed by abbreviated rank (excluding MJR+) e.g SGT followed by four appropriate numbers and an RP appropriate name (to staff’s discretion). Full name example: GC SGT 3504 Bob.
4.9b – Only MJR+ may spell their rank without abbreviation or numbers.
4.9c – Rank abbreviations: CR-CT-PVT-PFC-LCPL-CPL-SGT-SSG-MSG-SGM-2nd LT-1st LT-CPT-MJR-XO-CO-MCO-ABG-BG-SG
4.10a – Ribbons which are handed out by Navy or Generals may be kept in your RP name after resigning from an IC role, ribbons handed out by regimental higher-ups may not.
4.10b – Ribbon abbreviations must be no longer than three characters in length. You may have up to two ribbons in your RP name at any one time if awarded.
4.11 – You may spawn entities (anything in “entities” tab) only if you are out of combat for at least 10 seconds.
4.12 – You cannot shoot a vehicles weapons whilst the vehicle is using an LVS Resupply/Maintenance Pad.
4.13 – You cannot use explosive devices whilst in flight with a jetpack or rocketboot.
4.14 – All vehicles should be spawned either using the requisition droids (base/ship maps) or by asking staff to spawn them (planet maps) in a suitable location (LZ/Landing Pad)
4.15 – Takeoff priority during combat situations are as follows, in descending order: Razor Squadron | Other 327th | Sentinels / RC Characters | Other Jedi | Fleet / Generals.
4.16 – Never ram another player or ship with your own ship.
4.17 – Do not land on people, NPC’s or other vehicles.
4.18 – Never leave your ship unattended, ask the staff to despawn it if you are done with it.
4.19 – Never give your ship to anyone who isn’t in a regiment/job allowed to fly and is trained to fly.
4.20 – To utilise any LVS Bomber you need both OD and event hosts permission.
4.21 – Dioxis Gas cannot be used on droids.
Further Regimental and In Character rules can be found on the forums.
Section 5: Donator Regiment Rules
Failure to follow these rules may lead to a package strike or removal.
Upon first strike player will lose access for one week. Upon the second strike, said the player will lose access for two weeks. Upon the third strike, the player will lose access permanently and may only receive access under senior staff’s discretion.
Failure to follow the guidelines of your donator regiment may also lead to a package strike.
5.1 – Do not abuse your equipment or the skill system to gain an advantage, resist arrest or mess around.
5.2 – XP, skill points, hilts, and crystals may only be handed out to Jedi with a Jedi General present.
Neutral Job Rules
5.2 – All neutral jobs must be used to roleplay and not to minge. This also means not abusing equipment (e.g to avoid arrest).
5.3 – Wookies may not use the Speeder bike without the Navy or OD’s permission.
5.3 – Neutral roles may not work with enemies unless told so by staff. All neutral jobs work under the orders of Navy, Generals or the OD.
5.4 – Neutral jobs have only open comms. In addition to that maintenance droids, medical droids and bounty hunters working for the republic have secured comms It is FailRP to ‘steal’ comms unless the staff has granted permission.
5.5 – Weapons and comms cannot be stripped until the hostile has surrendered by holstering their weapons.
5.6 – If misbehaving, droid jobs must be taken to the AI Core instead of the brig.
5.7 – Staff may strike neutral job packages if rules are not being followed. Upon first strike player will lose access for one week Upon the second strike, said the player will lose access for two weeks. Upon the third strike, the player will lose access permanently and may only receive access under senior staff’s discretion.
Section 6: Event Enemy Rules
6.1 – Super battle droids can only walk.
6.2 – You may only shoot 1 rocket every 20 seconds, this applies to all rocket launcher weaponry as well as the B2 Super Battledroid wrist rockets.
6.3 – You should NOT ask to change classes when you are an event enemy. You get what you are given and you will not be able to change role.
6.4 – If main characters enter a ship, you should NOT shoot at them. If you do it will result in a warning.
6.5 – All event character names must be RP appropriate. Failing to have a suitable RP name will see you take no part as an enemy. It is to the staff’s discretion what an appropriate name is.
6.6 – Event characters must abide by the RP rules, this includes not running around and screaming like an idiot. Failing to do so will see you removed from the event.
6.7 – Only main event characters or sith may resist a Jedi General’s mind tricks when under interrogation.
6.8 – Melee Enemies must focus on Melee Friendlies. Should there be no Melee Friendlies in the area they are free to focus on anyone they find.
6.9 – Refer to 3.13 do not use explosive devices whilst in flight, specifically deathwatch.
6.10 – Upon reaching 1hp Event Enemy Characters should remain where they are and not attack anyone until they are above 1hp again.
6.11 – Prioritize ships, don’t just ignore them to go hold down mouse1 at a group of people.
6.12 – Do not hover in any ships, always be moving especially during a dogfight.
6.13 – You may NOT enter a vehicle of a faction which is not your own, without the event hosts permission.