Teams are formed via a snake-method draft process, following assignment of captains.
Teams play against each member of the same group. Based on the amount of sign-ups, a bracket will take place for the best teams of each group.
The ranking of the league is decided in the following order:
Amount of wins
Head to head
Signup End: Sunday November 21st 14:30 CET
Check-in Start: 14:30 CET (via Discord)
Check-in End: 15:30 CET
Draft Start: 15:30 CET
Brackets Announced: 16:30 CET
Group Stage Start: 17:00 CET
Finals Start: 21:00 CET
Teams that delay the start of a game by more than 15 minutes forfeit the first stopwatch round of the game, each subsequent 15 minutes will result in another round forfeited (Note: This does not include delays due to previous games overrunning).
Teams who continuously delay the start of matches will be removed from the event.
Matches and scoring
Matches will be played using latest version of RtCWpro (1.2.5).
Matches are 6v6 in Stopwatch Mode.
1 panzer/flamethrower/venom allowed per team.
No weapon boosting.
No intentional blocking of spawns or doors with revives.
Each team has two pauses per round.
Scoring (Entire Event): 1 point awarded per round won. If there is a double full hold no points will be awarded to either team. Teams can win a match 1-0, with one/three other rounds as Double Full Holds.
Scoreboard and console messages. Accept the console message to determine who won the round.
mp_base (10min timelimit)
mp_castle (30/20 spawntimes)
te_chateau (30/20 spawntimes & cellar door can be naded)
mp_keep (30/30 spawntimes)
mp_sub (30/20 spawntimes)
During the groupstage:
Each map will consist of an AB round
Both maps will be drawn randomly by the cup admins
Map 1will be selected from "common" base game maps: assault, base, beach, ice, village
Map 2 will be selected from "forgotten" base game maps: castle, chateau, keep, sub
During the playoffs:
Each map will consist of ABBA rounds
The teams make a cointoss on the captain discord channel, the winner is low seed, the loser high seed.
The high seed picks a map
The low seed picks a map
The decider will be drawn randomly by the cup admins
The following applies to a decider match played in case of a complete tie (0-0, 1-1, 2-2):
The decider is one round played using the AB format, low seed picks side.
In the case of a double fullhold during the decider then play another AB round on the same map, high seed picks side.
In the case of two double fullholds play another AB round on the final remaining map, the swap between low and high seed picking side continues.
Players may only play for one team.
Players must use a clan tag.
Players must not use an extremely long clan tag.
Players must use the name listed on the teams roster page.
Players must record demos and submit them if requested.
A team can play with a minimum of 5 players (IE: 5v6).
Players banned from the RTCW Discord server at the time when signups end will not be allowed to participate.
Servers and Crashes
All games should be played on the official servers provided. An admin will supply you with a server from the central server pool via the appropriate discord match channel.
If you have a problem with the assigned server for your match, please contact the admins.
If both teams agree you may switch to an 'outlier' server outside of the central pool of servers. This server must still be provided by the admin team. Please discuss well in advance if you want to switch from your assigned server.
If the admins decide you have purposely crashed the server this will result in the current stopwatch round being forfeited.
If their is a legitimate server crash restart the current stopwatch half as needed.
If a player crashes, teams can use their three pauses until the player returns (If a player substitutes in or the crashed player returns they need to /kill when rejoining)
Coverage & caster rules
Your team does not have the right to refuse match casting/streaming*. If a caster is available and you agreed beforehand, casters can jump in your comms. No Discord voice channel will be enforced to you.
Casters who jump in to an on-going match, must have their mic muted beforehand and must avoid disturbing the team at all costs. Casters who do not follow this rule can be reported and then potentially removed.
Players are allowed to stream their own comms and POV.
Streamers and casters need to have at minimum a two minute delay for casts to be allowed.*
* Refusing to do so will result in penalties that are at the discretion of the admin team.
Exploits & external applications
Weapon boosting is forbidden. However, accidental/incidental boosting does occur and it is legal. However, if a team feels that an "accidental boost" was intentional, they may contact the admins who will review the case.
On mp_village, the documents ARE NOT allowed to be passed on through the gate located near allied bridge/spawn. Doing so results in a forfeit of the round.
One panzer per team at one time. Player who spawns with a panzer is the only one who can shoot the panzer. No panzer swapping is allowed.
On mp_beach, teleporting through the floor/sinking into the ground near the basement barracks is ILLEGAL. Using this tactic will result in an immediate round loss.
Document duplication glitch: In the rare event that the documents become duplicated on any map, you are NOT allowed to transmit the fake documents to complete the round. Doing so will result in an immediate round loss. Utilizing a pause as soon as this happens to straighten out the situation is highly recommended.
If your team has a question about the legality of a possible tactic or exploit, contact an admin as soon as possible to avoid being penalized. If a player/team is found guilty of using an exploit that gained an obvious advantage, "It wasn't explicitly stated as being an exploit in the rules", "I/We didn't know," and "Everybody else is doing it," are NOT valid excuses. Spending an inordinate amount of time searching for the next undocumented exploit that gains your team an advantage in a match will almost certainly result in a penalty/forfeited round.
The usage of any external applications or devices is strictly forbidden (external mouse button controls are allowed). Players caught using one of these will result in a ban and possible team disqualification.
Config "RTCW20th" must be in place (DOWNLOAD v0.2 HERE > add to your /Main folder > when in-game exec rtcw20th):
r_gamma 1.3 - 2
r_intensity 1 - 1.5
r_picmip 0 - 1
Optional, but recommended
All games must be played with the "anniversary" config loaded (/callvote config anniversary)
The admins reserve the right to modify the following rules as necessary. Teams should check the rules on a regular basis and prior to every match to ensure they are in complete compliance. Rules are marked with an update date and we provide a log of changes to assist in this capacity. These rules are guidelines by which the this group of tournaments operate to ensure a fun and even playing field for all teams. At all times, these rules are subject to interpretation by admins. While our cup strives to provide the most comprehensive rules possible, not every scenario can be anticipated. Those matters are left to admin discretion based on the spirit of these rules and the situation at hand. Remember, this is just a game and good sportsmanship should be displayed at all times throughout the cup.
By participing to this event, all players on a roster agree to all rules above.
Common Sense Clause
All participants are expected to adhere to the highest standards of sportsmanship and ethical conduct. Examples of non-sportsmanlike behavior include, but are not limited to: Excessive use of profanity, insulting or rude behavior to anyone connected to the server, at any time. Failure to follow the instructions of a Referee or Tournament Official, publicly flaming or otherwise harassing, insulting, or excessively arguing with any person participating or connected to the tournament, in any forum or venue whatsoever, where the subject of the exchange is related to the activities of the tournament itself, will not be tolerated and are grounds for removal from the tournament.
18/11/21 - Added clarification on adjusted spawntimes for some maps & instructions on executing config (Adlad)
16/11/21 - Final updates published (Adlad)
15/11/21 - Initial ruleset published (Adlad, Graecos)