GetQuad! Kenya Invitational 2/Rules

• Overview
• Information
• Rules

Format and rules

• The tournament consists of 10 teams that have been placed in 2 groups of 5 teams each - round robin structure.
  
  
• The teams have been set up by admins and players.
  
  
• Each team plays each other once in a standard Bo3 game.
  
  
• Points are awarded based on match wins, 1 point per match win.
  

• If teams are equal in the table on match wins:
  

Then map difference + - (net maps) will separate the teams.
-If teams still can not be separated:
Then positions will be decided based upon their internal fight.
-If 3 or more teams are still equal and they have all beaten each other:
Then the map difference + - in those internal fights will decide.
-If still equal:
The frag difference in those internal fights decide.
-If that is also equal:
-Then the total frag difference of all games decide.

• Top 4 teams in each group advance to playoffs: quarterfinals.
  

• Groupgames (round robin) are best of 3 maps.
  

• Playoffs are best of 5 maps.
  

Map pool and picking process

obsidian	rock	anwalk
BO3: Group play For the first two maps, teams pick whatever map they want to play, regardless of what the other team picks. - Select first map picker team using: "/cmd rnd team1 team2" - winner picks the first map, other team picks the second map. - If 1-1 after 2 maps and teams do not agree on decider map: If both teams selected the same map, that map is also the decider. If the teams did not select the same map, then the remaining unpicked map from the pool is the decider. - The team who reaches 2 map wins first wins the game. BO5: Playoffs You play all 3 maps first. Select first map picker team using: "/cmd rnd team1 team2" - winner picks first - The team down 1-2 picks 4th map. The team up 2-1 picks 5th map. The 4th and 5th pick can be any map you want, so in theory a map can be played 3 times in a full Bo5 (if pick 4 and 5 are the same). - The team who reaches 3 map wins first wins the game.

Team Restrictions / Standins

• Team Poland must use at least one "div2 player" on every map. We have defined their players like this:
  

Div1: Insane - Tom - Blassy - Shamoth - Macler
Div2: Ponczek - Riki - Grl - Maks
If the other team agree, Poland do not have to use a "div 2" player.

• Players can be replaced - permanent or temporary - as long as their replacement are of "equal skill". Admins will decide this along with the players.
  
• Standins are dynamic and can play for several teams.
  
  • Any standin for any game has to be approved by the admins, unless both teams agree that it is ok and you can play on; just inform the admins after the game.
    
  • The standin pool consist of late signers, that missed the deadline or people can volunteer to be placed on it.
    
  • Admins will always attempt to ensure that the standin is suitable as a replacement
• Admins will not force a standin on a team.

Timeframe / Schedule rules

• All matches will have a deadline (sundays) and teams should be active in communicating with each other and schedule their games.
  

- This communication has to be done in the divisions scheduling channel.
- Once a match has an agreed upon time - this needs to typed into the #schedule channel.

• Each match has a one week window in which it can be played.
  
• If a team is idling or deemed by the admins to not be making an effort to produce the game it will be considered as if the offending team forfeits the match, and a Walk Over (WO) shall be awarded to the opposition.
• A Walkover will result in victory to the beneficiary, and 0 points to the offending team.
• A match can be delayed maximum 1 week. That means it must be played the following week.
• Any match can be played earlier than its scheduled week.

Ping

• The primary driver for server selection is to find a server where the teams have similar average pings (+/- 2ms) and to minimise that average.
• The pings should be the most even for the 2 teams and measures like cl_delay_packet or proxy rerouting to balance pings should be employed. A team with a higher average ping than their opponent on a given server may request the opponent to do this (or change server to somewhere with lower average ping).
• Matches must be played on the servers of the continent were the competition is being held.
• The maximum min-ping that can be required is 52ms. This may occasionally mean matches played with uneven pings where one team has high pinging players e.g. NA players on EU server.
• This process applies for every map played. Where lineup changes are made between maps it may become necessary to switch servers or adjust pings at the request of either team to rebalance pings.
• Servers that are providing significant packetloss that cannot be avoided by proxy rerouting should generally be avoided unless both teams agree to play there.
• If players still can't agree on a server, please contact admins about it. Admin decision is final and refusal to play on a server designated by neutral admins will be considered a WalkOver loss.

Server Settings

• Timelimit: 20 minutes
• Overtime: 5 minutes if match is a draw
• Deathmatch mode: 1
• Teamplay mode: 2
• Spawn mode: KTX2 Respawns
• Powerups: ON
• Discharge: ON
• KFjump: Toggled OFF (command = tkfjump)
• Airstep: OFF
• Jawnmode: OFF
• Antilag (or equivalent): ON (unless both teams agree to play without it.)
• Fallbunny: ON (if server allows)
• No berzerk, midair, instagib or other unusual modes.
• If a team requests nospecs-mode, the other team is obliged to comply.
  
  

These should be the basic 4on4 settings on all modern servers, but make sure to check if you are unsure.

Match Reporting

• The team that wins the match should report the match.
  

- Reporting of the match is done through the GetQuad website.

• In order for a match to be valid you'll need to have screenshots from each played map
• If for any reason match cant be reported, save demos and give them to admins.

Allowed clients

• EzQuake 3.2.2. (https://github.com/ezQuake/ezquake-source/releases/tag/3.2.2)
  • Also allowed any pre-releases, alpha and beta versions above 3.2.2.
• EzQuake 3.5-alpha18 and higher (latest here: https://github.com/meag/ezquake-source/releases/tag/3.5-alpha24, at the bottom of the page)
• EzQuake 3.6-x (latest here: https://github.com/ezQuake/ezquake-source/releases/tag/latest, at the bottom of the page)

• You play with pre-releases, alpha and beta versions at your own and your teams risk - crashing mid game or otherwise being unable to play if you are playing on one of these: Is not a valid excuse for anything.

• "Applications" to enable more clients forum thread here: https://www.quakeworld.nu/forum/topic/7548/2020-client-chat

Allowed rulesets

• ezQuake: smackdown, qcon
• Players should do f_ruleset checks before game start. It is ultimately the responsibility of the players to perform this check, and in general, matches played with outlying rulesets will not be overturned if the players neglected to perform this duty. Where there is ambiguity, the decision will be decided by the Admins.

Allowed proxies

• QWfwd
• Qizmo 2.91
  
  

Using disallowed clients/proxies might lead to points deduction or even a WO.

Scripting and cheats

Allowed

• cl_fakeshaft (only mentioned here as it used to be forbidden)

NOT allowed

• movement scripts (ezquake: cl_idrive must be OFF)
• kfjump
• custom rocket jump scripts
• Any other kind of movement scripts
• Teamoverlay
• Automated teamsays
• Radar
• Skin changing depending on health/armour/weapon
• Custom models not allowed by f_modified
• Any kind of cheat (wallhack, aimbot, timers etc.)
• Hacked clients
• Coaching, (timing quad and other items, relaying enemy positions and giving teamplay suggestions)
• Different individual enemy skins
  
  

Failure to follow these restrictions can result in the player or team receiving harsh penalties such as, but not limited to:

• points deduction
• WO
• player disqualification
• team disqualification
• permanent ban.

Warnings and disqualification

• Two warnings will result in disqualification
  
  

To retain order in the league and prevent teams from cheating effectively we may issue warnings to teams if they misbehave in some way.

Other offences

• Having one or several players intentionally drop from server during a game without replacing them
• Playing in more than one team, or playing under someone else's name in another team (mercing). Standins are an exception.
• Fakenicking to get into a division where you don't belong
• Griefing, flaming and abusive behaviour will not be tolerated.
  
  

Most of these cases could result in direct disqualification of the player (and in some cases the whole team) and a ban of at least 1 season.

Server problems

• The current map should be played to the end, no matter the servers condition
• In case of a disconnected player, teams should pause the game, by team captain asking admin status, all players should concede it fast and elected admin player should type ""pause"". Teams should wait maximum 10 minutes for the player, after that if the player is not back into the server, game must resume.
  
  

This procedure exists to help a player/team that encountered a problem, but is not to be abused, which in that case will be analyzed by the admins.

• Admins will decide if a map should be replayed on another server
• If a server gives 2 or more spikes that result in 100% packet loss for all players for more that 10 seconds, the map should be replayed on another server if the teams do not agree to the score/situation.

Admins

The admins are there to help you, so if you ever need our assistance or have any questions, you can find us in the GetQuake discord server. Admins can change/fix rules if problems occur. Head admins are Praxismo and Link.

 Hangtime -  Skurk-  Link -  Toma -  Praxismo -  ohl