The goal of the Major is to bring together the best Counter-Strike players in the world to a LAN setting, provide them an opportunity to claim their title, and to demonstrate to millions of CS players around the world just how high the Counter-Strike skill ceiling is.
This document does not contain all of the rules of the tournament; only the ones we require to be uniform across all Major events. For the complete body of tournament rules for your event, contact the tournament organizer.
What is expected of tournament organizers with respect to this document.
The Tournament Organizer ("TO") will include this document in its tournament rules. Event admins are expected to be familiar with the contents. Any conflict between these and other tournament rules are to be resolved prior to the publication of the event rules.
These are the main deliverables outlined in this document that are required of the TO, along with their due date (relative to the start of the event).
| Deliverable | Due | MRQ | Major |
|---|---|---|---|
| Final Rosters | Start | ✔ | |
| Agreements | Start | ✔ | |
| CoI Disclosures | Start | ✔ | |
| Server Demos | End | ✔ | |
| Mugshots | End | ✔ |
Rules and procedures for determining who is to participate in the events.
The Major features 32 teams
- 16 teams are invited to Stage 1 from the Major Regional Qualifiers.
- 8 teams are invited to Stage 2 based on Valve Regional Standing.
- 8 teams are invited to Stage 3 based on Valve Regional Standing.
Invitations are allocated according to the number of teams from the region that earned their respective position in the Major:
- One Stage 2 invitation is assigned to the region for every team of that region that reached Stage 3 of the previous Major.
- One Stage 3 invitation is assigned to the region for every team of that region that reached the Playoffs of the previous Major.
Top teams that have not been invited to Stage 2 or Stage 3 are invited to their region's respective Major Regional Qualifier (MRQ), with the following distribution:
| Region | MRQ Invitations | Stage 1 Invitations |
|---|---|---|
| Europe | Next 16 from VRS | 6 |
| America | Next 16 from VRS | 6 |
| Asia | Next 8 from VRS | 4 |
| Total | 40 | 16 |
Major Invites for Summer 2025 based on performance of regions in Winter 2024:
| Region | Stage 1 | Stage 2 | Stage 3 |
|---|---|---|---|
| Europe | 6 | 4 | 6 |
| America | 6 | 4 | 1 |
| Asia | 4 | - | 1 |
| Totals | 16 | 8 | 8 |
Teams in each world region are sorted via Valve Regional Standing (VRS). The three VRS regions are EU, Americas, and Asia, and these three lists are used for the purposes of invitation. A global version of the VRS is used only for the pre-event seeding of stages, after invitations have been accepted.
If a team is invited to participate in a stage of the event based on their Regional Standing, at least three out of the five members of the core roster (the five players indicated in the Regional Standing) must accept the invitation, otherwise the invitation will be extended to the next-highest ranked roster in the region.
A team’s region is determined by the citizenship of the majority of its players. In case of a tie, the team chooses between the two. In the case of players that don't belong to one of the 3 regions (Europe, Asia, Americas), those players can assign themselves to a region already represented on the roster. If all players are from another region, then they can choose any region.
Invitations will be sent to intact teams, per the invitation requirements above.
If a team declines an invitation, or is no longer intact, the next-highest ranked team receives their invitation. If there are no additional teams available, then the remaining slots are to be determined by a last-chance regional qualifier.
- Team roster must include 5 players ("Core Lineup").
- Team roster may optionally include 1 coach.
- Team roster may optionally include 1 substitute player that, were they to replace any core player, would not alter the Regional Assignment of the Core Lineup.
- The coach and substitute may be the same person.
A team cannot adjust their Core Lineup between the MRQ and the Major. However, they can register a different coach or substitute player.
The TO needs to collect the following of all registered participants and deliver them to Valve (Excel or CSV).
- Team
- Position (player, sub, or coach)
- Full name
- Nickname
- Date of birth
- Country of citizenship
- SteamID
- Steam Workshop autograph item link
The TO must inform participants that this information will be transferred to Valve.
New players' nicknames are to be registered and represented as they are commonly known in third party esports media (e.g., hltv and liquipedia). Players that have previously registered for a Major event and are using the same Steam account are to use their previously registered nicknames.
Team names and logos are to be registered and represented as they are commonly seen in their own media and in third party esports media.
If there are multiple teams whose commonly known names share the same title sponsors, only one of them may use the title sponsor at the event.
Players and teams are required to accept the following agreement (verbatim) in order to participate in the event. The TO will distribute (physically or digitally) and collect signatures or equivalent from all registered participants and team representatives and deliver them to Valve. The acceptance must be legally binding (e.g., valid signatures).
1. Rights Release
1.1 (a) “CS” means Counter-Strike, and future versions thereof. (b) “Likeness” means my appearance, performance, name, biographical information, and statements, and any audio or video depiction produced by me (i) during the CS event, or (ii) provided by me or my team to Valve Corporation (“Valve”) or the event operator. With respect to a team, Likeness also includes team trademarks, logos, or other team intellectual property that the team may decide to provide Valve or the event operator outside of the CS Workshop.
1.2 I agree that Valve may use, distribute, and display my Likeness (a) in CS, or (b) in media relating to CS or to a CS event that Valve licenses or sponsors. I agree that Valve will retain these rights for so long as I continue to participate in CS events. I also agree Valve may retain these rights to use, distribute and display my Likeness related to historical CS events forever.
1.3 I agree that Valve has no obligation to submit to me any material using my Likeness for any further approval and that Valve may edit my Likeness as Valve deems reasonable for the uses permitted by paragraph 1.2. However, Valve is not obligated to make any use of any of the rights set forth in this agreement.
1.4 To the extent Valve and I separately agree to terms governing my Likeness depicted in a submission to the CS Workshop, the agreement(s) regarding the Workshop will apply to the Workshop submission instead of this agreement.
1.5 I warrant and represent that this release does not in any way conflict with any existing commitment on my part. Each team also warrants and represents that its players may make this without any conflict with any existing commitment on to the team or by the team.
1.6 I agree that my promises are intended to have lasting effect as described in paragraph 1.2. The promises in this agreement will bind and benefit any heirs, successors and assigns of me or Valve.
2. Conflicts of Interest
2.1 Teams and players should not have any financial interest in the success of any team that they are competing against. To participate in this Tournament, players and teams are required to affirm that they have no conflict of interest (including any business entanglement such as shared management, shared ownership of entities, licensing, and loans) with any other participating team or its players.
2.2 I am not currently aware of any conflict of interest that I might have with another participating team or any player on another participating team. If I currently have a conflict of interest or become aware of one over the course of the event, I will immediately provide detail to the CS development team explaining the nature of my relationship with the other party, and a plan for resolving the issue in the future.
The TO is to collect any Disclosures of Conflicts of Interest that result from registration and make them publicly available.
The TO needs to provide Valve with player avatar images for all participating players.
- Images are to be head shots with a dark background; 512x512 PNGs.
- Images are to be named as the player's Steam ID (e.g., 12345678901234567.png)
The TO will not qualify, nor allow in any qualifying event, any player who has been "Valve Anti-Cheat" banned ("VAC Banned") in CS. Any player who is VAC Banned on any of their accounts must be approved in writing by Valve in order to be eligible to participate in the event. Any team on which a banned player has played during the period starting with the first qualifier and ending with the end of the event, will be banned ("Banned Team"). Valve also reserves the right to disqualify any player, team, broadcaster, commentator, or producer in its sole discretion. The TO will immediately disqualify such person or team upon notice from Valve. Any event winnings by such player or such Banned Team will be forfeit. No player from a Banned Team will be eligible to compete in the event with any other team.
Individuals (including coaches) that are prohibited from participation in the event are not to be employed or partnered with the TO for the event (including streaming partners). Nor are they to have access to team/staff-only areas.
Rules, procedures, and definitions that pertain to the format and structure of the competition.
- Stage 1
- Swiss bracket
- 16 Teams
- Stage 2
- Swiss bracket
- 16 Teams
- Stage 3
- Swiss bracket
- 16 Teams
- Playoffs
- Single elimination bracket
- Top 8 from Stage 3
The MRQ requirements are as follows:
- Each region will hold one Major Regional Qualifier.
- The MRQ may be held online.
- If a region must be subdivided to accommodate ping of participating teams (e.g., AMER -> NA and SA), Major invitations will be split evenly among the regions. If invitations cannot be evenly split, the remaining invitation(s) will be granted to the subdivided qualifier featuring the team with the highest Regional Standing.
- All teams in the MRQ will be invited directly based on their Regional Standing. If it is not practical to fill all closed qualifier positions via Regional Standings, the TO may supplement with open qualifiers.
The MRQ format for a region is determined by the number of Major slots for that region. The formats are as follows:
- For 3 and 4 invitations, 8 teams are divided into two GSL groups:
| Group A | Group B |
|---|---|
| 1 | 2 |
| 4 | 3 |
| 5 | 6 |
| 8 | 7 |
| Opening Matches |
|---|
| 1 v 5 |
| 2 v 6 |
| 3 v 7 |
| 4 v 8 |
All matches are best of 3.
-
For 3 Invitations (e.g., NA/SA split):
- Teams with 2-0 record advance.
- Teams with a 1-1 record play the following matches:
- Highest seed from A faces lowest seed from B
- Highest seed from B faces lowest seed from A
- Teams with 2-1 record play and the loser is eliminated.
-
For 4 Invitations (Asia):
- Teams with 2-0 record advance.
- Teams with 1-1 record play the following matches:
- Highest seed from A faces lowest seed from B
- Highest seed from B faces lowest seed from A
- Teams with 2-1 record advance.
-
For 6 Invitations (Americas, Europe): 16 team Swiss bracket
Decider matches (Advancement or Elimination) are best of 3. All other matches are best of 1.
- Teams with 3-0 record advance.
- Teams with 3-1 record advance.
- Teams with 3-2 compete for 1 spot:
- The three 3-2 record teams are first sorted by difficulty score.
- The lower two teams play a best of 3 and the loser is eliminated.
- The remaining two teams play a best of 3 and the loser is eliminated.
- Teams play against opponents of identical W-L record.
- Three wins advance---Three losses eliminate
- All elimination and advancement matches are to be best of three.
- All other matches are to be best of one.
- Teams are not to play the same opponent twice in the same stage, if possible.
- Match-ups shall be determined by seed. The first round follows the Initial Match-ups. In round 2 and 3, the highest seeded team faces the lowest seeded team available that does not result in a rematch within the stage. In other rounds, refer to the following table and select the top-most row that does not result in a rematch:
| Priority | |||
|---|---|---|---|
| 1 | 1v6 | 2v5 | 3v4 |
| 2 | 1v6 | 2v4 | 3v5 |
| 3 | 1v5 | 2v6 | 3v4 |
| 4 | 1v5 | 2v4 | 3v6 |
| 5 | 1v4 | 2v6 | 3v5 |
| 6 | 1v4 | 2v5 | 3v6 |
| 7 | 1v6 | 2v3 | 4v5 |
| 8 | 1v5 | 2v3 | 4v6 |
| 9 | 1v3 | 2v6 | 4v5 |
| 10 | 1v3 | 2v5 | 4v6 |
| 11 | 1v4 | 2v3 | 5v6 |
| 12 | 1v3 | 2v4 | 5v6 |
| 13 | 1v2 | 3v6 | 4v5 |
| 14 | 1v2 | 3v5 | 4v6 |
| 15 | 1v2 | 3v4 | 5v6 |
Match-ups for the first round of the Swiss format are as follows:
| Swiss Round 1 |
|---|
| 1 vs. 9 |
| 2 vs. 10 |
| 3 vs. 11 |
| 4 vs. 12 |
| 5 vs. 13 |
| 6 vs. 14 |
| 7 vs. 15 |
| 8 vs. 16 |
- Bracket A:
- 1 vs. 8
- 4 vs. 5
- Bracket B:
- 2 vs. 7
- 3 vs. 6
- All matches are best of three
All Major and MRQ events are to use the following map pick-ban process for determining which map (bo1) or maps (bo3) are played.
- The higher seed team chooses to be Team A or Team B
- Team A removes 2 maps
- Team B removes 3 maps
- Team A removes 1 map
- Team B chooses starting side
- The higher seed team chooses to be Team A or Team B
- Team A removes 1 map
- Team B removes 1 map
- Team A picks the map 1
- Team B chooses starting side on map 1
- Team B picks map 2
- Team A chooses starting side on map 2
- Team B removes one map
- Team A removes one map
- Team B chooses starting side on map 3
Coming into the event, all 32 teams are sorted based on their current global standing in the VRS.
-
Stage 1:
- All teams will use their pre-event seed.
-
Stage 2:
- The teams directly invited to this stage will be seeds 1-8, and use their pre-event seed.
- The advancing 8 teams will be seeds 9-16 and use their final seed from the previous stage (see Mid-stage Seed Calculation).
-
Stage 3:
- The teams directly invited to this stage will be seeds 1-8, and use their pre-event seed.
- The advancing 8 teams will be seeds 9-16 and use their final seed from the previous stage (see Mid-stage Seed Calculation).
-
Playoffs:
- All teams will use their final seed from Stage 3 (see Mid-stage Seed Calculation).
For all Swiss match-ups, after the initial matches, seed is determined (in order) by:
- Current W-L record in the stage
- Difficulty Score in the current stage
- Initial seeding of the current stage
Each team's Difficulty Score is tracked for the purpose of tie-breaking.
The Difficulty Score is the sum of current wins minus the sum of current losses for every opponent a team has faced.
Team A's prior opponents are 2-0 and 1-1. Team A's Difficulty Score is 2 (prior opponents have 3 wins total, and 1 loss total, so 3-1 = 2)
Team B's prior opponents are both 1-1. Their Difficulty Score is 0 (prior opponents have 2 wins and 2 losses in total, so 2-2 = 0)
Therefore, if both Team A and B have the same win-loss record, Team A gets the higher seed because it played against teams that were more difficult to defeat.
Requirements that pertain to the technical setup, configuration, and execution of the MRQs and Majors.
The TO is to use the up-to-date in-game versions of the maps in the Active Duty Map Group.
Players can have workshop maps on their competition machines provided that
- The workshop map was downloaded directly from the workshop by an event admin.
- The workshop map has a minimum of 100k (one hundred thousand) subscribers.
- The game is restarted in the presence of an admin before the competition match begin.
- Game art and sound are not to be modified on player or observer clients.
- Augmented reality (AR) elements are not to be designed to pretend to be a part of the game world.
- Augmented reality (AR) elements are to only ever present useful information (e.g. player statistics).
- Any sponsorship in AR attached to the above needs written approval by Valve.
- Players' access to their inventory should not be modified or augmented.
Competition PCs are to have no internet access aside from what is minimally required to log in to Steam and CS and run the game.
-
Block access to everything and allow only UDP traffic to AS32590 blocks (http://bgp.he.net/AS32590#_prefixes) to avoid any content hosted on 3rd party sites from getting onto the tournament machines. Blocking all non-UDP traffic, primarily TCP access, even to our AS32590 blocks is also required, because our IP ranges still deliver game content, and malicious participants can have game content masquerading as different appid on Steam Greenlight, Early Access, or the Workshop.
-
Have the tournament LAN ports 27015-27050 open for TCP and UDP to Valve network AS. This will just allow WebSocket connections to be used for logon traffic.
-
Ideal implementation will be proactively dropping non-UDP connections with TCP resets or similar low-level packets sent to initiating clients, which should hopefully help the client timeouts to be reasonable (as opposed to blackholing outgoing traffic and forcing the client to be stuck waiting for prolonged periods of time).
-
Set the player machines to use local host (127.0.0.1) for DNS, otherwise players will experience stalls while trying to reach an external DNS due to the network restrictions.
Competition PCs are to be secured and managed by event staff and restricted down to what is minimally required to log in and run the game.
- Provide each player a unique SSD that remains in the possession of the TO and only used by players while supervised.
- The SSD image must be created using a Steam account with access to all game depots including Chinese audio localization files by Perfect World and other Perfect World assets that are required for players using their Steam accounts linked to Perfect World accounts.
- Let us know the Steam account you will be using to author the SSD images and we will add correct licenses to your Steam account so that you could download all the required assets. Without the correct licenses some players will be unable to launch the game because network restrictions will be blocking downloads of missing assets.
- Create non-admin Windows account for players and do not distribute admin credentials or access.
- Set the entire Steam folder to Read-Only access with the exception of the \Steam\logs\ folder which will need write access to update the log files.
- Create a directory “C:\configs” on each machine and define a system global environment variable USRLOCALCSGO with the value of that directory “C:\configs” (or if each player has their own Windows account that environment variable can have path pointing at player’s roaming profile subdirectory). Players can copy their config.cfg into C:\configs and the game will load and save configs there so you won’t need administrator rights for players to change configs, and Steam CS install can remain read-only.
- Collect a list of required peripheral drivers from players and download them directly from the manufacturer.
- USB mass storage devices and similar devices should be disabled using the following instructions:
- Start > Run > gpedit.msc
- Local Computer Policy > Computer Configuration > Administrative Templates > System > Removable Storage Access
- Enable the deny rules for all of the entries except for Custom Classes.
- Setup disk auditing so you can see all changes made to the disk by the player
- Setup AppLocker
- Application Identity Service (AppIDSvc) must be started for AppLocker to work properly. Recommend setting it to automatic.
- Go to Applocker and create default rules then delete the allow program files rule.
- Set allow rules for the following (can be set for the everyone group or the Windows user players will be using):
- Steam.exe
- csgo.exe
- any other applications players will need access to such as VOIP (note that these applications may be blocked from making config file changes on the limited Windows user account so prepare the configs ahead of time from the admin account)
- Set Deny rules for the following (can be set for the everyone group or the Windows user players will be using):
- powershell.exe
- cmd.exe
- cscript.exe
- In the BIOS set a password then enable Secure Boot, set boot to UEFI only, remove all boot devices other than the OS drive (specifically make sure USB boot is not an option), and enable VT-d if the hardware supports it.
Setting up auditing rules should be done on player machines so if a player is called into question there are records of actions taken on the machine. It should be noted that on some hardware this could potentially cause performance issues so once auditing rules have been set the machines should be tested and benchmarked to ensure that the game will still run smoothly.
-
Enter the following commands into an elevated command prompt:
- auditpol /set /user:proplayer /category:* /success:enable
- auditpol /set /user:proplayer /category:* /failure:enable
NOTE: Make sure the /user:proplayer is changed to reflect the account name the players will be using.
- The clock on player machines should also be set to synchronize with an internet time server to ensure the time stamp on the events is accurate.
Clients should have the following convars set as such:
cl_invites_only_mainmenu 1
cl_invites_only_friends 1
- Server may run eBot.
- For any other server mod, the TO will obtain approval in writing from Valve.
- Confirm that server is recording demos. Demos are to be delivered to Valve.
All server convars are to be set to Premier defaults (by first loading cfg/gamemode_competitive.cfg and then loading cfg/gamemode_competitive_tmm.cfg) except for the following exceptions.
- The following convars are to be set as such:
tv_enable 1
tv_enable1 1
tv_dispatchmode 0
sv_maxusrcmdprocessticks 3
sv_max_dropped_packets_to_process 3
tv_broadcast 1
tv_allow_autorecording_index 0
sv_steamauth_enforce 1
mp_autokick 0
sv_matchend_drops_enabled 0
sv_damage_print_enable 0
sv_reliableavatardata 2
sv_invites_only_mainmenu 1
mp_spectators_max 10
sv_matchpause_auto_5v5 1
sv_clockcorrection_msecs 0
mp_overtime_limit 0
mp_warmup_pausetimer 1
mp_warmuptime 60
mp_halftime_pausematch 1
mp_competitive_endofmatch_extra_time 155
mp_warmuptime_all_players_connected 0
sv_spec_hear 4
tv_relayradio 0
sv_vote_allow_spectators 1
sv_vote_issue_loadbackup_spec_only 1
sv_vote_issue_loadbackup_spec_authoritative 1
sv_vote_issue_pause_match_spec_only 1
sv_vote_creation_timer 25
sv_vote_failure_timer 25
sv_occlude_players 0
sv_force_transmit_players 1
sv_force_transmit_ents 1
sv_holiday_mode 0
cash_team_bonus_shorthanded 0
game_mode 1
game_type 0
log on
mp_logdetail 3
mp_logdetail_items 1
mp_logmoney 2
sv_gameinstructor_disable 1
sv_invites_only_mainmenu 1
tv_allow_camera_man_steamid <STEAM_ID_OF_OBSERVER>
- The following convars can have any value:
mp_disconnect_kills_players
mp_do_warmup_period
mp_halftime_pausetimer
mp_overtime_halftime_pausetimer
mp_win_panel_display_time
occlusion_test_async
spec_replay_enable
sv_allow_votes
sv_allow_wait_command
sv_dc_friends_reqd
sv_forcepreload
sv_hibernate_postgame_delay
sv_hibernate_when_empty
sv_kick_ban_duration
sv_kick_players_with_cooldown
sv_lan
sv_load_forced_client_names_file
sv_max_queries_sec
sv_maxcmdrate
sv_maxrate
sv_maxuptimelimit
sv_memlimit
sv_mincmdrate
sv_minrate
sv_pausable
sv_pure_kick_clients
sv_pure_trace
sv_server_graphic1
sv_server_graphic2
sv_steamgroup
sv_steamgroup_exclusive
sv_voiceenable
sv_vote_quorum_ratio
sv_vote_timer_duration
tv_advertise_watchable
tv_allow_static_shots
tv_autorecord
tv_broadcast_origin_auth
tv_broadcast_url
tv_chatgroupsize
tv_chattimelimit
tv_debug
tv_delay
tv_delay1
tv_delaymapchange
tv_deltacache
tv_maxclients
tv_maxrate
tv_name
tv_overridemaster
tv_relay_whitelist_cidr
tv_timeout
tv_title
tv_transmitall
Servers must be configured to submit logs in order for the match results to present in the client to all users.
- Provide Valve the Steam ID of the account ("Admin") that will be setting and submitting the match logs in order to enable the Control Room.
- Provide Valve a Web API key for the Admin account. If you don't have one, create one here.
Below is a step-by-step test to confirm that GOTV and caster camera/audio are working correctly.
-
Get a vanilla CS game server install using SteamCMD >> app_update 740 validate.
-
Create your game server login token for CS AppID 730 at: https://steamcommunity.com/dev/managegameservers
-
Launch the game server using bash on Linux
./srcds_run -debug -game csgo -console +game_type 0 +game_mode 1 +mapgroup mg_dust247 +map de_dust2 -tickrate 128 +sv_setsteamaccount TOKEN_FROM_PREV_STEP +tv_enable 1 -ip 10.10.10.12 -
On the game server enable GOTV camera man SteamID (and optionally set a shorter TV delay for testing):
sv_spec_hear 4 tv_delay 7 tv_allow_camera_man_steamid STEAM_ID_OF_OBSERVER (optionally start GOTV+ broadcast upload) -
Connect players to the game server:
- one player connect CT (connect XX.XX.XX.XX:27015)
- tester connect to the GOTV port (connect XX.XX.XX.XX:27020) or start watching playcast
-
Run the game on observer computer with -interactivecaster launch option
-
Connect observer's game to the server as spectator (connect XX.XX.XX.XX:27015, then press 'M' to switch to spectator, will appear on the scoreboard as 'SPEC')
- Note that the game server will print the following line when your cameraman connects:
Adding ID:XXXXXXXX to active caster list!
- Note that the game server will print the following line when your cameraman connects:
-
Verify on the game server that players are connected as expected:
statusmap : de_dust2 gotv[0]: port 27020, delay 7.0s, rate 32.0 userid name uniqueid connected ping loss state rate adr 2 1 "Player1" STEAM_1:1:XXXXXXX 11:35 14 0 active 786432 X.X.X.X:27005 7 "GOTV" BOT active 32 10 3 "Player2" STEAM_1:0:XXXXXXX 07:11 17 0 active 786432 X.X.X.X:27005tv_status--- GOTV[0] Status --- Online 11:01, FPS 128.0, Version 8378 (Linux) Master "GOTV", delay 7, rate 32.0 Game Time 10:54, Mod "csgo", Map "de_dust2", Players 2 Local Slots 128, Spectators 1, Proxies 0 userid name uniqueid connected ping loss state rate adr 2 1 "Viewer1" STEAM_1:1:3 07:37 35 0 active 196608 X.X.X.X:27005 -
GOTV viewer should enable caster camera control and caster voice via scoreboard
-
Observer should start switching camera and narrating the action
-
GOTV viewer in our test sees camera switching and caster's in-game voice narration matching the camerawork
Rules and procedures that pertain to the active administration of the tournaments.
Each team can substitute a player with their registered substitute once during the event.
- A team may make a substitution in-between matches for any reason.
- A team may make a substitution during a match or in-between maps only in the case of a medical emergency.
- Once a substitution has been made, the team can continue to play with the substitute player until they choose to revert to their Core Lineup.
- The substitution rules above apply if a team chooses to revert to their Core Lineup.
- Once the team reverts to the Core Lineup, it may not substitute again for any reason and must play shorthanded or forfeit if the situation arises.
The TO will prevent players from bringing any electronics (e.g., pagers, cell phones, etc.) aside from permitted gaming peripherals (mouse, keyboard, etc) to the competition area by employing a metal detector security detail at the entrance.
Any other items players wish to bring on stage must be inspected by the TO staff.
Aside from the TO staff, only the five players and the team's pre-registered coach are permitted in the competition area during event matches.
Coaches are not to communicate with (i.e., be seen, heard, or felt by) the players by any means at any time with the exception of warmup, half-time, and tactical timeouts.
Coaches that wish to call a timeout are to do so by notifying an admin.
In the case of any matches where event admins are not physically present (e.g. online matches), no team staff, including the coach, may be physically or virtually present or communicate with the players at any time during the match.
Servers must be configured to submit logs and data is to be entered for each match.
- Provide Valve the Steam ID of the account ("Admin") that will be setting and submitting the match logs in order to enable the Control Room.
- Provide Valve a Web API key for the Admin account. If you don't have one, create one here.
- Launch CS from the Admin account, click on Watch, and then click on Control Room button.
- Fill out the stage, teams and map for the match about to be played. We suggest formatting the match password as follows:
teamname1-vs-teamname2-stage-1-of-3-map - On the server the match is to be played on, set the following convars.
log on
mp_teamname_1 <Team Name 1>
mp_teamname_2 <Team Name 2>
logaddress_token_secret <match password>
logaddress_add_http <Valve supplied URL>
Return to the Control Room and click the SAVE FINAL SCORE button. This will close out the match in the game for all users and allow them to claim souvenirs.
Obligations that pertain to the completion of the tournaments.
Final Major Rankings are determined by (in order)
- Position in Playoffs
- Stage 3 W-L record
- Stage 3 Difficulty
- Stage 2 W-L record
- Stage 2 Difficulty
- Stage 1 W-L record
- Stage 1 Difficulty
- Initial Seeding
| # | Team | Position | W/LL | DL | W/LC | DC | Initial Seeding | Next Major Invitation Earned |
|---|---|---|---|---|---|---|---|---|
| 1 | Team Spirit | Major Champion | EUR Stage 3 |
|||||
| 2 | FaZe Clan | Grand-finalist | EUR Stage 3 |
|||||
| 3 | G2 Esports | Semi-finalist | 3-1 | EUR Stage 3 |
||||
| 4 | MOUZ | Semi-finalist | 3-2 | EUR Stage 3 |
||||
| 5 | The Mongolz | Quarter-finalist | 3-0 | 4 | ASIA Stage 3 |
|||
| 6 | Team Vitality | Quarter-finalist | 3-0 | -4 | EUR Stage 3 |
|||
| 7 | Team Liquid | Quarter-finalist | 3-1 | AMER Stage 3 |
||||
| 8 | HEROIC | Quarter-finalist | 3-2 | EUR Stage 3 |
||||
| 9 | FURIA Esports | - | 2-3 | 6 | AMER Stage 2 |
|||
| 10 | MIBR | - | 2-3 | 3 | AMER Stage 2 |
|||
| 11 | Natus Vincere | - | 2-3 | 2 | EUR Stage 2 |
|||
| 12 | GamerLegion | - | 1-3 | 1 | EUR Stage 2 |
|||
| 13 | 3DMAX | - | 1-3 | 0 | EUR Stage 2 |
|||
| 14 | paiN Gaming | - | 1-3 | -5 | AMER Stage 2 |
|||
| 15 | Wildcard | - | 0-3 | 1 | 3-2 | -1 | AMER Stage 2 |
|
| 16 | BIG | - | 0-3 | 1 | 3-2 | -3 | EUR Stage 2 |
|
| 17 | FlyQuest | - | - | - | 2-3 | 6 | ||
| 18 | Passion UA | - | - | - | 2-3 | 4 | ||
| 19 | Complexity Gaming | - | - | - | 2-3 | -6 | ||
| 20 | Virtus.pro | - | - | - | 1-3 | 1 | 10 | |
| 21 | Cloud9 | - | - | - | 1-3 | 1 | 19 | |
| 22 | Rare Atom | - | - | - | 1-3 | -1 | ||
| 23 | Imperial Esports | - | - | - | 0-3 | 3 | ||
| 24 | Fnatic | - | - | - | 0-3 | -3 |