Gamer.LK Competitive Rules
Last modified: 16 MARCH 2022
This page contains the game-specific rules for Gamer.LK PUBGM tournaments. These rules must be followed in conjunction with the General Competitive Rules of Gamer.LK Tournaments.
GENERAL COMPETITIVE RULES AT GAMER.LK TOURNAMENTS
The General Competitive Rules can be found here. The general rules listed there apply to all gaming titles and all teams/players who register for any Gamer.LK Competitive tournament are expected to follow them.
1. TOURNAMENT BRACKET
There will be no tournament bracket involved.
2. TOURNAMENT COMMUNICATION
All teams and players are required to join the Sri Lanka PUBG Mobile Community to stay up-to-date with the latest information regarding the game and the local community.
3. PLAYER COMMITMENT
3.1. – By submitting a registration for a Gamer.LK PUBGM tournament, all 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. – Matches will be played on the mobile platform only. Emulators will not be allowed.
3.4. – Players are allowed to bring their own peripherals including headsets, battery packs, etc.
4.1. – Players must only compete on an eligible device and may not use an external device or attachment of any kind that modifies the game’s controls (e.g. bluetooth controllers, wired controllers, mouse, keyboard etc.) without the express consent of Gamer.LK Staff.
4.2. – Players must use their own mobile devices (Android/IOS). Tablets and other similar devices or emulators are forbidden.
5. PLAYER ELIGIBILITY
All player accounts should be at least level 30, any new PUBG accounts will not be allowed.
6. TOURNAMENT FORMAT
6.1. – The tournament will be held on Custom Rooms.
6.2. – Teams will be divided into groups depending on the number of registered teams.
6.3. – Groups
6.3.1. – If 24 or more teams have registered, the teams will be divided into an ideal number of groups allowing an even spreading of teams to select the final 16 teams. (total team number divided by 2,4,8,16).
6.3.2. – If 23 or less teams have registered, the teams will be added into a single group, where the top 16 teams moves to the final group. In the case where it’s the minimum number of teams, 16, they directly play the final group.
6.4. – The final lobby should only have 16 teams and these teams need to be selected equally from all the groups.
6.5. – Teams will be divided in the seeding order according to the example below. Eg: If 100 teams registered, 4 groups of 25 teams will be divided accordingly: Team 1 goes into Group 1, Team 2 goes into Group 2, Team 3 goes into Group 3, Team 4 goes into Group 4, Team 5 goes into Group 1, Team 6 goes into Group 2, etc.
7. GAMEPLAY AND PLAYER VERIFICATION
7.1. – All players need to record hand cam footage (from a third party camera or device) of all their matches in the format below, following these rules:
7.1.1. – After joining the custom lobby, the player’s face needs to be shown to the camera and the playing phone screen of the player in the lobby should be shown to the camera as well.
7.1.2. – If the player has to disconnect before the lobby starts, they have to redo the above step once they reconnect.
7.1.3. – The entire game needs to be recorded throughout with the playing phone and the player both visible on the camera (i.e. player holding the phone while they play).
7.1.4. – The player cannot leave the camera frame at any point during the game.
7.1.5. – The playing phone cannot be taken away from the camera frame during the game.
7.1.6. – At the end of the game, the playing phone screen should be shown to the camera and the scoreboard should be visible.
7.2. – The recorded hand cam footage should be kept with the player for 14 days from the end of the tournament. The Tournament Staff will request players/teams to submit their footage and the footage then needs to be uploaded and shared with the Staff.
7.3. – In the event of a dispute in a match played, the respective player will be requested to submit the relevant footage to the Tournament Staff. The player must submit their footage within 30 minutes of the request being made.
7.4. – If any player is unable to provide their recorded footage within the specified time period to the Tournament Staff, they will face disqualification from the Tournament and their team will receive a loss. Further penalties may be issued as well.
7.5. – All footage must be clear and in the requested format above. If it is found that any player has breached a rule, such as a playing phone is taken out of the camera frame, the Tournament Staff reserve the right to cancel the points in the respective match. Further penalties may be issued as well.
7.6. – Players should always maintain their personal appearance (be appropriately dressed) and refrain from making any insulting, obscene gestures or remarks and refrain from any behavior that violates the rules of the tournament and the general ethics of Esports. The Tournament Staff reserve the right to issue the appropriate penalties on any breach of the same that is evident in the recorded footage.
8. MATCH SCHEDULE
8.1. – Players are expected to be present at the exact times for their matches as announced.
8.2. – After groups are made, new players will not be added into any group.
8.3. – Gamer.LK and any Organizers will make every effort to inform players of scheduled match dates and times – but please note it is the responsibility of the players to make sure they arrive on time for their matches. Gamer.LK or any Organizer will not be responsible to inform matches to players individually or provide reminders. Not attending a match due to not being informed of the schedule is NOT an excuse.
9. GAME RULES
9.1. – Game Format
All players need to enter the PUBG Custom ID and Password to join the lobby. The custom lobby settings will be as below.
9.2. – Match Format
9.2.1. – For all qualifying rounds (until the grand finals), each group will play 3 maps (Erangel, Sanhok, Miramar).
9.2.2. – For the finals, the final group of 16 teams has to play 6 maps – each map in the map pool currently will be played exactly twice.
9.2.3. – All map randomisations by organisers need to be recorded by referees, and stored for future verification.
9.3. – Matchmaking Settings
The following matchmaking settings apply:
– Team Size: 4 players
– Game mode: Third Person Perspective (TPP)*
– Map Pool: Erangel, Sanhok, Miramar
– Server Location: Asia
– Red Zone & Flare Guns: Disabled
– Safe zone 1 display time: 80s for Miramar & Erangel, 60s for Sanhok
– ALL Weapons: x2
– Scopes and Magazines: x2
– Aim Assist And Sound Visualization: Off
* changing between TPP & FPP in the game is allowed
9.4. – Scoring
Scoring will be for each game (i.e. in a best of 3 games, all 3 games will be scored) and be based on each team’s final kill count and in-game placement as set forth below
1 kill = 1 point
9.5. – Ties
Ties between two teams will be determined in the order of
(a) Total times they won first placement or chicken dinner across tournament games,
(b) Total placement points,
(c) Total kills
(e) The placement points in the most recent match will be considered
10. GAMEPLAY RULES
10.1. – Use of restricted items during a game
Straight disqualification will be given if you are caught using an item from the banned list and the win will be automatically given to the opponent.
10.2. – 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.
10.3. – Hacking
Hacking or otherwise modifying the intended behavior of the game client is prohibited.
10.4. – Scripting
The use of scripts are prohibited.
10.5. – Use of Macros
The use of macros are prohibited.
10.6. – Use of Third Party Softwares
The use of any third-party addons, hooks, programs or wrappers that interact with or alter the client, its appearance or behaviour for the purposes of gaining an unfair advantage is prohibited.
10.7. – Impersonations
Impersonating an eligible player by attempting to alias as them, using their 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.
10.8. – In-game names
Each player must have his/her primary nickname or something very similar as his game name during all matches to be easily identifiable for referees, broadcasters, and viewers. What counts as similar is for the Tournament Staff to decide. The only additional information allowed in a player’s ingame name is clan tags or sponsor names.
10.9. – Collusion
10.9.1. – Collusion, match fixing, bribing a referee or match official, or any other action or agreement to intentionally influence (or attempt to influence) the outcome of any match or Event.
10.9.2. – Other forms of collusion include:
– Teaming: Players working together during the match
– Planned Movement: Agreement between 2 or more opposing players to move through the map in a planned way before the match begins.
– Communication: Sending or receiving signals (both verbal and non-verbal) to communicate with opposing players.
– Item Dumping: Intentionally dropping items for an opposing player to collect.
11. MATCH RULES
11.1. – Pauses
There will be no pauses in the game.
11.2. – Disconnects
Players who disconnect during a match will be able to reconnect to the game. However, the game will continue during the period.
11.3. – Technical issues
At LAN tournaments, players should raise their hand and immediately contact Tournament Staff in the event of a Technical Issue. Staff will then assist to rectify the situation and the necessary action. Failure to report issues in a timely manner may cause the issue to be disregarded by the Tournament Staff. At online tournaments, technical issues will not be considered.