Not open for further replies.


HR Director & Learning Development
Super Admin
Titanium VIP
  • Nov 14, 2023
    This section's sole purpose is to be used as a reference for Members to validate their ingame moderations; either it be a ban, kick, or warn.

    For instance, a User has been banned for LTAP. Here the User gets to understand what LTAP is & how can it be avoided in the future by referring the guidelines as mentioned below.

    • Should a user express any forms of disrespect towards any Staff Member(s).
    • Should a user demand their ban appeal to be accepted, thus ban is voided & lifted.
    The Corporate Team reserves the right to reject your ban appeal if they've deemed that the User has no intention of appealing, nor they're changing for the better, or to improve their moderation history with Us, Mountain Interactive Corp.

    This policy is in-effect for an appealing User that has Class C, or even Class D in their records.
    We imply the Use of this Policy by having an agreement between 2 parties, Us & Appealing User.

    We're to specify a said deadline that the Appealing User may not violate any equivalent or worse guidelines.
    Failure to do so will result in their account being terminated across all of our services that we (may) use.

    1. We require our Mountain Moderation Team to use the violation TERM/ACRONYM; such as, FRP, NLR, RDM, etc.. when applying a ban/kick/warn on a User.
    2. All Evidences of the violations will be attached in the "notes" section of YOUR profile. (
    3. Every violations are categorized into Subtitles and MIR&R § , a.k.a. Mountain Interactive Rules & Regulations Sub-Section(s).
    4. Each sub-sections are also divided into classes; A, B, C & D. With D being the highest of violation severity.
    All classes are appeal-able, as long as it doesn't violate Terms Of Services & Guidelines of third-party services that we currently use.

    Class A | First Offense ~ Warns/Kicks
    Class B | Second & Third Offense ~ Temporary Bans (24 hours > 48 hours)
    Class C | Forth Offense ~ Permanent

    Class A through C can be appealed directly after violation.

    Class D | Permanent ~ Intentional/Purposely violating.
    - Appeal after 30 days or through support mail.
    - Email: [email protected]

    Maximum Number of violations eligible for said class will not be specified.

    Subtitle 1: Public Regulations

    MIR&R § 101: New Life Rule (NLR) Class A
    ∙ After death, whether that be by bleeding out or being shot to death, a player may not return to the location in which the roleplay scenario was at; nor can an LEO pursue the original suspect.
    ∙ Players are exempt from NLR if they need to respawn or reset for roleplay purposes; however, if players are found using this clause to bypass NLR for obvious reasons, a harsher punishment will be imposed.

    MIR&R § 102: Fail Roleplay (FRP) Class A
    ∙ Players may not commit any actions that would be considered as imaginary/non-existent in the real world.
    ∙ These actions consist of but are not limited to:
    a. Getting into a wreck and pretending nothing has happened.
    b. Getting shot and not pretending to be wounded.
    c. Immediately pulling a gun out on an individual who has you hostage.
    d. Accessing the Police Armory without any further RP
    e. Usage of Premium, or Custom Inserts that aren’t designed for that specified team

    MIR&R § 103: Fear Roleplay (F-RP) Class A
    ∙ A player should express their fear in-game equivalent to that of in-real life
    ∙ Example: When you’re being held hostage, a gun is drawn to yourself, it’s said that you should obey the commands of the hostage-holder as you’re being threatened with a firearm.

    MIR&R § 104: Combat Logging (CL) Class A
    ∙ This section can come under RTAA/LTAA
    ∙ Anything alongst the line of resetting, or leaving the current in-game experience; to prevent any loss of belongings or financials due to a current, on-going combat; any further roleplay scenario that has correlations to combat.

    MIR&R § 105: No Intent To Roleplay (NITRP) Class D
    ∙ Players may not purposefully ruin the game or roleplay experience for others by actions such as, but not limited to:
    a. Camping a building/area for the sole purpose of “killing all of the cops.”
    b. Being in an Emergency Service team just to obtain weaponry.

    MIR&R § 106: Random Deathmatch (RDM) Class D
    ∙ Players may not part-take in or start a random death match.
    ∙ RDM's fall under the following definitions:
    a. Player who has attempted to shoot another player for no underlying reason.
    b. Player who randomly shot & killed another player for no underlying reason.

    MIR&R § 107: Mass Random Deathmatch (MRDM) Class D
    ∙ Players may not part-take in or start a Mass RDM's.
    ∙ Mass RDM's consist of:
    a. Killing 5 or more players consecutively without any specific reason.

    MIR&R § 108: Power/Meta-Gaming (P/MG) Class A
    ∙ Power/Meta-Gaming in all forms is prohibited.
    ∙ P/MG is the act of using a game mechanic, external information, or a roleplay concept to favor a specific character or story and give them an unfair or unrealistic advantage.
    ∙ Idea of having your in-real life knowledge used on the current in-game character, that includes the usage of track command; in case a Moderator Member.
    ∙ Usage of streams or other media items (pictures, or videos) to gain an advantage on another player.

    MIR&R § 109: Out Of Character (OOC) Class A
    ∙ Players must stay in character while in-game and must not break this.
    ∙ Players may only go out of character when talking to staff members or when the situation requires it.

    MIR&R § 110: Abuse of ACS (AoA) Class A
    ∙ Players may not abuse ACS in an attempt to gain a tackle advantage on another player.
    ∙ Players may not knock out any other players with ACS for no absolute reason. (comes under RDM)

    MIR&R § 111: Player Disrespect (PD) Class A
    ∙ Players shall not use any sorts of slurs, or method of discrimination, nor harassment to one another.
    ∙ In-cases where a player reports another player, they should have valid evidence or video showing that such section has been violated and the reporting party wants to press charges.

    Subtitle 2: Vehicle Regulations

    MIR&R § 201: Vehicle Deathmatch (VDM) Class A
    ∙ Players may not part-take in or start a vehicle deathmatch.
    ∙ VDM falls under the following:
    a. Any player who purposefully rams his/her car into another player without any underlying cause (not being in danger etc.)

    MIR&R § 202: Reckless Driving (GTA) Class A
    ∙ Players may not drive unrealistically or erratically for a long period of time, nor can they drive with speeds over 200/mph, as well as driving off-road unless the roleplay situation calls for it.
    ∙ Speeding 200/mph and continuously flipping the car, as well as ramming other individuals without a specified reason.

    MIR&R § 203: Drive-By's (D-RDM) Class A
    ∙ All drive-By's must be within a connection between you and the other player that takes place in roleplay.
    ∙ These can't be done randomly against other players as it would be counted as RDM.
    Subtitle 3: Civilian Regulations

    MIR&R § 301: Reset/Leave to Avoid Arrest (R/TAA) Class A
    ∙ Player left the game due to technical difficulties.
    ∙ Resetted and left the game; not coming back.
    ∙ Players are prohibited to leave the game nor reset their character while being in an active roleplay.
    ∙ Players must notify others if they've faced technical difficulties through Discord to void getting banned.

    MIR&R § 302: Scene Interference (SI) Class A
    ∙ Players may not interfere with any RP scene they aren't a part of. If you were not originally a part of that roleplay scenario, DON'T attempt to join it unless it directly affects you.
    ∙ Players may not use a traffic stop that they aren't a part of to ambush anyone, especially LEO.

    MIR&R § 303: Interactions with Fire/EMS
    ∙ Players may not interact with Fire or EMS personnel with the intent to kill, murder, shoot at, kidnap, or commit any crime against said individuals.

    MIR&R § 304: Authorized Use of Vehicles (AUV)
    ∙ Players may drive any vehicle(s) they want to operate.
    a. Includes all the whitelisted teams, donator vehicles, or custom-insert vehicles.

    ∙ Reported User(s) shall not be held responsible for loss of your car, or standard in-game vehicle; this is due to the current In-game Car Lock System implied, as well as a kill-seat script on specially designed vehicles.

    MIR&R § 305: Spawn Killing (SK) Class D
    ∙ Players may not camp other spawns with the intent to kill or harm other players after they respawn.
    ∙ More specifically LEO's, may not camp another spawn with the intent to arrest said player after they respawn – they started a new life (NLR).

    Subtitle 4: Emergency Services Regulations

    MIR&R § 401: Team-killing (TK) Class D
    ∙ Players may not kill others on their team without any reason or cause.

    MIR&R § 402: Abuse Of Teams (AoT) Class D
    ∙ Players may not use teams to avoid arrest, exploit weaponry or any related-punishment.
    ∙ Nor to purposefully get out of a roleplay scenario without both parties agreeing to void the scenario.

    MIR&R § 403: Abuse Of Radio (AoR) Class D
    ∙ Players with access to the radio may not abuse the radio in any way.
    ∙ Players may not spam panic calls for no reason. Only push the panic button once every 2 minutes.
    ∙ Nor can they text-spam the radio.

    MIR&R § 404: Tool Abuse/Cuff Rushing (TA/CR) Class D
    ∙ Players may not abuse their tools in any way, that includes open-firing or disarming their weapon without cause, that would result in fail-roleplay or make an unfair reason.
    ∙ LEO's may not use their cuffs to arrest individuals repeatedly and unreasonably.
    ∙ LEO's, and those with access to the cuff script, may not arrest a player who is at a considerable range where cuffing in real life would be improbable.
    ∙ Nor can they detain (or grab) a player who is at a considerable range where grabbing them in real life would be improbable.
    ∙ Nor can they rush towards an individual and immediately arrest them. You must roleplay the arrest.

    Subtitle 5: In-Game Experience


    MIR&R § 501: Leave To Avoid Punishment (LTAP) Class B

    ∙ Players may not leave, in other words, attempt to leave the game in order to avoid moderation punishment or to avoid talking with a Moderation Member.
    ∙ Player making hateful comments/conduct.

    MIR&R § 502: Interfering with Staff (IWS) Class A
    ∙ Players may not interfere with any staff member who is attempting to conduct his or her duties.
    ∙ Nor can they interfere with any staff member who is on a staff scene.

    MIR&R § 503: GLitching (GL) Class C
    ∙ Players may not glitch themselves or any item in the game in an attempt to aid themselves in order to have a better advantage.
    ∙ Nor can they glitch into any building or areas of the map where they shouldn't be.

    MIR&R § 504: Staff IMpersonation (SIM) Class C
    ∙ Players may not impersonate any member of the MI Team with the intent to moderate the game, whether it be wearing a Staff Hoodie or anything in that nature.
    ∙ Nor can they pretend they're staff members, regardless of the current situation they're in.
    ∙ Moderation is reserved strictly for Staff Members only.

    MIR&R § 505: Exploiting/Conspiring with Exploiters (EXP / C-EXP) Class C
    ∙ Players may not exploit the game in an attempt to ruin the roleplay experience, to give themselves a better advantage, or to cause chaos.
    ∙ Nor can they conspire with an exploiter (assisting or aiding an exploiter). This includes attempting to conceal their identity.

    Subtitle 6: Individual Trouble


    MIR&R § 601: False Report to Staff (FRS) Class A

    ∙ Players may not make a report about another player with the intent to get the other player in trouble without probable or valid reasoning.

    MIR&R § 602: Personal Information (PI) Class D
    ∙ Players may not leak PI of other players while in-game without their consent.
    ∙ Real-life information includes; addresses, names, ages, and other personal information.
    - All information is to be made up for roleplay purposes.

    MIR&R § 603: Ban Evasion/Alternative Account (BE/AA) Class D
    ∙ Players may not utilize any alternative accounts with the intention to evade their ban.
    ∙ Nor can they utilize any glitch or attempt to bypass SimpleAdmin to bypass their ban.

    MIR&R § 604: Staff Disrespect (SD) Class A
    ∙ Similar to § 111, applied to any active Moderation Members within Mountain Interactive.
    ∙ Intense usage of slurs, or any other forms of discrimination, or harassment implied to Mods.
    ∙ In-cases where the situation gets worse, a Member of the Head Moderation should be notified.

    MIR&R § 605: TRolling (TR) Class C
    ∙ Comes under § 102 & § 105, can also be called as a griever.
    ∙ Players that come under this section show no single interest in playing the designated game, how it’s supposed to be played; for instance NOT roleplaying at all & constantly irritates, or ruins the fun of other Member’s roleplay.

    MIR&R § 606: Administration Discretion (AD)
    ∙ Each violation should be checked on a case-to-case basis. This section can be inquired with any Board, or Corporate Member.
    ∙ This section also includes violations related to Moderation Systems; such as, Violation Of Peacetime & Abuse Of !help Calls. V-PT has anything in correlation with firing a weapon, or any cause of disruption from brandishing a weapon & V-HS is also considered as misuse, or abuse !help to call staff for self-benefit, or random involvement with no apparent reason.

    MIR&R § 607: Violation of Terms Of Service (V-TOS) Class D
    ∙ Violation to our TOS, Community Guidelines, or any other policies for all the services that we currently, or may use in the near future.
    ∙ These terms includes discussions that are indirect, or direct to;
    a. Bomb RP’s, or IRL explosives, or terrorism context.
    b. Promotion of illegal substances, such as use of alcohol, or any other drugs.

    ∙ This section doesn’t require Board Approval & it can be done by any Volunteer Staff.
    Termination across all services REQUIRES approval from Board Members.
    Upvote 0
    Not open for further replies.