1. If you think someone deserves attention for their great work, shoot them a kudos here:
    Kudos Thread If they have done something really unique, consider recommending them for a medal here: Medal Nomination Form
  2. Hey Guest, would be great if you'd chip in here. All support is greatly appreciated!
  3. Become a member of PRTA today, fill out the application form here.

Contact! Rules

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 complaints should be filed in the appropriate discord channel.

Introduction

The following rules and regulations lay out the manner in which the Contact Tournament is run. 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 regard 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.

Section 1 - General Comments

    1. Responsibility
      1. While players are of course individually responsible for their own actions, the chain of command is there to reinforce the rules and act if necessary.
      2. Commanders are responsible for the punishment (with approval from the admins) of individual(s) who break team-wide rules.
      3. The admin team is responsible for any individual(s) who break tournament wide rules.
    2. Acceptance of Regulations
      1. By signing up for the Tournament players agree to abide by the regulations herein.
    3. Alterations to Regulations
      1. The Administration reserves the right to change/alter the regulations as they see fit.
      2. Rules may only be changed or amended mid season if the administrators and team commanders agree.
      3. The administrators reserve the right to give punishments in any category lesser than or equal to the specified one, in light with the severity of the incident.
    4. Appeals
      1. The decisions of the Administration are final. Any complaints must be made in a mature manner and through the Chain of Command. Public arguments, flame fests, trolling and anything which undermines the integrity of the tournament will see appropriate penalties imposed.
      2. If appeals/complaints do not reach the admins in due time you may file a complaint in the report section directly to the admins.

Section 2 - Ethos

    1. Ethos
      1. The Tournament’s ethos is to provide an environment for players to engage in organized, competitive and teamplay-oriented matches that meet high standards of tactical gameplay and are conducted in a spirit of good Sportsmanship and Fair Play.
      2. ‘Sportsmanship and Fair Play’ is understood to mean the following:
        1. Respect for the rules.
        2. Respect for the opponents.
        3. Respect for the administration.
        4. Equal treatment for all players.
      3. Commanders must ensure that their team does not violate the above principles. They should seek the advice of the administration if they are unsure.
      4. Discussions between individual teams and team commanders and the admins are to be kept confidential to avoid any conflicts of interest.
      5. 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 additions or corrections.
      6. The Administration reserves the right to take action against any players deemed to be in violation of the Tournament Ethos.
    2. Punishment
      1. The Administration expects every person involved in the Tournament to uphold these standards. Should any behaviour arise that violates the principles of Sportsmanship and Fair Play, the Administration may issue punishment. Any such punishment must be proportionate and appropriate.

Section 3 - Sign-ups & Clan/Community Restrictions

    1. Team Restrictions
      1. There is no limit on the number of players a Team can have on its roster.
      2. If the difference in team size goes beyond 3 then the team with the greater number of players cannot receive any more applicants until balance is re-established.
    2. Acceptance of Applications
      1. The Administration and Team Commanders reserve the right to reject any applicants at their discretion.
      2. Any user who has been removed from the Tournament due to inactivity can request to be re-added to his/her original team by reapplying. The application will then be considered by the Administration along with the SCO/CO of that Team.
      3. Any user whose signup is rejected by the Tournament Staff can submit a PM to an administrator (1 per Campaign) via the website, to be considered and discussed by the PRTA Staff along with the SCO/CO of each team.
      4. Any user who is banned on the PRTA Forum but wishes to take part in the Tournament can appeal by talking to a PRTA Manager directly. Being unbanned on the PRTA Forums only allows you to make a signup request; it does not automatically mean acceptance.
      5. Any appeal to be allowed to play in a campaign is limited to a Grunt position. Officer positions are not available to players entering the tournament after appeal.
    3. Clan/Community Memberships
      1. Players signing up to the Tournament may not include their Clan Tags in their username. Put this in the designated place on the signup form.
      2. Every player signing up for the Tournament is obliged to mention their Clan or Community Memberships, as requested on the sign-up form. Any sign-up that fails to declare Clan or Community Memberships will be deemed invalid and ignored.
      3. Any player that attempts 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.
      4. Any player that joins a Clan or Community while being part of the Tournament is required to inform their SCO of their new membership. Failure to do so may result in a sanction.
      5. It is strictly prohibited to advertise Clans or Communities and/or attempt to recruit players to Clans or Communities during the Tournament.
      6. Players are allowed to use their Clan Tags in combination with their Team Tags in unofficial, unrelated events such as public server playing. Players should always make sure to remove these tags for any official Tournament events such as battles and training.
    4. Clan Restrictions
      1. Every player that signs up for the Tournament does so as an individual. However, in order to maintain balance between teams and to avoid the majority of a team or squad being controlled by a single Clan or Community, restrictions must be added.
      2. These restrictions apply to each team equally.
        1. Teams are only allowed as many ‘Clan Squads’ as the opposing team has. A ‘Clan Squad’ is a Squad where over 60% of participants belong to the same Clan.
        2. Excluding the ‘Clan Squads’, the remaining Squad rosters may only have a maximum of 60% of players from the same Clan or Community during battle and on the team roster.
    5. Player Preferences
      1. A player can name the team he/she prefers to join. Although this does not guarantee assignment to that team, the Administration will do their best to accommodate preferences.
      2. Once a player is assigned to a team, he/she may not be transferred to another team unless both High Commands and the Administration agree on the trade.
      3. Any sign-up of a player that has previously resigned from one team and is attempting to join the opposite team will be deemed invalid and ignored.
      4. If a sign-up is made with a different forum account and the player does not declare this, it will be deemed invalid and ignored and the player may face sanction.
    6. Reserve Activity
      1. It is the responsibility of Team High Commands to ensure the following is enforced:
        1. Every Reserve is required to attend 1 team event (training or battle) per month.
        2. Every Reserve is required to be on TeamSpeak while participating in Tournament events.
        3. Every reserve is required to be on the discord and check it once a week.
        4. All reserves must complete the signup procedures.
      2. The Administration reserves the right to remove reserves whose activity falls below the expected level.
    7. Grunt Activity
      1. It is the responsibility of Team High Commands to ensure the following is enforced:
        1. Every Grunt is required to attend 1 team event (training or battle) per month.
        2. Every Grunt is required to be on TeamSpeak while participating in Tournament events.
        3. Every Grunt is required to be on the teams discord and check it twice a week.
        4. All grunts must complete the signup procedures.
      2. The Administration reserves the right to remove Grunts whose activity falls below the expected level.
    8. Leave of Absence (LOA) Guidelines
      1. Each team must have an LOA Channel in their team Discord where written LOAs must be posted.
      2. Squad Leaders may post an LOA for one of their Grunts if he/she is unable to do so.
      3. The maximum duration for an LOA is 1 month. Any further length must be discussed with the Administration and will only be permitted in exceptional circumstances.
      4. Players who do not properly file an LOA may be removed after failing regular activity requirements.
      5. It is the responsibility of Team High Commands to monitor and regulate Team LOAs.

Section 4 - Communications

    1. In-Game Chat
      1. The use of All-Chat is not allowed for any reason except by SCO/COs and Admins for running the match. Anyone who breaks this rule will be punished. 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.
    2. Microphone
      1. All players are required to have and use a microphone.
      2. All players must be able to speak and understand english in order to participate in the tournament.
    3. TeamSpeak
      1. All players must use the PRTA TeamSpeak for Tournament-related activities which include battles and trainings.
      2. All participating players are required to be on the appropriate Tournament channels in the PRTA TeamSpeak during a battle. Failure to do so will prevent participation in the battle.
      3. All players must use the same nickname on TeamSpeak that they use in-game.
    4. Mumble
      1. In-game Mumble remains the primary means of communication during a battle. However, TeamSpeak remains mandatory as the primary means of communication between participants the Administration.
    5. Meetings
      1. A clear agenda must be prepared in advance of any scheduled meeting.
      2. Commanding Officers must liaise with each other and the Administration via TeamSpeak both before and after each Battle.
      3. Decisions made and actions to be carried out must be recorded in the forums before the end of each meeting.
    6. External Communications
      1. The primary tool for Team management and battle planning will be the Team Discord. Other tools such as the PRTA Forums can also be used to coordinate team issues.

Section 5 - Conduct

    1. Cheating
      1. Anyone cheating will be banned from the tournament, teamspeak, and 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. If there are questions about what is and what isn’t considered a bug/exploit, the Team Commanders should ask a Tournament Admin and refrain from using them until a decision is made.
      3. Failure to report other players that you know are breaching rules is also considered a violation of Tournament rules and will be severely punished.
    2. Language and Profanity
      1. PRTA’s Discord Rules and Forum Rules must be followed at all times.
      2. The Administration reserves the right to take action against any players deemed to have broken PRTA’s Discord Rules and Forum Rules.
    3. Fair Play
      1. All players are expected to uphold the values of Sportsmanship and Fair Play in line with the Tournament Ethos. Actions that break, manipulate, bypass or otherwise avoid Tournament rules will be met with Administrative action.
    4. Kits
      1. Kit restrictions are meant to be upheld, kits will be limited to the team not the squads. You may not use more than one of the spawn kits per squad at a time (exception being medics and rifleman) . You may pick up another kit and use it, however you may not spawn in with the intention to pull multiple spawn menu kits.
    5. Forfeits
      1. Teams that are unable to present the required number of players and refuse to play will lose the battle.
      2. Upon a team forfeiting, they will give the opposing team 12 points and receive 0 points for that battle.

Section 6 - Prohibited Actions

    1. The Administration delegates authority to Team High Commands to enforce discipline within their own team. Team High Commands may take action against members of their team as they see fit. Any serious breaches must be reported to the Administration.
    2. Teamkilling
      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. Editing Client Files
      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 with a reserve taking your spot.
      2. Alteration of client files is considered cheating and a breach of Tournament Ethos (editing maps for practice is allowed as long as it follows the PR Server Agreement).
    4. Suicide Tactics and Deliberate Asset Destruction
      1. Nobody may use any suicide tactics at any point. Any instances of suicide which abuses this rule or the ticket system will be punished.
      2. The deliberate destruction of the team's own assets is forbidden unless ordered by an Officer and/or approved by the Commander.
      3. If any of the above rules are broken, both the team and the specific individual(s) may be penalized.
    5. Live streaming and recording
      1. Live streaming is forbidden under any and all circumstances.
      2. Recordings of entire matches may be posted only after the campaign has concluded.
        1. Funny moments or highlights of matches may be posted with approval of the Team High Command.
    6. Flag rushing
      1. Do not rush unless one of the rushing exceptions is in place.
      2. Rushing is defined as any of the following happening before 10 minutes have passed:
        1. Attacking anyone inside the radius of the enemy's first cappable flag.
        2. Entering the radius of the enemy's first cappable flag.
        3. Stopping the enemy from entering the radius of the enemy's first cappable flag.
        4. Intercepting the enemy between any of their spawn points and their first cappable flag.
      3. Rushing exceptions are defined as follows:
        1. The flag can be capped (i.e. it has an attack marker on it).
        2. There are only 2 neutral flags in the beginning on this map, layer and layout.
        3. Your team has paradrop spawns in the beginning on this map, layer and layout
    7. Base Protection
      1. Dome of Death is defined by either the lines drawn on the map surrounding the mainbase or the areas where a warning message is automatically given to a team upon entering it.
      2. Do not attack, place mines within, fire into or out of the Dome of Death.
      3. Stay out of the opposing team's Dome of Death unless you are engaged in a jet on jet dogfight.
      4. Do not initiate a dogfight if the opposing jet is inside his own Dome of Death.

Section 7 - Battle Cycle

    1. Procedures
      1. Each battle-cycle begins on Sunday and runs for two weeks. The first weekend is reserved for a team training activity and the second Saturday at 18:00 UTC is the battle day.
      2. The next map to be played will be chosen the day of the battle to prevent teams from tanking to get a better faction in the next battle.
      3. Factions are decided by the loser of the previous battle. The deadline for decision is the Sunday after the previous battle (i.e. the next day) at 19:00 UTC, and the choice must be submitted to the admins. If a team fails to choose a faction in time the factions may be chosen by the other team.

Section 8 - Pre-Battle

    1. 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.
      2. At the battle start time, the map will be reloaded and the battle will be live. This will be announced by the Administration.
    2. Joining the Server
      1. Permission must be given by an officer on teamspeak prior to joining the server.
      2. Players are required to use their team tag account whenever joining a tournament server.
      3. If a player joins the server without following the above rules they will receive a warning followed by a kick if they have not complied.
    3. Conduct
      1. Players are only allowed to spawn after receiving permission from the SCO or CO.
      2. Players are not allowed to leave their main base until the official start of the battle.
    4. 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.
    5. Team Numbers
      1. Teams are expected to field minimum 40 players and maximum 49 players.
        1. If the minimum number cannot be upheld, the Team’s CO will be given the option to forfeit or to play with what they have.
        2. Forfeiting may only happen before a battle has commenced.
        3. If the maximum 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 players kicked until the numbers are corrected. Please be patient and allow time for the admins and commanders to sort this out.
      2. Teams are allowed to replace players mid-battle as long as the active Admin is informed on TeamSpeak.

Section 9 - During the Battle

    1. Rounds
      1. The server will run 1 live round of the map that had been previously decided and announced by the administration.
    2. Battle Restarts
      1. If a battle crashes less than an hour in it is replayed within the same day.
        1. If a team cannot produce the required numbers as mentioned in section 8.V.1 they have the option to forfeit or play with that they have.
      2. If a battle crashes more than an hour in, then:
        1. If one team has at least a 150 ticket lead they are awarded the win. They will receive the amount of points for the flags controlled, in addition to the points for tickets remaining.
        2. If no team has a substantial lead, the battle will be rescheduled.
        3. If the battle server is attacked we will talk with the team commanders and execute our pre planned contingency procedure.
    3. Squads
      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 Command.
    4. Tags
      1. During battle all players must have their correct tags and nicknames for Teamspeak and in-game. Tags are to be as follows; C|XXX Username
      2. Players with incorrect tags will be warned and kicked if not compliant.
    5. Building Assets
      1. Mortars cannot be built in a location where the fired shells will pass through buildings, textures (except forests) or any other static objects on the map.
      2. Mortars may not be destroyed and be rebuilt in order to bypass rearming them.
      3. FOBs 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.
        2. The FOB must not spawn players into a non-enterable building and must be visible.
        3. Razor-wire and sandbags may be used to block access points.
    6. Admin Support
      1. Admins will be available on TeamSpeak for any serious issues that may need immediate action.
      2. Admins are only to be contacted by the Supreme Commander or the In-Game Commander.
      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 for the duration of the battle.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice