PRT Rules & Regulations

[[R-ADM]Onil]

ALL Officers are to enforce these rules in their own Teams.
By signing up for this Tournament, you are accepting and agreeing to abide by the following rules.
Any direct complaints should be posted in the Admin Support forum.

Introduction

The following rules and regulations lay out the manner in which the Project Reality Tournament (the Tournament) is run. Tournament staff (Administrators) will be guided by them when dealing with members of all teams (Players) and their leaders (Officers). In turn, Players and Officers have a duty to ensure that their actions are not in breach of these rules at all times. Due to the nature of all competitive events, these rules cannot cover every eventuality. Where events occur that fall outside of specifically identified rules, Administrators will act as they see fit to apply the spirit of them, in line with the Tournament Ethos. The rules themselves should not be considered absolute on what is allowed and what is not, but a guide as to the purpose and direction of the Tournament as a whole. Players should not seek to justify their own actions with regards to the rules but self-regulate as a community. Ultimately, the rules exist to maintain the ability for all involved to enjoy the tournament; not to penalize individuals or teams for no cause.

- The Project Reality Tournament Administration, September 2015

Table of Contents

1. General Comments
2. Ethos
3. Sign-ups & Clan/Community Restrictions
4. Communications
5. Conduct
6. Prohibited Actions
7. Battle-Cycle Definition
8. Pre-Battle
9. During the Battle

9.7. Control Point Attack Protocols
9.8. No-Go Zones
9.9. Building Assets

10. Post-Battle
11. Private Messages
12. Punishment Tables

-------------------------------------------------------------------


Section 1 - General Comments

I - Responsibility

1. While players are of course individually responsible for their own actions, SCOs, COs, 2iCs, HCOs and SLs are personally responsible for ensuring players under their command are aware of and abide by the following regulations.

II - Acceptance of Regulations

1. By signing up for the Tournament, players agree to abide by the regulations herein.

III - Alterations to Regulations

1. The Administration reserves the right to change/alter the regulations as they see fit.
2. To be determined by the severity of the incident, the administrators reserve the right to give punishments in any category lesser than or equal to the specified one.

IV - Administration

1. The Administrators’ and Managers’ decisions are to be seen as final. While you may protest, all protests must be made in a mature manner, and through appropriate channels. Failure to behave appropriately when protesting such a decision may see the protest being ignored or the offender penalized.
2. Issues should be raised via the Chain of Command. While the Tournament Staff encourages discussion, public arguments, flame fests, trolling and similar will see appropriate penalties imposed. (Forum AWS or other warning as appropriate.)

V - Protests and Queries

1. These should be raised via the Admin Support forum, and not raised individually with Administrators via the Private Message system.
2. Matters that require immediate/rapid attention should be flagged with the appropriate prefix.
3. Administrators will not become involved with complaints/protests/queries over private messages.
4. The Admin Support forum will serve as a viable means of submitting complaints. If you wish to submit a complaint (against an administrator only) private, PM one of the Management Staff.

VI - Forum Signatures

1. The total size of signatures are no bigger than 200px by 500px.
2. Campaign ribbons (featuring the Roman numerals such as VI, X, XII, etc.) may not be displayed in the signature. Missing ribbons under a player's avatar must be brought up with administration.

Section 2 - Ethos

I - Ethos

1. The Tournament’s ethos is to provide an environment for players to engage in organized, teamplay-orientated matches that meet high standards of realistic tactical game-play and are hosted in a spirit of good sportsmanship and fair play.
2. The ethos is upheld by the rules and regulations set forth by the Administration. All players are expected to follow these rules and any new published addenda. The Administration makes all decisions based on this Ethos.

II - Punishment

1. The administrators expect every member of this community to uphold these standards. As such, should a bad sportsmanlike or unfair action be performed by a team or by a member, punishments may be given based on a “Breach of Tournament Ethos.”
2. This breach will constitute a specified Category of infraction. (Section 12)
   1. Where the breach impacts the individual. (Category 1)
   2. Where the breach impacts an inter-team group of players. (Category 2)
   3. Where the breach impacts a team. (Category 3)
   4. Where the breach impacts a match. (Category 4/5)
   5. Where the breach impacts the entire tournament. (Category 6)

Section 3 - Sign-ups & Clan/Community Restrictions

I - Acceptance of Applications

1. The Tournament Staff along with the Team Commanders reserve the right to reject any applicants they believe will engage in activities detrimental to the Tournament or in breach of the Tournament Ethos.
2. Any user who has been kicked, due to inactivity, can request to be re-added to his team (not the opposite team) by submitting such request via support ticket. The request will then be considered by the PRT Staff along with his SCO/CO.
3. Any user whose signup is rejected, by the PRT Staff, can submit an Appeal (One per Campaign Only!) via support ticket, to be considered and discussed by the PRT Staff along with the SCO/CO of each team.
4. Any user who is banned on the main PR Forum will automatically have his signup rejected. He can submit an Appeal to one of the Moderators at the PR Forum to be un-banned. Being un-banned on the PR forum does not automatically mean that his signup will be accepted on the PRT, that requires a different appeal to be made and discussed by the PRT Staff.
5. Any user who is banned on the PRT Forum can submit an Appeal via PM to the PRT Management on the main PR forum. Being un-banned on the PRT forum does not automatically mean that his signup will be accepted, that requires a different appeal to be made and discussed by the PRT Staff.
6. Any Appeal to be allowed to play in a campaign is limited to a grunt position. No user will be accepted to return and take an officer position, in that specific campaign, after his appeal.

II - Clan/Community Memberships (Category 1 or 2)

1. Players signing up to the PRT may not include their Clan Tags in their username. Inclusion of Clan Tags in a forum username will lead to changing of the username by the Administration with the possibility of further infractions.
   
2. Players joining the official PRT Teamspeak Server are not allowed to include any Community or Clan Tags in their username. Inclusion of Clan Tags on the Team Speak Server will lead to kick or ban if this rule is repeatedly broken.
   
3. Every player signing up for the PRT is obligated to mention their Clan or Community Memberships (even if only a recruit) on their sign-up form, as requested. Any sign-up that does not contain such existing information will be invalid and ignored.
   
4. Any player that purposely tries to conceal their Clan or Community membership may be removed from the tournament. The administration reserves the right to increase the restrictions for that Clan or Community following any violations.
   
5. Any player that joins a Clan or Community while being part of the PRT, is required to inform their Supreme Commander and the Administration (via support ticket) of their new membership. Failure to do so may result in the player being removed from the Tournament.
   
6. It is strictly prohibited to actively advertise Clans or Communities and/or recruit players to Clans or Communities during a PRT Campaign. This includes the use of Clan Tags on any information posted on the PRT forum as well as in any player signature. You may do so only after the Campaign has ended and only if you refrain from using the PRT forums for it.
   
7. Players are allowed to use their Clan Tags in combination with their PRT Team tags in non-PRT related events, including public server play. Players should always make sure to remove these tags for any official PRT battles, trainings, etc.

III - Clan/Community Restrictions

1. Every player that signs up for the PRT, does so as an individual player. However, in order to increase the balance between the teams and to avoid the majority of a team or squad to be controlled by one single clan or community, restrictions must be added. These restrictions apply to each team separately.
   
   No more than 40% of a team's or group's total number of players can be members of the same Clan or Community. Members from the same Clan or Community can be on opposite teams. Players who left their clan within a period of a month or less before sign-ups still count as a member of that clan.
   
   It is advised that all Clans, Communities or Groups, organize themselves according to these rules, before their members sign-up. (Category 3 or 4)

1. Squads may only have a maximum of 50% of players from the same Clan or Community.
   
2. In-Game Squads are allowed to have a maximum of 50% of their players from the same Clan or Community, rounded up. For example, a 7 man squad can have 50%(3.5 players, rounded up to 4) and a 5 man squad can have 50%(2,5 players rounded up to 3) from the same clan or community.(Category 4)
   
3. Only 40% of the team's Squad Leaders can be from the same Clan or Community. This will be dependent on how the SCO/CO structures their team.
   
4. There can only be a maximum of 2 members of the same Clan or Community in a Team's Staff (SCO/CO + 1 Staff member or a max of 2 HCO's).

IV – Player Preferences

1. A player can name two other players that he would like to play with. However, those two players cannot name any other players or that preference will be invalid and ignored.
   
   X signs-up with Y and Z
   Y signs-up with X and Z
   Z signs-up with X and Y
   
   Officers should name two players they would like to have included into their squad. Those players should then name each-other besides their SL on their sign-ups. If you want to stick together in the same Team (Assigned by the Administration) and possibly in the same Squad (Assigned by the SCO) you should make sure that you and your friends are all aware of this rule and will follow it on the sign-up form. This however does not guaranty that you will be placed in the same squad as that is dependent on multiple factors.
   
2. A player can name the team he prefers to join and that preference will be taken into account when the administration is assigning him to a team. This however does not guarantee him to be added to said team.
   
3. Once a player is assigned to a team, he may not be transferred to the other team until the end of the campaign.
   
4. Any sign-up of a player that has previously resigned from one team and is attempting to join the opposite team in the same campaign, will be invalid and ignored. If the sign-up is made with a different account and the player does not mention their previous PRT account/s, it will be considered a breach of the tournament rules and may result in the player being banned from the tournament.

V – PRT Team Member Activity

1. Every Team Member is required to Sign-In/Out for all Squad/Team Trainings and Battles
   
2. Every Team Member is required to attend at least 1 Squad/Team training per battle-cycle (exceptions can be made if proper excuses are given).
   
3. Every Team Member is required to attend at least 1 Battle per 2 Battle-cycles. Supervised by the SCO's and their Officers.
   
4. Every Team Member is required to check the PRT forum at least 2 days per week (exceptions made for LOA's). Supervised by the SCO's and the Administration
   
5. Players lack of activity may result in their removal from the team.

VI – PRT Team Reserve Activity

1. Every Team Reserve is required to attend at least 1 Squad/Team training per 2 battle-cycles (exceptions can be made if proper excuses are given). Supervised by the SCO's and their Officers.
   
2. Every Team Reserve is required to check the PRT forum at least once per week (exceptions made for LOA's). Supervised by the SCO's and the Administration.
   
3. Players lack of activity may result in their removal from the team.

VII – Leave of Absence (LOA) Guidelines

1. LOAs must be processed through the Roster Page. Written or verbal LOAs through the forum, Teamspeak, etc. are unacceptable except in exceptional circumstance.
   
2. The maximum duration for an LOA is one month. Any further length must be discussed with administration and will only be permitted in exceptional circumstance.
   
3. Players who do not properly file an LOA may be removed after failing regular activity requirements.

Section 4 - Communications

I - In-Game Chat (Category 1)

1. The use of All-Chat is not allowed for any reason except by SCO/COs and Admins for running the match. Forum warning will be given to anyone who breaks this rule. Don't complain - unbind the key before the match!
2. The team-chat is only to be used for information that is important to the whole team. It is up to the officers to make sure that everyone only uses it when necessary or to set up rules that specify the use of team chat during a match.

II - Microphone (Category 1)

1. All players are required to have and use a microphone.

III - Teamspeak (Category 1)

1. All players must use the Official PRT Teamspeak on PRT-related activities.
2. All players must be on Teamspeak to play the match. If they aren't on TS after the SCO/Admin asks or warns them, they will not be allowed to play. No Teamspeak, no game.
3. All players must use the same nickname on Teamspeak that they use in-game.

IV - Mumble

1. In-game Mumble may, of course, be used as the primary means of communication during the battle. However, Teamspeak will continue to be mandatory as it is the primary means of communication between the teams and the admins.

V - Meetings

1. Commanding Officers must liaise with each other and the Battle Administrators using Teamspeak both before and after each battle.

VI - External Communications (Category 3)

1. The primary forum for team management and battleplanning are the http://tournament.realitymod.com/ forums. While other outlets like Steam or Discord can be used to coordinate team issues, all significant decisions, team events, sign-ins, and roster management must occurr or be posted on the Tournament Forums.

Section 5 - Conduct

I - Cheating (Category 4/5 or 6)

1. Anyone Cheating will be banned from the Tournament Forums and the Project Reality Forums and their information will be passed to all Project Reality server administrators for a general ban. You will no longer be able to play Project Reality if you use cheats.
2. Exploiting either known or unpublished/unknown bugs will not be tolerated and will count as cheating. The PRT exists in order to provide a honest and realistic game, bugs/exploits are not in the interest of that and of the mod as a whole. If there are questions about what is and what isn’t considered a bug/exploit, the Team Commanders should ask a Tournament Admin.
3. Anyone not reporting other players that are breaching these rules, are considered accomplices and may also be severely punished.

II - Language and Profanity (Category 1 or 2)

1. Profane / racist / disrespectful / offensive language on the forums or in-game will be regarded as a breach of forum rules, team discipline and Tournament ethos.
2. Remarks not clearly breaching 5-II-1 but that the Administrators deem to violate the ethos of the Tournament may also be penalized.

III - Fair Play

1. Players are expected to demonstrate a sense of ‘fair play’ in line with Tournament Ethos as well as all posted Tournament and team rules.
2. Actions that are deliberately undertaken to manipulate, bypass, or avoid Tournament rules may be considered as cheating and/or a gross breach of the Tournament Ethos. (2-II)

IV - Use of Tournament Tags on Public Servers (Category 2)

1. Current players may wear their Tournament tags in public servers on condition they uphold the Tournament ethos, and may be penalized within the Tournament for bringing the Tournament into disrepute.

   1. Entire Teams are not encouraged to play on a server with their tags, as some server admins complain that it scares away players. If expected to have a big turnout, use of normal (non tourney) tags is strongly suggested, but will not be penalized should this be the complaint. It is also highly advisable for tournament players to avoid increasing the unbalance of the teams in public servers. They should give the example of fair play and contribute to team balance.

2. Retired players who have been honorably discharged may retain their tags for public play on the same conditions as active players. Bringing the Tournament into disrepute will cause the Tournament administration to petition servers to implement a ban on the offending player’s tagged name.
3. Dishonorably discharged players are not permitted to use Tournament tags. Failure to remove tags will cause the Tournament administration to petition servers to implement a ban on the offending player’s tagged name.

V - Forfeits

1. Teams that are unable to present the required number of players (8-V) will lose the battle.
2. For teams that refuse to play a match, the team will lose the said battle.

Section 6 - Prohibited Actions

I - Teamkilling (Category 1 & 5)

1. Intentional team-killing will not be tolerated. This includes before, during and after the battle.
2. Players who team-kill risk being kicked from the server. Team Commanders are given the right to request the removal of players from the server for team-killing.
3. Any punishments post-battle need to be team side and will, of course, be backed by the Admins.

II - Editing Client Files (Category 6)

1. No client files may be edited while taking part in the Tournament. If you or others are kicked for editing files, the battle will continue.
2. Alteration of client files is considered cheating and a breach of Tournament Ethos. (Editing maps for practices is allowed as long as it follows the PR server agreement.)

III - Suicide Tactics and Deliberate Asset Destruction (Category 4 or 5)

1. No teams may use any suicide tactics at any point, with the exception of unconventional (including Militia & FSA) forces who may use any explosive device to kill themselves while also attempting to or inflicting harm on opposing players. Any instances of suicide which abuses this rule or the ticket system, will be punished as an Ethos violation.
2. The deliberate destruction of the team's own assets is not allowed unless if ordered by an Officer and/or approved by the Commander.
3. Civilians are not allowed to use suicide tactics (Intentionally running in front of enemy fire or into an area being hit by enemy mortars) to reduce enemy intel points or increase enemy spawn delay.
4. If any of the above rules are broken, both the team and the specific individuals may be penalized.

IV - Livestreaming (Category 4)

1. It is not allowed to live-stream (with or without delay) any campaign battles. This includes publishing video, audio, or any other in-game content publicly until after the battle has finished. Any release of such content post-battle is at the discretion of the team command staff.

Section 7 - Battle Cycle

I - Procedures

1. Each battle-cycle begins on Monday and runs for two weeks. The first weekend is reserved for team training and the second Saturday is the battle day.
2. The map for the battle is decided by the operation in effect. If an operation has been completed, then the next operation will be chosen by the staff of the team which did not choose the previous operation. The deadline for decision is the Sunday after the previous battle (i.e. the next day) at 19:00PRT, and the choice must be submitted in the appropriate thread in the Joint Officers' Mess.
3. The opposing team then has 24 hours (i.e. until 19:00PRT on Monday) to choose the map they wish to ban from the list of maps of the chosen operation. They can also choose not to ban a map if they wish to allow the other team to have more maps to choose from. Besides the option to ban a map, they should also choose a map to be played in said operation. Such decisions should be posted on the same thread in the Joint Officers' Mess.
4. The team who chose the Operation will then also choose a map to be played, and decide which map gets played first. This decision should be made already even before the opposing team chose their map, by listing the maps by preference and updating said list once they're informed of which map got banned and which map got chosen by the opposing team. This is to make the whole process faster. They should post their decision until 24h:00PRT on that same Monday.
   

   1. If a team does not inform the Admins of their choice before the deadline has passed, the Admins will decide which Operation or map will be played.
   2. Once the Operation and map have been decided and announced, they cannot be changed.

Section 8 - Pre-Battle

I - Pre-Battle Procedure

1. The server information will be released 45 minutes prior to the battle start time. Players should start joining the server 15 minutes before the battle starts. At this time the rules of Section 5 comes in to effect.
2. At the battle start time, the map will be reloaded and the battle will be live.

II - Joining the Server (Category 1)

1. Permission must be given by an officer on teamspeak prior to joining the server.
2. Players are required to use their PRT team tag account whenever joining a PRT server.
3. If a player joins the server without following the above rules, he will receive a warning, followed by a kick (if the player has not complied).

III - Conduct (Category 1)

1. All players on joining the server must not team-kill and must not use in-game all chat, as per the rules. Violators will be warned on the server and kicked if it persists.
2. Players are only allowed to spawn after receiving permission from the SCO or CO.
3. Players are not allowed to leave their main base until the official start of the battle.

IV - Start of the Battle

1. The round is live when the Battle Administrator states it is, with a “Live Live Live” message.

   1. Administrators are not responsible for those who do not pay attention to the message or may be away from the computer.

2. There is a 3 minute countdown at the beginning of the match for Commanders to report problems or possible issues to the admins.

V - Team Numbers

1. The minimum amount of in-game players is 32.

   1. If a team cannot produce the numbers within 15 minutes after start time, the Administrators will conclude that that team will lose that battle by default.

2. Each team can have a maximum of 48 players in-game.

   1. If this number is exceeded, the team CO's will be informed to reduce it within the next 5 minutes. If that time has passed and the number is still exceeded, the team will have some of its players kicked until the numbers are corrected.

3. Teams are allowed to replace players mid-battle as long as the Battleday Admin is informed on Teamspeak.

Section 9 - During the Battle

I - Chat (Category 1)

1. During battles, all chat is not to be used by anyone except the Commanders and Administrators for running the match. Violators will be warned on the server and kicked if it persists.

II - Rounds

1. The server will run 1 live round of the map that had been previously decided and announced by the administration.

III - Restarts Prior to 90 Minutes of Play

1. During a battle if a server crashes or needs restarting before 1 hour and 30 minutes into the battle, that round becomes void and is re-played no matter what the score was. (On the match day.)
2. Scoring will then commence fresh once the round has restarted.

IV - Restarts After 90 Minutes of Play

1. If a server fails more than one hour and thirty minutes into the round, the score is taken as is and victory is given to the team with the highest amount of tickets.
2. If the difference is less than 50 tickets, the round is considered a draw and no points will be awarded to either team.

V - Squads (Category 1)

1. All soldiers are to be in a squad at all times.
2. Players may move freely between squads at the discretion of the team commander.

VI - Tags (Category 1)

1. During battle all players must have their correct tags and nicknames for Teamspeak and in-game.
2. Players with incorrect tags will be warned and kicked if not compliant.
3. Players not tagged will be kicked.

VII - Control Point Attack Protocols (Category 4 or 5)

1. Type 1 CP's (Uncappable main-bases and protected main-base areas - Purple.)

   1. No access is permitted by any opposing team members.
   2. Firing in to or out of a Type 1 CP is forbidden. This includes mortars.

2. Type 2 CP's (Cappable main-bases – Purple and Green.)

   1. A Type 2 CP is divided into two distinct areas: Player/Asset spawn points (Purple) and the remaining area of the main base (Green).
   2. Any main-base with a cappable flag will be considered a Type 1 CP until the flag becomes cappable for the opposing team. Once that happens, the Purple areas will continue to be protected by the rules of a Type 1 CP, while the Green areas become a Type 3 CP.

3. Type 3 CP's (Flags that are within the AAS sequence, whether you can cap them at that time or not.)

   1. Both teams are allowed to move in and fire to or from a Type 3 CP (following the exception of a Type 4 CP).
   2. Both teams are allowed to build their assets inside a Type 3 CP.

4. Type 4 CP's (First Cappable Flags in the AAS sequence on Round Start - Until they have been captured or while uncapped for the first 10 minutes of the round):

   1. It is not allowed to fire into and/or from a Type 4 CP with any deployable weapon, including mortars, any type of vehicle or any type of heavy handheld weapon (AA's and AT's) until the Type 4 CP has been captured or within the first 10 minutes of the round if uncapped. Smallarms, including grenadiers, are allowed to fire into and/or from the flag radius.
   2. It is Not allowed to rush and deny the capture of the enemy's first flag by entering its radius until the Type 4 CP has been captured or within the first 10 minutes of the round if uncapped.
   3. Once a Type 4 CP is captured, or 10 minutes have passed and the flag remains uncapped, or if the flag becomes active in the cap order, these rules cease to exist and the flag becomes a Type 3 CP.

VIII - No-Go Zones (Category 3 & 4)

1. Mapper placed DoD's (Dome of Death) are areas in which both teams are allowed to fire from and/or into but are not allowed to build in.

   1. Blue DoD lines represent an area that the Opfor team cannot enter, except when in air vehicles flying by.
   2. Black/White DoDs represent an area that both teams cannot enter, except when in air vehicles flying by. These are usually on the edge of the map.
   3. Red DoD lines represent an area that the Blufor team cannot enter, except when in air vehicles flying by.

2. Admin Placed NGZ's (No-Go Zones) are areas in which spawn-points and team assets are protected.

   1. Purple NGZ represents a main-base and/or other safe zones in which firing is not allowed, either from or in to. That includes mortar splashes, so be extremely careful when firing into the vicinity of such areas. (Category 4)
   2. Green NGZ represents a staging area that ensures safer outside perimeters around a main-base or other safe zones. This means that both teams are not allowed to fire from or into this area, as well as build any assets within it. It is also a No-Go-Zone for the opposing team which is not allowed to enter it even if there is no DoD.
      
      Any Engagement that starts outside of a Green NGZ can continue even if some of the soldiers or vehicles of one of the teams move inside a Green NGZ. That means that the opposite team can fire into the Green NGZ at those targets until the engagement is over. That team still can't enter the Green NGZ though.
      
      This NGZ can however be temporary when connected to a Type 2 or Type 3 CP, meaning that it ceases to exist if such flag becomes cappable. In this case, all above rules are suspended until the flag becomes uncappable. If the flag is no longer cappable (before being neutral and while not being capped) all enemy in the area will have 2 minutes to cease fire and 10 minutes to leave the area. All built assets will also have to be destroyed during that time.
      
   3. Blue NGZ lines represent an area that the Opfor team cannot enter (but can fire into) except when in air vehicles flying by. These are extensions made to the original Blue Line DOD.
   4. Red NGZ lines represent an area that the Blufor team cannot enter (but can fire into) except when in air vehicles flying by. These are extensions made to the original Red Line DOD.
   5. Green NGZ lines represent an area that one of the teams cannot enter (but can fire into) except when in air vehicles flying by. This is a temporary No-Go-Zone connected to a flag and it will cease to exist once the flag becomes capable. These are extensions made around a Green NGZ area.

IX - Building Assets (Category 3 & 4)

• Mortars must not be built in a location where the fired shells will pass through buildings, textures, or any other static objects on the map.

  1. Exception: Mortars may be built in a forest, as long as the foliage is not too thick. Within reason, the mortar round must be fired without impacting a tree.

• FOBs or Hide-outs may be built indoors as long as they do not completely impede access to the building or room in which they are placed.

  1. No part of a FOB (except the dirt skirt) can be 'glitched' inside a part of a non-enterable building or static. The FOB must not spawn players into a non-enterable building.
  2. Razor-wire and sandbags can be used to block access points.

X - Admin Support

1. Admins will be available on Teamspeak for any serious issues that may need immediate action.

   1. They are only to be contacted by the Supreme Commander or the In-Game Commander.
   2. The admins are not in game, they are, however, watching through PRISM but and cannot supervise everything that happens. That is why most of the complaints will need to be made Post-battle. Make sure the issue can be solved by the available admin at the time of the battle, before you contact him.
   3. Requests to kick a player from the server will have to be well-based. The player in question will have to be warned first to give him the possibility to change their attitude or action. If the player has not complied, he will then be removed from the server and not allowed to return.

Section 10 - Post-Battle

I - Battle Results Release and Battle Review

1. There will be no official announcement of the winner of the battle until the Monday after the battle. (Later if complaint review is necessary).
2. Battle Recorder / PRISM recording in conjunction with screen-shots and chat logs, are what the Administrators use to determine the validity of complaints and to issue penalties.

II - Battle Related Complaints

1. Battle-related complaints must be sent no more than 24 hours after the start of the match (not all the data to back it up, just the complaint itself).
2. All complaints must be filed through the Admin Support forum ticket system and should be flagged [COMPLAINT].
3. The only person eligible to lodge an appeal ticket is the Supreme Commander or the In-Game Commander of the respective team.
4. Approximate times of violations must be kept. Any relevant screen-shots or videos (scores, times, etc) should be included in the thread for comparison with Battle Recorder.
5. Teams should know that any complaint that is not valid could result in penalties being placed on the team that reported the complaint.
6. Any complaints not raised in accordance with this section will be ignored.

Section 11 - Private Messages

1. The PRT Management reserves the right to view individuals' PMs if there is a reason deemed serious enough to be a valid threat to the PRT. If this is necessary the user(s) will be notified.
2. Private message usage follows the forum rules and any abuse of this system may see messaging privileges removed without prior notification and a separate AWS warning relating to the type of abuse.
3. Users should never contact an Admin via PM unless if in response to a PM sent by an Admin. Any issues should always be posted as a Support Ticket for all Admins to have access to. If the issue is with an Admin, a PM may be sent to the Lead Management.

Section 12 – Punishment Tables

Category 1 - Where the breach impacts the individual:

User: 1-3 Point Infraction.
Team: N/A.

Category 2 - Where the breach impacts an inter-team group of players:

User: 2-4 Point Infraction, removal from next battle cycle.
Team: Possible loss of up to 25% of the points won in this battle

Category 3 - Where the breach impacts a team:

User: 3-5 Point Infraction, removal from next battle cycle.
Team: Possible loss of up to 50% of the points won in this battle

Category 4 - Where the breach impacts a match:

User: 4-6 Point Infraction, removal from next battle cycle.
Team: Possible loss of up to 100% of the points won in this battle

Category 5 - Where the breach impacts a match:

User: Ban (3 day), removal from next battle cycle.
Team:Possible loss of up to 100% of the points won in this battle

Category 6 - Where the breach impacts the entire tournament:

User: Ban (Permanent).
Team: N/A.
Other: Any other involved users may receive infraction points or temporary bans.