Last modified: 09 MARCH 2023
This page contains the game-specific rules for Gamer.LK Mobile Legends Ranked tournaments. These rules must be followed in conjunction with the General Competitive Rules of Gamer.LK Ranked Tournaments.
3.1. – By submitting a registration for a Gamer.LK Ranked Mobile Legends tournament, all teams and players acknowledge without limitation to comply with the rules set herein and especially with the decisions made by the Gamer.LK Staff.
3.2. – All competitors are expected to know and understand all the rules described here. Not knowing that a rule existed or that it was in place will not be considered as an acceptable reason for breaking said rule.
3.3. – A player or team’s name, icon, profile picture or logo may not contain any of the following: profanities, obscene language, gang affiliation, drugs, sexual material, offensive material, slander of Gamer.LK or it’s administration, partners or sponsors.
3.4. – A player’s name cannot change during the tournament. He/she must play with the name they initially registered on until the tournament ends. A player who changes it during the tournament should revert it back to what he/she registered with or they will not be allowed to participate.
4.1.1. – A Team has to consist of at least FIVE players.
4.1.2. – Upto TWO substitute players can also be registered for each team.
4.1.3. – Each player can be registered and can subsequently play for only one team during the tournament.
4.2. – Substitutions
4.2.1. – The substitute player/s must be registered with the team prior to the tournament starting.
4.2.2. – Use of a substitute player must be informed to the Gamer.LK Staff well before the start of the scheduled match.
4.2.3. – The use of non-registered, suspended, or otherwise ineligible players in a match is not allowed under any circumstances.
4.2.4. – Doing so will result in a suspension or extended suspension of the individual in question, suspension of relevant team management, and may result in match overturn.
4.3. – Stand-ins
4.3.1. – By definition, a stand-in here refers to a player who hasn’t been registered to a team on the registration form but wants to play for a team after registrations close/matches commence.
4.3.2. – At LAN tournaments, the use of a stand-in is allowed but they have to be presented and registered at the Registration Desk before they are used.
4.3.3. – The use of a stand-in in online tournaments is strictly prohibited and is grounds for disqualification.
4.3.4. – This applies to account sharing as well. The Steam account that was used during registration should be the only one used for playing.
4.4.5. – In LAN tournaments which have qualifiers (such as SLCG), no player that played in any other team at any qualifier that was completed can be used as a stand-in.
5.1. – For online tournaments, both teams scheduled to play at a certain time should be present online on Discord or Ingame at least 30 minutes before the scheduled start time. For LAN tournaments, teams should be present at the venue well before an hour of their scheduled match time.
5.2. – If by 10 minutes past the scheduled match start time a team doesn’t have enough players to play, the match will be deemed a walkover to the team that is present with its full roster.
5.3. – A team CANNOT start a game shorthanded. Both teams should necessarily have 5 players and there can be no games with 4 players on either site. Any team with players missing after the grace time provided will be considered as having forfeited the match.
5.4. – In a best of 3 or 5 games match, a maximum delay of 10 minutes in between matches will be allowed.
5.5. – Regarding the scheduling of online matches, matches can be played on all days of the week (including public, bank. mercantile holidays, etc) and will be scheduled beforehand and announced on a “Draw/Schedule” on Gamer.LK. Scheduling will be done at the discretion of Gamer.LK Staff.
5.6. – Gamer.LK and any Organizers will make every effort to inform the teams of scheduled match dates and times – but please note it is the responsibility of the teams to check their game time and date. Gamer.LK or any Organizer will not be responsible to inform matches to teams. Not attending a match due to not being informed of the schedule is NOT an excuse.
The team who completely destroys their opponent’s nexus or forces their opponent to surrender.
6.2. – Game Settings
– Game Mode: Draft pick 5v5 match BAN 5
– Game Type: Room Tournament (LIVE)
– Team Size: 5
– Allow Spectators: Lobby Only
6.4. – Use of Public Chat
Public chat can only be used by the team captains and/or Tournament Staff regarding game pauses, disconnections, etc. Team members are allowed to greet each other at the start and end of the match on public chat (i.e: GGWP, GLHF, etc) but should avoid using it during a match. No foul language is allowed on public chat and doing so may lead to the match being awarded to the opposing team and the offending team being disqualified from the match. Penalties for future matches may also be applied.
6.5. – Account Suspensions by Moonton
Any player who loses access to their registered account due to a suspension or penalty issued by Moonton in the middle of a tournament, regardless of the reasons will NOT be allowed to take part in the tournament. They will not be allowed to switch their account. The team may proceed with a Substitute player if they have one registered on their roster or if not they will have to forfeit their matches. This rule applies to online tournaments and tournaments with online qualifiers.
6.6. – Side Selection
6.6.1. – First pick & second pick are determined from the coin toss, the team that wins the
toss can choose the first pick or second pick.
6.6.2. – Alternates for game two. A coin toss is used again if there is a third game.
7.1. – Abuses & Exploitation
Exploiting game or map bugs/glitches/flaws (“exploits”) for the purposes of gaining an unfair advantage is prohibited. Exploits that are not specifically named here are still prohibited but will be dealt with on a case-by-case basis. Gamer.LK Staff reserve the right to decide what will be deemed as an exploit or abuse.
7.2. – Scripting
The use of scripts are illegal.
7.3. – Use of Third Party Softwares
The use of any third-party addons, hooks, programs or wrappers that interact with or alter the game client, its appearance or behaviour for the purposes of gaining an unfair advantage is prohibited. Exceptions: Third party voice communication software such as (but not limited to) Teamspeak are allowed.
7.4. – Impersonations
Impersonating an eligible player by attempting to alias as them, using their Moonton(Mobile Legends) account or by any other method is prohibited and will result in the aliasing player and the player they are aliasing as being removed from the tournament. The Tournament Staff will have access to player IP addresses and other information to monitor accounts and players.
7.5. – In-game names
Each team member must have his/her primary nickname or something very similar as his ingame name during all matches to be easily identifiable for referees, broadcasters, and viewers. What counts as similar is for the Gamer.LK Staff to decide. The only additional information allowed in a player’s ingame name is clan tags or sponsor names. Team members are kindly requested to limit the use of profanity on in-game names/aliases as this degrades the value of the team and the tournament as well.
All lobbies should be hosted ONLY by Gamer.LK Staff. Under no circumstance should players join a lobby created by anyone else.
8.2. – Game Setup
5.1 Start of Pick / Ban Process. Once all ten players have reported to the official game lobby, a referee will request confirmation that both teams are ready for the pick/ban phase (as defined and described below). Once both teams confirm readiness, a referee will start the game
5.2. Recording of Pick/Ban Process. Picks/bans will proceed through the client’s Tournament Mode feature. If picks/bans are completed substantially in advance of game setup, at the instruction and discretion of GLK referees, the GLK referees will record the official picks/bans and manually abort the game start.
8.3. – Restrictions on Gameplay Elements.
Restrictions may be added at any time before or during a match, if there are known bugs with any items, Heroes, skins, emblems, or battle spells, or for any other reason as determined at the discretion of Gamer.LK.
8.4. – Spectators
Team managers/Sub players are NOT allowed in the game lobby. Random players are not permitted in the private lobby for any reason. Gamer.LK League Referees and Casters have the right to spectate any game.
9.1. – Prohibited heroes
On the online servers, some remade Heroes, and Heroes that have newly been added will be prohibited from use within two weeks of being updated. The specific match prohibitions and usage times will be notified by GLK officials. As for Heroes that are known to cause glitches, members of the GLK will prohibit their usage for matches for a period of time according to the seriousness of the glitch, please strictly comply with the GLK’s notifications.
9.2. – Picks & Bans
Draft Pick proceeds in a snake draft format as follows:
Blue = A; Red = B
Ban: ABABBA; Picks: ABBAABBAAB
In the event of an erroneously-selected Hero pick or ban caused by personal reason, the erroneous selection shall be deemed irrevocable. If it is caused by a technical reason or malfunction of the game, the team in error must notify a referee immediately, the referee and GLK referees will then communicate and confirm with one another before deciding whether or not the player can re-select.
9.3. – Trading Champions
Teams must complete all champion trades before the countdown ends during the Trading Phase, or will be subject to a penalty in future games.
9.4. – Pauses
If it is an online match, the maximum pause time for each team during each game is 3 minutes, the Referees must pause the match as soon as a team calls for a game pause and ask for the reason for pausing. If no good reason for pausing the game can be given, the GLK referees have the right to penalize the team which called for the pause according to severity. Acceptable reasons include, but are not limit to: Lag, software malfunction such as a glitch, phone hardware malfunction, the health of a player, GLK referees have the final right of interpretation for what is deemed an acceptable reason. If one team has used up all of its pause time during a game but still signifies they wish to pause, the Referee must first assess the situation and decide whether they will pause the match on behalf of the officials (due to a major issue such as a phone malfunction, internet disconnection, game crash etc.), if it’s just a little bit of lag or another minor issue the Referee can refuse the player’s request to pause the game and ensure the smooth running of the match. Once the problem has been resolved, the Referee must ask all players whether they are ready or not, once all the players have agreed, the Referee can resume the match.
9.5. – Disconnects & Reconnects
If a player disconnects, the game is to be paused instantly. When the number or the duration of breaks becomes too high or long, Gamer.LK Staff reserve the right to force the continuation of the game. Tournament organizers are not allowed to take a decision in these situations.
9.6. – Controlled Game Start
In the event of an error in game start or a decision by Gamer.LK to separate the pick/ban process from game start, a GLK referee may start the game in a controlled manner and all players will select Heroes in Custom – Classic Mode. All players will select Heroes in accordance with the previous valid completed pick/ban process.
9.7. – Game of Record
A game of record (“GOR”) refers to a game where all ten players have loaded and which has progressed to a point of meaningful interaction between opposing teams. Once a game attains GOR status, the period ends in which incidental restarts may be permitted and a game will be considered as “official” from that point onward. After the establishment of GOR, game restarts will be allowed only under limited conditions (see Section 9.4)
Examples of conditions which establish GOR:
9.7.1. Any attack or ability is landed on minions, jungle creeps, structures, or enemy heroes.
9.7.2. Line-of-sight is established between players on opposing teams.
9.7.3. Setting foot, establishing vision or targeting skillshot ability in opponent’s jungle by either team, which includes either leaving the river or entering brush connected to enemy jungle.
9.7.4. Game timer reaches Thirty Seconds (00:00:30).
9.8 – Stoppage of Play
If a player intentionally disconnects without notifying a GLK referee or pausing, the GLK referee is not required to enforce a stoppage. During any pause or stoppage, players may not leave the match area unless authorized by a GLK referee.
GLK referees may order the pause of a match or execute a pause command on any player station at the sole discretion of the GLK Referee, at any time.
9.9. – Player Pause
9.9.1. Players may only pause a match immediately following any of the events described below, but must signal a GLK Referee immediately after the pause and identify the reason. Acceptable reasons include:
– An Unintentional Disconnection.
– A hardware or software malfunction (e.g. monitor power or peripheral disability or game glitch)
– Physical interference with a player (e.g., fan gank or broken chair or table)
Player illness, injury, or disability is not an acceptable reason for a player pause. In such a situation, the team must alert a GLK referee, who may in his/her sole discretion, grant a pause in order to evaluate the identified player to determine whether player is ready, willing, and able to continue playing within a reasonable period of time, as determined by the GLK referee, but not to exceed a few minutes. If the GLK referee determines that the identified player is not able to continue playing within such reasonable period of time, then the identified player’s team shall forfeit the game unless a GLK referee, in his/her discretion, determines that the game is subject to an Awarded Game Victory (see Section 9.5).
9.9.2. Resuming the Game. Players are not permitted to resume the game after a pause. After clearance from a GLK referee is issued and all players are notified and ready at their stations, which will be contingent on the team captain confirming through in-game chat that both teams are ready to resume play, the inclient spectators will unpause the game.
9.9.3. Unauthorized Pause
If a player pauses or unpauses a game without permission from a GLK referee, it will be considered unfair play and penalties will be applied at the discretion of Gamer.LK
9.9.4. Resuming the Game
Under which conditions can a game be reset is entirely decided by the GLK referee. The following conditions are examples used to illustrate:
– Remakes Before GOR. The following are examples of situations in which a game may be remade if GOR has not been established:
– If a player notices that player’s emblems, battle spells or GUI settings have not applied correctly due to a bug between the game lobby and match, player can pause the game to adjust these settings. If the settings cannot be correctly adjusted, then the game may be restarted.
– If the GLK referee determine that technical difficulties will not allow for the game to resume as normal (including a team’s ability to be in proper position for certain game events, such as minion spawn)
9.10 – Restarts After GOR
The following are examples of situations in which a game may be restarted after GOR has been established.
9.10.1. If a game experiences a critical bug at any point during the match which significantly alters game stats or gameplay mechanics.
9.10.2. If a GLK referee determines that there are environmental conditions which are unfair (e.g. excessive noise, fan gank, hostile weather, unacceptable safety risks)
9.11. – Restart Protocol
If a game experiences a critical bug at any point during the match that significantly alters game stats or gameplay mechanics, or the external environmental conditions become untenable then a restart may occur.
Certain circumstances must be met before a restart may occur. GLK referees must determine that the bug is critical and verifiable.
For the bug to be considered critical, the bug must significantly damage a player’s ability to compete in the game situation. The determination of whether the bug has damaged a player’s ability to compete is up to the sole discretion of the GLK referees. In order for a bug to be considered verifiable, the bug must be conclusively present and not possibly attributable to player error.
The spectator must then be able to replay the instance in question and verify the bug. If a player believes s/he has experienced a critical bug, s/he must pause the game and alert a referee in a timely fashion. If it is believed that a player is attempting to delay reporting of a bug to wait for a possible restart at a more advantageous time, then a restart will no longer be granted. If GLK referees determine that the bug is critical and verifiable and
that the player followed the pause protocol, then the disadvantaged team will be presented with the option for a restart. If the team accepts, officials will attempt to utilize the rules set in Section 9.4 to recover the game. An exception to Rule 9.4 is if the restart occurred due to a hero bug, then settings no longer will be retained (including picks and bans) regardless of Game of Record status and the hero may be made ineligible for at least the remainder of the day’s matches unless the bug can be conclusively tied to a specific game element that can be fully removed (i.e. a skin that can be disabled).
This section is applicable if the pause is directed as per Section 9.4 and does not limit the ability of an GLK referee to institute a restart.
9.12. – Controlled Environment.
Certain conditions may be preserved in the event of a restart of a game that has not reached GOR, including, without limitation, picks/bans or battle spells. If, however, a match has reached GOR then GLK referees shall not retain any settings.
9.13. – Player Confirmation of Settings.
Each team captain shall verify that every player on his/her team has finalized their intended game settings (including emblems, talents, controls, and
GUI settings) before GOR is established. Any error in verification is not grounds for a game restart after GOR is established.
9.14. – Awarded Game Victory.
In the event of a technical difficulty which leads GLK referees to declare a restart, Gamer.LK may instead award a game victory to a team. GLK referees, in their sole discretion, may determine that a team cannot avoid defeat to a degree of reasonable certainty. The following criteria may be used as reference for determining this acknowledgement, if the two criteria are not satisfied, one team’s victory is unable to be directly determined, however, if one of the criteria has been satisfied the GLK referee will use their own judgement according to the situation to determine whether one team would be inevitably defeated.
9.14.1. The difference in kills between the teams is no less than 15.
9.14.2. A game has been played for more than 10 minutes on the game clock while gold difference is more than 800*gaming time.