Difference between revisions of "GetQuad! Draft 1/Rules"
m |
|||
| Line 53: | Line 53: | ||
}} | }} | ||
| − | + | Summary of Rules | |
| + | Format | ||
| + | The tournament will consist of a round robin in each division. | ||
| + | Teams will be split between 3 divisions based on skill level. | ||
| + | Each team in each division will play each other once in a best-of-three (BO3) match. | ||
| + | Points will be awarded based on map wins, 1 point per map win. Winner of each game gets 2 points. Looser of each game gets 1 or 0 points. | ||
| + | If teams are equal in the table, on points (map wins), then map difference + - will seperate the teams. If teams still can not be | ||
| + | seperated then a decider game will be played BO3. If more teams than 2 are equal, we will have to set up a mini tournamet, meaning | ||
| + | a new round robin between the teams. | ||
| + | When all games are played we could do a playoff if teams want to. That would be decided very much on activity. | ||
| + | |||
| + | |||
| + | |||
| + | Map pool divison 1 | ||
| + | |||
| + | |||
| + | TB3 maps; dm2, dm3, e1m2. | ||
| + | |||
| + | Decider map: standard BO3 rule. | ||
| + | |||
| + | |||
| + | Map pool divison 2 and divison 3 | ||
| + | |||
| + | |||
| + | cmt2, cmt3, cmt4, dm2, dm3, e1m2, e3m3tdm, schloss | ||
| + | |||
| + | Decider map: 1 of the TB3 maps; dm2, dm3, e1m2, with this format: | ||
| + | |||
| + | - If no TB3 map have been played then each team tosses 1 TB3 map each. Do random team draw in console of who tosses first. | ||
| + | - If 1 TB3 map have been played, you do random draw in console on the reminding 2 TB3 maps as decider. | ||
| + | - If 2 TB3 maps has been played, the last one is played as decider, or 3 x same map (standard BO3 rule). | ||
| + | |||
| + | |||
| + | Note:Teams can pick other map’s if both agree. | ||
| + | |||
| + | |||
| + | Team Restrictions | ||
| + | Teams to consist of 5 players per team | ||
| + | In each division there is a standin/reserve pool that can be used if your team is 1 player short. You can not use more than 1 standin per game. | ||
| + | Timeframe | ||
| + | All matches will have a deadline and teams should be active in communicating with each other and schedule their game. | ||
| + | |||
| + | If a team is idling or deemed by the admins that they are not making an effort to produce the game it shall be considered the ofending | ||
| + | team forfeits the match and a Walk Over (WO) shall be awarded to the opposition. | ||
| + | |||
| + | The schedule is on the table/games page. | ||
| + | |||
| + | Ping | ||
| + | Choice of server should be suitable for both teams | ||
| + | The pings should be the most even for the 2 teams and measures like cl_delay_packet to increase the fairness of a match are welcomed. | ||
| + | Matches must be played on the servers of the continent were the competition is being held. | ||
| + | The team A with highest average ping can require the other team B to ping up to the level of team A's lowest pinging player. Only the best possible ping is accounted for. Using delay packet or rerouting to raise the ping of the lowest pinging player in order to force the other team to ping up more is NOT allowed and will be punished. | ||
| + | The maximum minping that can be required is 52ms. | ||
| + | Is its impossible to get a server fair pings for each teams (<=15ms), players can interchange between servers to make a fair game or increase the game communication latency with cl_delay_packet command to make the games the most fair possible. | ||
| + | If players still can't agree on a server, please contact admins about it. Admin decision is final. | ||
| + | Server Settings | ||
| + | Timelimit: 20 minutes | ||
| + | Overtime: 5 minutes if match is a draw | ||
| + | Deathmatch mode: 1 | ||
| + | Teamplay mode: 2 | ||
| + | Spawn mode: Either KTX/KTX2 Respawns or KTPro Spawn is to be selected | ||
| + | Powerups: ON | ||
| + | Discharge: ON | ||
| + | FPS: A max of 77 fps is allowed. | ||
| + | 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. | ||
| + | These should be the basic 4on4 settings on all modern servers, but make sure to check. | ||
| + | Spectators | ||
| + | If a team requests nospecs-mode, the other team are obliged to comply. | ||
| + | Match Reporting | ||
| + | The team that won a match should report the match. | ||
| + | In order for a match to be valid you'll need to have screenshots from each played map | ||
| + | Reports should be made on the tournament thread at ???????, stating the order of the maps played. | ||
| + | Walkover | ||
| + | Walkovers are 2 pts | ||
| + | Allowed clients | ||
| + | Open source clients (with source code publicly available on Internet) that have equivalent checks/restrictions of ezQuake's: | ||
| + | ezQuake (2.2.x, 3.0.x, 3.1.x, or new version of ezquake if its out while tournament is running), https://ezquake.github.io/ | ||
| + | FTEQW (1.00), http://fte.triptohell.info/ | ||
| + | FodQuake (0.4), http://fodquake.net/ | ||
| + | Allowed rulesets | ||
| + | ezQuake: smackdown, thunderdome or qcon | ||
| + | FTEQW: strict | ||
| + | FodQuake: eql | ||
| + | Note: Players should do f_ruleset checks before game start. | ||
| + | Allowed proxys | ||
| + | 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) | ||
| + | Different enemy skins | ||
| + | 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) | ||
| + | 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 | ||
| + | 2 (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) | ||
| + | Fakenicking to get into a division where you don't belong | ||
| + | Griefing, flaming and general abusive behaviour will not be tolerated. | ||
| + | Most of these cases 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 10seconds, the map should be replayed on another server if the teams does not agree to the score/situation. | ||
| + | Tournament 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 GetQuad discord server. Admins can change/fix rules if problems occur. Tournament admins are: | ||
| + | |||
| + | The Draft rules are based in EQL and Thunderdome rules, as well as previous tournament rules. | ||
Revision as of 17:57, 17 April 2019
Summary of Rules Format The tournament will consist of a round robin in each division. Teams will be split between 3 divisions based on skill level. Each team in each division will play each other once in a best-of-three (BO3) match. Points will be awarded based on map wins, 1 point per map win. Winner of each game gets 2 points. Looser of each game gets 1 or 0 points. If teams are equal in the table, on points (map wins), then map difference + - will seperate the teams. If teams still can not be seperated then a decider game will be played BO3. If more teams than 2 are equal, we will have to set up a mini tournamet, meaning a new round robin between the teams. When all games are played we could do a playoff if teams want to. That would be decided very much on activity.
Map pool divison 1
TB3 maps; dm2, dm3, e1m2.
Decider map: standard BO3 rule.
Map pool divison 2 and divison 3
cmt2, cmt3, cmt4, dm2, dm3, e1m2, e3m3tdm, schloss
Decider map: 1 of the TB3 maps; dm2, dm3, e1m2, with this format:
- If no TB3 map have been played then each team tosses 1 TB3 map each. Do random team draw in console of who tosses first. - If 1 TB3 map have been played, you do random draw in console on the reminding 2 TB3 maps as decider. - If 2 TB3 maps has been played, the last one is played as decider, or 3 x same map (standard BO3 rule).
Note:Teams can pick other map’s if both agree.
Team Restrictions
Teams to consist of 5 players per team
In each division there is a standin/reserve pool that can be used if your team is 1 player short. You can not use more than 1 standin per game.
Timeframe
All matches will have a deadline and teams should be active in communicating with each other and schedule their game.
If a team is idling or deemed by the admins that they are not making an effort to produce the game it shall be considered the ofending team forfeits the match and a Walk Over (WO) shall be awarded to the opposition.
The schedule is on the table/games page.
Ping Choice of server should be suitable for both teams The pings should be the most even for the 2 teams and measures like cl_delay_packet to increase the fairness of a match are welcomed. Matches must be played on the servers of the continent were the competition is being held. The team A with highest average ping can require the other team B to ping up to the level of team A's lowest pinging player. Only the best possible ping is accounted for. Using delay packet or rerouting to raise the ping of the lowest pinging player in order to force the other team to ping up more is NOT allowed and will be punished. The maximum minping that can be required is 52ms. Is its impossible to get a server fair pings for each teams (<=15ms), players can interchange between servers to make a fair game or increase the game communication latency with cl_delay_packet command to make the games the most fair possible. If players still can't agree on a server, please contact admins about it. Admin decision is final. Server Settings Timelimit: 20 minutes Overtime: 5 minutes if match is a draw Deathmatch mode: 1 Teamplay mode: 2 Spawn mode: Either KTX/KTX2 Respawns or KTPro Spawn is to be selected Powerups: ON Discharge: ON FPS: A max of 77 fps is allowed. 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. These should be the basic 4on4 settings on all modern servers, but make sure to check. Spectators If a team requests nospecs-mode, the other team are obliged to comply. Match Reporting The team that won a match should report the match. In order for a match to be valid you'll need to have screenshots from each played map Reports should be made on the tournament thread at ???????, stating the order of the maps played. Walkover Walkovers are 2 pts Allowed clients Open source clients (with source code publicly available on Internet) that have equivalent checks/restrictions of ezQuake's: ezQuake (2.2.x, 3.0.x, 3.1.x, or new version of ezquake if its out while tournament is running), https://ezquake.github.io/ FTEQW (1.00), http://fte.triptohell.info/ FodQuake (0.4), http://fodquake.net/ Allowed rulesets ezQuake: smackdown, thunderdome or qcon FTEQW: strict FodQuake: eql Note: Players should do f_ruleset checks before game start. Allowed proxys 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) Different enemy skins 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) 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 2 (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) Fakenicking to get into a division where you don't belong Griefing, flaming and general abusive behaviour will not be tolerated. Most of these cases 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 10seconds, the map should be replayed on another server if the teams does not agree to the score/situation. Tournament 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 GetQuad discord server. Admins can change/fix rules if problems occur. Tournament admins are:
The Draft rules are based in EQL and Thunderdome rules, as well as previous tournament rules.