General Rules

General Rules

  1. Rules are subject to change at any time. It is the responsibility of all the users participating on Gaming-League.net to know and understand the rules before scheduling any matches. By sending or accepting a challenges, you acknowledge that you have read, understand, and agree to abide by the rules posted here.
  2. Our goal here at Gaming-League.net is to provide gamers with a place to find fair and competitive matches. In order to accomplish this goal, we will not tolerate players or teams that cause problems or attempt to undermine the positive atmosphere on Gaming-League.net. This includes teams that cheat, dispute on purpose, or repeatedly abuse other players. There are severe penalties for these offences. As with all accusations, valid proof must be provided.
  3. Users must utilize their own unique username when competing on Gaming-League.net. This unique username must have been registered on Gaming-League.net personally by the user. The registered username must contain the correct and complete Name, Address, and Email of the user. If a false Name, Address, or Email was entered, the user voids the privilege to participate in the Ladder/Tournament and receive any prizes.
  4. All Gaming-League.net accounts, teams and roster spots are property of Gaming-League.net. Any advertising of, or attempts to buy, sell, trade, or exchange any aforementioned item is strictly prohibited. Violators will be removed from all Gaming-League.net online properties and all related accounts terminated. Furthermore, Gaming-League.net reserves the right to deactivate, reset or temporarily suspend any account or team, without notice, that violates our Terms.
  5. If a user is found to be evading an active penalty, the original account that was banned will be disabled, regardless of the original offense. In addition, users found to be participating on a team with a user that is evading a ban will be subject to penalties including removal from the site. We advise you to report the evading user immediately by utilizing our ticket support system.
  6. The Leader of a team can change the team name, blast message, logos, avatars and website links. The images/information submitted must be appropriate and if found otherwise, the team will be subject to penalties.
  7. Teams on a ladder must contain the minimum number of eligible players to remain active on a ladder. Teams without the minimum number of eligible players – especially teams that are “abandoned” – are subject to removal at the Staff’s discretion.
  8. As to ensure fair competition, Gaming-League.net reserves the right to amend all match-related rules listed herein on a case by case basis. Teams who manipulate these rules maliciously and/or at the expense of other members will be penalized for Unsportsmanlike Conduct.
  9. All rostered members associated with a team must live within the correct region of competition. This applies to only region specific ladders/tournaments/events. Penalties will be assessed to all players in the incorrect region along with the leader of the team.
Matches

  1. All matches must be played in their entirety unless both teams agree to postpone or cancel the match. A Standard Ladder Match will be played best of 1 map, 3 maps (first to 2) or best of 5 maps (first to 3).
  2. Randomized maps MUST be used. Verbal agreements will not receive staff support.
  3. We strongly recommend that you set your Friends List to “Private”.
  4. If a map results in a tie, the map will be replayed with the same sides and settings.
  5. Deliberate and repeated team-killing or committing suicide on purpose during any Kill-Dependent game mode  will  result in a forfeit of the map. If a team is accused of violating this rule, the accuser must provide valid proof. Complete the match and then report the scores correctly and then submit a ticket.
  6. Team changing in-game is not allowed. If a player joins the wrong team upon launch, the map will be restarted. Abuse of this rule will result in a lock/ban. If a player changes teams after the first kill, the offending team will forfeit the map.
  7. Using disabled equipment/weapons/secondaries during a game will result in a forfeit of that map. Using the equipment includes holding it while running or walking and/or placing it on the ground.
Eligibility

  1. All team members must have an active tag associated with their account. Failure to have an associated tag on an account may also cause a player to be ineligible.
  2. Only one(1) tag is allowable per member per platform.
  3. If you identify the other team has an ineligible player on their team, simply ask them to replace the player with one that is eligible. If they can not replace the player, the round will be a forfeit for their team unless both teams agree to allow the ineligible player to play. This agreement must be done in the match comments section. There is no exceptions to this agreement or admins will not honor the agreement when making a decision on support tickets.
Substitute Player

Any team can have any number of substitute players but must adhere to the following rules;

  1. All substitute members must play at least one game during the course of the tournament/ladder/event or will not be eligible for winnings.
  2. After each game in the match, each team may make any number of substitutions between players.
  3. Players must be on the team and eligible 2 hours prior to any match he/she wishes to play in.
Hosts

  1. The higher ranked team at match time will host the first map. The higher ranked team is the team ranked closer to “1” on the ladder. If there is a tie in rank (i.e. both are unranked), the Team ID closest to 0 will host first. The lower ranked team at match time will host the second map. This will alternate for each map until/if a tie breaker map is needed. If a tie breaker map is needed, the lower ranked team will host the final map.
  2. The team that is not hosting will pick which side to play on.
  3. Teams may not delay the match for more than 5 minutes between each round/map. A round is defined as a stopping point during the match when match settings may be altered, and/or players may switch sides or change equipment.
  4. If a player/host disconnects during the initial launch of a map, the map will be restarted. The initial launch is defined as within the first 30 seconds or before the first kill. If both teams disagree over when the disconnection took place, proof must be provided. Complete the match and then report the outcome. Submit your ticket containing valid proof.
  5. If the host disconnects after the map has started, the host’s team forfeits that map. After the map has started is after 30 seconds or after the first kill. If both teams disagree over when the disconnection took place, proof must be provided. Complete the match and then report the outcome. Submit your ticket containing valid proof.
  6. If a player disconnects after the game has started, the game will continue and a player may be re-invited. The re-invited player may be the player that dropped or a new eligible player that was selected as a substitute when setting up the match. The only exception to this rule is for a “Kill Dependent Game Mode”. Please see the rule below regarding “Kill Dependent Game Mode”.
  7. A “Kill Dependent Game Mode,” often referred to as Deathmatch, is a game mode whose winner is decided by the overall number of kills, or points gained from kills. Because this mode relies on the number of players present, a team can never play shorthanded when playing this mode. A Team that loses a player during this game mode, after the first kill has occurred, forfeits that map.
  8. A team can start a map shorthanded unless it is for a “Kill Dependent Game Mode” (for a description of what a “Kill Dependent Game Mode” is, please see above). You can only be shorthanded by one player. For example, in a 4v4, a team can start a map with 3 players. If you are missing more than one player, you cannot start a map. This rule applies to all matches except for 1v1’s.
Disconnects

  1. If a player/host disconnects during the initial launch of a map, the map will be restarted. The initial launch is defined as within the first 30 seconds or before the first kill.
  2. If a player disconnects, they may be re invited or an eligible substitute player may take their place.
  3. If the host disconnects after the map has started, the host’s team forfeits that map. After the map has started is after 30 seconds or after the first kill.
  4. If both teams disagree over when the disconnection took place, proof must be provided. Complete the match and then report the outcome and submit a ticket for review.
No Cheating or Glitching

  1. Zero tolerance policy for cheating. Teams caught cheating, “glitching”, or abusing in-game mechanics will immediately be disqualified from the tournament or ladder and may be subject to a ban.
  2. Any acts of cheating or glitching will be forwarded to the Game Manager and dealt with respectively.
  3. ANY exploitation of a map flaw without reporting it to an Admin is grounds for disqualification and removal from ladder & tournament competition.
Communication

  1. Teams are allowed to utilize Party Chat during matches.
  2. The use of any communications other than what is provided within the game is strictly prohibited.
Lag Tests

  1. A lag test must conducted for at least 60 seconds prior to any match being played, and any time the host is changed.
  2. A lag test is a test round that doesn’t count and uses the standard game settings that will be used during the match. For the lag test, a map that is not scheduled for play must be used. If the game lags during this test, a new host must be chosen. If both teams cannot agree on an acceptable host, a ticket must be submitted by both teams to cancel the match.
  3. Only if both teams agree that a lag test is not necessary, this rule may be ignored.
Rosters

  1. It is the responsibility of both teams to verify the eligibility of all players playing in the match prior to starting or continuing any match play. A team playing with an ineligible player will forfeit the map the ineligible player participated in. Players must be on the team and eligible 30 minutes prior to any match he/she wishes to play in.
  2. All gamertags on a team’s roster must be valid. The gamertag must be legitimately owned by the user on the roster.
  3. Users are permitted to be listed on only one team on each ladder at any given time. Users are only permitted one gamertag per ladder.
  4. All roster spots must be comprised of only one valid gamertag. Spelling and spaces must be exact, but does not need to be case sensitive.
  5. Gamertags may not contain foul language, disparaging remarks, hateful or racist names.
  6. If a team uses an ineligible player in a match they will forfeit the map the ineligible player participated in. Proof must be shown to support any claims of an ineligible player playing in a match.
Challenges

  1. When sending and accepting challenges, you MUST select the players who will actually be playing in the match. You will be prompted to do this before sending and accepting any challenges. The number of players you must select is determined by both the match size and the ladder. Therefore, if the match is a 2v2, you will need to select two (2) people. On Team ladders, however, you will have the ability to select up to one (1) additional player. This player may serve as a substitute during the match.
  2. The only players eligible to play in the match are the players who are selected when the challenge was sent/accepted. Once a match is confirmed, the eligible players from both Teams will be displayed on the Match page. Players who enter the room, but whom were not selected to play beforehand, will be considered ineligible players.
  3. If you need to cancel an already accepted match, you must first select the match you wish to cancel and hit the “Request Cancellation” button. Fill out the required field to notify your opponent that you wish to cancel, and then submit the request. Your opponent will then either accept or decline the request. If the cancellation request is not accepted by your opponent, you will be required to play the match. Your opponent will have 72 hours to respond to this request. If the request is not accepted or declined within 72 hours, the match will be automatically cancelled.
No-Shows

  1. A team has 15 minutes to show-up with the proper number of eligible players and be ready to start the match. Failure to do so will result in a forfeit. Teams are responsible for all scheduled matches.
  2. If you have a No Show issue, please submit a Ticket.
  3. To receive a no show win, you must submit a ticket within 30 minutes of the scheduled match time. If you have any proof, be sure to submit it in your ticket.
Reporting

  1. Both teams are responsible for reporting the match within 30 minutes of its completion. If teams do not report matching results, the match will result in a ‘dispute’. Both teams are then required to submit a ticket regarding the dispute and include any valid proof they have. If you had a problem with the match, you can submit a ticket containing your valid proof.
  2. Falsifying match scores may result in a penalty. Do not dispute a match you lost legitimately. Disputing on purpose is defined as knowingly reporting that you won a match despite the outcome of the match resulting in a loss for your team.
  3. Matches that go unreported by one team will be reported automatically for the team that did report. Matches that go unreported by both teams will be deleted automatically.
  4. Teams who report matches before the match has concluded are subject to penalties.
Tickets

  1. Submitting an incomplete or incorrect ticket will be closed immediately.
  2. The decision to escalate and/or assign a ticket to another staff member will be made by the staff member viewing that ticket. Requests for “Supervisor Review” are not valid.
  3. The admin’s decision is final.
  4. When submitting a ticket, It is very important that your ticket contain all the proof that you have to support your case. If you are submitting a ticket about a match, please include the match ID and team ID.
  5. Helpful information to include in the ticket include;
  6. – Which player broke the rule
  7. – What map was the issue in
  8. – About how far into the map was the rule broken (it is preferred if you can give the exact time on the timer)
  9. – What was the exact error message or what is the name of the server you need addressed.
  10. Do not dispute on purpose or you risk being penalized. Disputing on purpose is defined as knowingly reporting that you won a match despite the outcome of the match resulting in a loss for your team.
  11. Your ticket must include valid proof to support your claim. Proof needs to clearly show the entire scoreboard so that we can see all players involved. It must also adequately support your claim by showing the problem you encountered.
  12. All proof submitted in your ticket needs to be from the match in question. If you submit proof from the wrong match/game or links to inappropriate material, you risk being penalized.
  13. You may wish to challenge an admins judgement if you feel your ticket was handled poorly. To do this, you must create a NEW support ticket and explain your concerns with any proof you may have.  You must submit the challenge ticket within 2 days (48 hours) of the outcome of the ticket in question is released/resolved.
Challenging Outcome of Ticket

  1. This ticket will then be reviewed by a higher ranked admin. The senior admin will only review the resulting decisions made by the previous admin to ensure that the outcome was of sound judgement.
  2. The senior admin will not go over old ground as this ticket is to ensure the admin was working within guidelines and with everyone’s best interest at heart.
  3. However, the senior admin may overturn a previously made decision if they feel this would be the correct thing to do.
  4. You may challenge an admins judgement once per season.
  5. The conclusion of this ticket is final.
Proof

  1. Before submitting any proof, please make sure the match is reported correctly. If you had an issue with a match such as a No Show, Wrong Settings, etc., you must report the correct Match Status on the Match Report screen. Do not dispute the match on purpose.
  2. When submitting proof, you must paste the hyperlinks to your proof in the URL boxes located below the “Message Body” box. Be sure to only place one URL link in each box.
  3. All proof submitted in your ticket needs to be from the match in question. If you submit proof from the wrong match/game or links to inappropriate material, you risk being penalized.
  4. You need to show proof of winning each map/game in a match to be given the win for it. All proof must be clearly visible and show the in-game full scoreboard during the completion of that map/game. The proof must clearly show both team’s players to be considered valid. Also, proof needs to be large enough in size to clearly read all scores and gamertags.
  5. All video proof should be uploaded to a website such as YouTube. The URL link to the individual pictures/proof must be placed in a ticket.
  6. For all glitching and cheating claims, the burden of proof is on the accuser. To submit a glitching or cheating claim, you must submit a ticket and include the URL link containing valid proof.
  7. All conversations between users are not considered proof. This includes AIMs, emails, PMs, etc.
Staff

  1. Please do not contact a staff member directly regarding your support ticket. We assure you it will be answered in a timely manner.
  2. Staff members that enter a match have the discretion to make any 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. After the match, if you disagree with a call made, you must first accurately report the match. You may then submit a ticket for review by a staff member.
  3. You can view all Staff from the Help > Staff Contact list link in the main menu.
  4. Teams or players are NEVER to badger staff about a decision unless they are making an official penalty challenge or complaint.
  5. In this case only the site TICKET system should be used.  Disregard for this rule could result in a site wide suspension. This includes badgering an Admin through their personal messenger system in or outside of Gaming-League.net
  6. Abuse of our volunteer Staff will not be tolerated in any form. This includes written messages or verbal comments inside and outside of match lobbies.
Team and Player Penalties

Minor Strike

Inappropriate Content Submitting or Irrelevant Proof
Unsportsmanlike Conduct
Ticket Spam/Abuse Spamming or Abusing the Ticket System
Major Strike
Managing Multiple Accounts or Double Rostering
Attempting Free Wins
Regional Rule Violation Violating Regional Rule
Staff Abuse Abuse of Support Member
Ban
Disputing on Purpose or Disputing a Match Without Valid Proof
Cheating or Glitching
Free Wins Giving or Receiving Free Wins
Disputing on Purpose
Evading an Active Ban
Impersonating Staff Impersonating an Gaming League Staff Member
Fake Proof
Playing with a Hacker/IP Flooder/Infections/Modified Console
Hijacking/Phishing Gaming-League.net Account
Proxy IP
IP Flooding