Menu

COD: Black Ops 3 Regler

Sidst opdateret: 16. December 2015 – 23:35

1 General
2 Competition Guidelines
3 Game Specific Settings
4 Match Specific
5 Host
6 Reporting
7 Team Guidelines
8 Conduct
9 Prizes
10 Admin/Staff
11: Miscellaneous


1 General

1.1 These rules are subject to change at any time before the registration deadline, so check them often. In extremely rare cases, rules may be altered after the competition has started.

1.2 Teams are allowed to utilise Party Chat during matches.

1.3 Users are prohibited from sharing account information. This includes, but is not limited to the following: usernames, passwords, gamertags, email accounts, etc. If another person accesses your account, you may be disqualified from the competition. This includes giving out your password to allow others to account recover your Playstation.

1.4 It is the responsibility of the player to ensure the Gamertag they use, matches the Gamertag listed when they apply.

1.5 If a team has already registered and a players Gamertag is incorrect, the player who wishes to change their Gamertag must, themselves, contact an admin prior to the official registration end time of the competition stating their new Gamertag.

1.6 In order to be eligible for the award, all teams must play their matches in its entirety. If either team withdraw from the competition at any time in the run up to the final, they waive all rights to any prize claims.

1.7 Users are allowed to compete in more than one tournament at a time, unless as this may delay the tournament. If delays do take place as a direct result of users taking part in other tournaments, the delaying team may be disqualified from the competition.

1.8 Participation in a competition constitutes entrant’s full and unconditional agreement to these Rules, the Official Rules, and Referee decisions, which are final and binding in all matters.

1.9 Abusive language towards other players within the competition and/or staff will not be tolerated. This may result in disqualification from the competition.

1.10 A team representative (ie Captain) must be contactable with an Admin at all times. We recommend that you check the site regularly to ensure you do not miss any communications from Admins. Right now we have a discord chat you will be invitet into when you register.


 

 

2 Competition Guidelines

2.1 This page contains the comprehensive rules governing gameplay and conduct. Whilst we have endeavoured to ensure all rules provide adequate guidance to meet all eventualities, instances may occur where teams feel that further guidance is needed. In such an event, contact a member of the Admin Team.

2.2 All competitors involved are expected to know and understand all of the rules. Not knowing that a rule existed is not an excuse for breaking that rule.

2.3 Any rule being broken may lead to disciplinary action. This action will be at the discretion of the Admin(s) involved, and the situation will be taken into account. Punishment may include, but not be limited to, forfeits, replays, penalty points, kicks, temporary and permanent bans.

2.4 Rosters must be submitted to the admin at the event, before registration for the Competition closes. In addition no subs or pick-ups will be permitted.

2.5 Your Gamertag must match that displayed on your team roster. It is both teams responsibility to check rosters before a match is played; any issues should be reported to an admin.

2.6 If a players Gamertag is incorrect, that player must not play and the team shall continue.

2.7 If a banned weapon/ability is used, it will result in a forfeit for the rounds in which they were used.

2.8 Planting on top of the bombsite in not allowed, doing so will result in a forfeit of the map. This also includes any exploit to alter defusing of the bomb through an object or making the bomb not defusable at any point in any position.

2.9 All participants in any competition will be required to uphold to the highest standards and observe common sportsmanship. Racism will NOT be tolerated. If you are seen to be racist then you will have action taken against you. Being abusive in any way towards fellow players or admins will also result in disciplinary action.

2.10 Using any Restricted Item listed below will result in a forfeit of the game, or a forfeit of the Search and Destroy round(s).

2.11 We highly recommend that all players appear offline and set their Friends List to Private during the Cup. However, players are not required to do either of these things.

2.12 After a game lobby has been created, only players on the two teams and admins may be invited/join.

2.13 Coaches are allowed to spectate their team only.

2.14 If a player lags out of a game during the first 30 seconds or before the first kill, the game must be restarted. If a player lags out of a game after the first 30 seconds or after the first kill, the game must continue and the player who lagged out may rejoin the game. If all players on a team lag out, that team will forfeit the game.

2.15 If a player lags out of a Search and Destroy game, the current round must be completed. After that round has been completed, the game must be ended. It is the responsibility of the shorthanded team to end or leave the game before the start of the next round. Rounds that are played while a team is shorthanded will be counted. After a game is ended, the shorthanded team will be given 5 minutes for their teammate to return before they must start another round shorthanded. When the game resumes, the score will be as it was when the game was ended and the teams will be set to begin the next round from the proper sides. For example, if Team A was leading 1 point to 0 when a player on Team B lagged out, and round 2 was won by Team A, the game would resume with Team A leading 2 points to 0.

2.16 If a player lags out of an Uplink game in the first half, the current half must be completed. After that half has been completed, the game must be ended. It is the responsibility of the shorthanded team to end or leave the game before the start of the next half. Any part of a half while a team is shorthanded will be counted. After the game is ended, the shorthanded team will be given 5 minutes for their team mate to return before they must start another half shorthanded. When the game resumes, the score will be as it was when the game was ended and the teams will be set to begin the next round from the proper sides. If a player lags out on the second half of a map, the team must complete the rest of the half.

2.17 If a player lags out of a Hardpoint game during the initial 30 seconds of the map being started, the game must be ended. After the game is ended, the shorthanded team will be given 5 minutes for their team mate to return before they must start shorthanded. The map will be started from 0-0. If a Player disconnects from a Game after the first 30 seconds, the Game must continue and the Player who disconnected may rejoin the Game.

2.18 If the Host disconnects from a game during the initial 30 seconds of the map being started, the game must be restarted. If the Host disconnects from the Game after the first 30 seconds or after the first kill, the hosting team will forfeit that map.

2.19 Any form of cheating, glitching, abusing in-game mechanics, or unsportsmanlike behaviour may result in a forfeit of a Map, Match, or Ban from Gfinity Events. Punishable unsportsmanlike behaviour includes, but is not limited to, excessive use of foul or degrading language. In addition, breaking any rule may result in a forfeit of a Round/Map, forfeit of a Match, Verbal Warning or Ban from Gfinity Events.

2.20 CPH NetParty reserve the right to stream any match in this competition. If your team’s match is chosen, you are to cooperate fully with the staff that are in your match.

2.21 If a game should tie, it must be replayed.

2.22 If any of the General/Map Settings are incorrect, the map must be stopped immediately and restarted with the correct settings. No map forfeit will occur. If a map is played to completion the map result will stand.


 

 

3 Game Specific Settings

3.1 All of the Settings and Restrictions are listed below. Anything in bold is a change from the default settings within the game.

3.2 The hosting team is responsible for setting up the game with the correct map and settings. If any of the settings are incorrect, the map should be stopped immediately and the setting corrected. No map forfeit will occur. If a map is played to completion the map result will stand.

3.3 Banned Weapons

Launchers – XM-53

3.4 Banned Scorestreaks

UAV
Care Package
H.A.T.R

3.5 General Settings – All Game Modes

Pre-Match Timer: 15 Seconds
Pre-Round Timer: 5 Seconds (3 Seconds for Search & Destroy)
Dynamic Events: Disabled
Map Scorestreaks: Enabled
Team Switching: Enabled
Spectating: Team Only
Spectating POV: First Person Only
Killcam: Enabled
Mini-Map: Normal
Battle Chatter: Disabled
Announcer: Enabled
Specialist Draft: Enabled
Ban/Protect: Enabled


3.6 Ban & Protect Settings

Ban/Protect Voting: Enabled
Ban/Protect Time: 15 Seconds
Create a Class Edit Time: 90 Seconds
Scorestreak Edit Time: 10 Seconds
Votes Per Player: 1

Specialist Draft

Specialist Draft: Enabled
Draft Time: 10 Seconds

Ban & Protect Rules

3.6.1 If a player makes a mistake during Ban & Protect (bans/protects the wrong item for example), the game cannot and must not be restarted.

3.6.2 If a player forgets to Ban or Protect at item, the game cannot and must not be restarted.

3.6.3 Teams should take a picture of the Ban & Protect stage in case a game is required to be replayed due to incorrect settings or another case as by defined in these rules.

3.6.4 If any of the timings for Ban & Protect are different from above, the game must be restarted but the same Ban & Protect items selected up until the point of the restart.

3.6.5 If evidence cannot be provided of the Ban & Protects that were made, admins cannot enforce rules where judgement is based on that information.


3.7 Spawn Settings – All Game Modes

Respawn Delay: See Gamemode
Incremental Spawn Delay: Disabled
Force Respawn: Enabled
Wave Spawn Delay: Disabled
Suicide Penalty: 3 Seconds (Hardpoint only)
Team Kill Penalty: Disabled


3.8 Health and Damage – All Game Modes

Hardcore: Disabled
Health: 100%
Health Regeneration: Normal
Friendly Fire: Enabled
Headshots Only: Disabled
Explosive Delay: None
Scorestreak Delay: 15 Seconds


3.9 Custom Classes

Custom Classes: Yes
Selections Allowed: 10


3.10 Hardpoint

Time Limit: 5 Minutes
Score Limit: 250 Points
Capture Time: Disabled
Activation Delay: Disabled
Location Order: Linear Order
Scoring: Constant
Pause Timer: Enabled
Respawn Delay: Disabled


3.11 Search and Destroy

Round Length: 1.5 Minutes
Score Limit: 6 Rounds
Bomb Timer: 45 Seconds
Plant Time: 5 Seconds
Defuse Time: 7.5 Seconds
Muti Bomb: Disabled
Round Switch: Every Round
Silent Plant: Enabled
Dog Tags Disabled
Number of Lives: 1


3.12 Uplink

Time Limit: 5 Minutes
Score Limit: 10 Points
Round Limit :2 Rounds
Carrier Armor: Normal
Carry Score: 2 Points
Throw Score: 1 Point
Reset Time: 15 Seconds
Respawn Delay: 5 seconds


3.13 CTF

*The game currently has a bug that will be fixed in a future patch. The CTF “Win Rule” setting is backwards. “Round Wins” is pointing to the “Total Flag Captures” string and description, and vice versa. To play with {Total Flag Captures} as the functioning Win condition, Go to [Setup Game] -> [Edit Game Rules] and set {Win Rule} to {Round Wins}. Make sure to also go to [Capture The Flag Advanced] and set {Capture Limit} to {Unlimited}.

Win Rule: Round Wins*
Time Limit: 5 Minutes
Round Limit: 2 Rounds
Round Win Limit: 2 Rounds
Enemy Carried = Delayed
Auto Return Time = 30 Seconds
Capture Condition: Flag At Base
Pickup Time: Instant
Return Time: Instant
Respawn Delay: 7.5 seconds


3.14 Maps & Modes

  • Search and Destroy: Breach
  • Search and Destroy: Evac
  • Search and Destroy: Fringe
  • Search and Destroy: Hunted
  • Search and Destroy: Infection
  • Search and Destroy: Redwood
  • Search and Destroy: Stronghold

  • Hardpoint: Breach
  • Hardpoint: Evac
  • Hardpoint: Fringe
  • Hardpoint: Stronghold

  • Uplink: Breach
  • Uplink: Evac
  • Uplink: Fringe
  • Uplink: Infection

  • CTF: Breach
  • CTF: Evac
  • CTF: Fringe
  • CTF: Stronghold

4 Match Specific

4.1 No warm-up or practice games are permitted once the Match’s first game has begun.

4.2 If a match is played before the scheduled time, it will not be considered a warm-up and will count as the official scores.

4.3 Teams must have at least three players present in order to start a game. A team will forfeit the Match if they don’t have at least three players present by 15 minutes after a Match’s default start time (Grace Period). Teams that played a previous game(s) in a Match will forfeit the Match if they don’t have at least three players present by ten minutes after the conclusion of the previous game (Grace Period). Teams with three players present will be forced to start a game at the end of a Grace Period. Bots are not permitted in any game. If Teams that are scheduled to play each other both forfeit a game or Match, the higher seeded team will be awarded the Game/Match win.

4.4 To get help with a No Show issue, you MUST contact an admin within 15 minutes of the scheduled match time.

4.5 If you suspect the opposing team is cheating, using the wrong weapons, glitching etc. you MUST contact admins with proof of the accusation. Glitching accusations must be supported by video proof. You can use built-in support on the PS4 to record footage to support your accusation.

4.6 A standard five minute delay between maps is allowed for the new host to setup. Teams may request an extension to this by a further five minutes, by contacting an admin.

4.7 If the Host incorrectly ends a game, their team may forfeit the game.


 

5 Host

5.1 For BO3, the top bracket team must host 1st Map. The lower bracket team must choose sides on the first Map.

5.2 Then the lower bracket team will host the 2nd Map. The top bracket team must choose sides on the second Map.

5.3 The top bracket team will host the 3rd Map. The lower bracket team must choose sides on the third Map.

5.4 For BO5, the top team must host all odd numbered games (1, 3, 5) in a Match. The lower team must host all even numbered games (2, 4) in a Match. The team that isn’t host must choose which side to start on.

5.5 Games must be played in order.

5.6 As the hosting team changes over the course of a Match, the new Host should leave the Custom Games Lobby and create a new one. If host isn’t given to the player that was designated to be the game’s host, the game must still be played.

5.7 Teams should play a Lag Test Game, for roughly 30 seconds, to determine if a Host is acceptable. If it is determined that the Host is unacceptable, a new Lag Test Game should be performed with a new Host. Lag Test Games should be played using a Game Mode and/or Map that the teams are not schedule to play.

5.8 All players must agree that the Host is reasonable before the start of a game. If a reasonable Host cannot be found, the best Host should be used.

5.9 If a players connection to the Host becomes unreasonable during a game, the game must still be played. After each game, either team may request that a new Host be tested, if the previous Host was unreasonable. The round/game where connection became unreasonable will not be replayed.

5.10 The Team that doesn’t Host a Game must choose a side to play for that Game.


 

6 Reporting

6.1 Both teams must report the Match results within 10 minutes of its completion.

6.2 To report the Match results, teams must report the Match Score accurately, with overall games won being reported. For example, the Match Score can be reported as 3-0, 3-1, etc. Reporting the individual points for each game is optional.

6.3 How do I report scores?

To report scores contact an admin.

6.4 You are only able to report score 15 minutes after the designated start time of the fixture

6.5 Both teams captains must submit the result so the admin.

6.6 If two teams/players says the result differently, a member of the Admin Team will be notified of the discrepancy and will intervene.

6.7 Teams/players found to be deliberately misentering results may face disciplinary action from the Admin Team.

6.8 If a Match is not played, and neither team reports a No Show, awarding of the Match win will be decided by a admin.

6.9 At least one member of each team should take a Scroeenshot(s) of each Runds results. Screenshots should contain the Round Score, players on each team, and a time stamp. In order to dispute a player leaving and/or an in-game glitch, video proof must be provided. The video must show the Gamertags, Map, Game Type, as well as the player dropping or the opposing team performing a glitch.

6.10 If a Screenshot(s) or Video(s) is needed in order to resolve a dispute, you must clearly state what the issue is, the time in the video in which the issue occurred, and/or what the admin should be looking at in the Screenshot/Video. For all cheating claims, the burden of proof is on the accuser.


 

 

7 Team Guidelines

7.1 It is the responsibility of the team to ensure that all players are eligible to participate in the competition and have no other accounts that are banned.

7.2 It is the responsibility of the players to not play for more than one team in the competition.

7.2 It is the responsibility of the team and players to ensure Gamertags are entered correctly on the website.

7.3 It is the responsibility of the team to ensure the conduct of all players on your roster.

7.4 It is the responsibility of the team captain to ensure there players are on the correct team before game has started. Any kind of abuse to this rule i.e time wasting will result in a Disqualification


8 Conduct

8.1 All participants in any CPH NetParty competition will be required to uphold to the highest standards and observe common sportsmanship. Racism will NOT be tolerated. If you are seen to be racist then you will have action taken against you. Being abusive in any way towards fellow players or admins will also result in disciplinary action.

8.2 Anyone who has been caught cheating in any event may be suspended from all future CPH NetParty events. Admins will review cases and players may be suspended for a period of not less than one month and is subject to review by admins for readmission after that point. If a player is caught cheating in a match, their team shall forfeit that game. CPH NetParty will not conduct witch-hunts to try and find cheat violations against players.

8.3 Players are expected to compete in a professional manner. Throwing a match, halting play without cause, or showing a flagrant lack of effort will be construed as a violation of player conduct, and will result in match forfeit and disqualification from the Event.

8.4 Consequences for players and Clans behaving in a manner considered by admins to be abusive, glitching, modding, cheating, unsporting, or who in any way conduct themselves in a manner not befitting the League, will be subject to the following minimum sanctions:

a. First offence, Player warned.
b. Second offence, Forfiet round.
c. Third offence, Forfiet game.
d. Any further offences will result in the team being permanently removed from the league.

8.5 Players found to be abusing the game mechanic to gain advantage in a way considered by the admins to be unsporting will result in an admin review of the match and suitable remediation will be made in respect of that game. This will include, but is not limited to: overturning match results and awarding default wins, points deduction, player/clan temporary or permanent bans.

8.5a For all avoidance of doubt, this includes deliberately killing team mates or committing suicide to replenish grenade and special grenade supplies. If a team suspects their opposition of doing this, they should immediately contact an admin who will then overturn the result of the game or map upon proof being presented via the theatre lobby.


9 Prizes

9.1 All results and final placements are verified by Admins before prizes are awarded.

9.2 If one or more players are found to have broken any rules then the entire team will forfeit their prize.


10 Admin/Staff

10.1 Staff can be contacted to answer any questions or solve any problems your team may have during a Match.

10.2 If a adminmember is called into a Custom Games Lobby, players must keep the Gfinity Staff member un-muted at all times.

10.3 Verbal and/or written abuse of a Staff member will not be tolerated. This includes, but is not limited to: Forum Posts, Private Messages, and PSN messages. The individual user and/or team violating this rule will be subject to penalties. All team leaders are responsible for the conduct of the players on the team while interacting with Staff and are subject to penalties if a team member becomes abusive towards Staff.

10.4 Staff members have the discretion to make necessary calls to ensure the match is completed successfully. When in a match, the Staff member’s call is final and must be followed. Failure to do so will result in penalties for your team.


11: Miscellaneous

11.1 The rules are open to many different interpretations. The only interpretation, which matters, is the interpretation of the Admin team. We reserve the right to modify the rules at any time. This includes changes due to software updates or releases, and any other change deemed necessary by the league. You must understand that the rules listed are guidelines to try and ensure fair and competitive play, and they will be applied by officials based on the spirit of the game. Teams should check the rules prior to any event to ensure they are in compliance. They should also keep an eye on the website, as changes will be announced on the website. You must be familiar with the current rule set.

Log ind:

Aktive Turneringer

Artikler