Qlan War Tournament 1/Information

From QWiki
Revision as of 21:50, 9 January 2022 by D0PESK1LLZ (talk | contribs) (Created page with "{{Tabs static |name1=Overview |link1=Qlan_War_Tournament_1 |name2=Division 1 |link2=Qlan_War_Tournament_1/Div1 |name3=Division 2 |link3=Qlan_War_Tournament_1/Div2 |name4=Divis...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Tournament system

  • Teams are sorted into divisions reflecting their skill level.
  • The tournament consists of two stages:
    • A round-robin group stage.
    • A single elimination playoff.
  • The first 6 teams of each division will get a spot in the playoffs.
  • The playoffs will have a 3rd place match.
  • Teams have to play one match per week (except when they have a bye).
  • Each team plays each other once in a BO3 match in the group stage.
  • Playoff matches are BO5.

Points

  • The ranking is determined by taking the following stats into account (in order):
    • Points (1 point per match win).
    • Map difference.
    • Internal fight.
    • Map difference in those internal fights.
    • Frag difference in those internal fights.
    • Total frag difference of all games.

Match procedure

Map Pool

  • dm2
  • dm3
  • e1m2

BO3

  • The procedure is "pick-pick-play".
  • The team that wins "/cmd rnd team1 team2" picks first.
  • All maps have to played once, except if both teams agree otherwise.

BO5

  • The procedure is "pick-pick-play-pick-pick".
  • The team that wins "/cmd rnd team1 team2" picks first.
  • The first team to win 3 maps wins.
  • All maps must be played once in the first 3 maps.
  • If the match is not won after 3 maps have been played, the team that's down 1-2 picks the next map.
  • If the match goes to 5 maps, the other team picks the last map. The last map cannot be repeated without agreement from the opposing team captain.

Scheduling

  • All matches have a deadline (consult the division page for the dates).
  • Teams should schedule matches on the Discord server and tag the admins when a time and date has been found.
  • If a team is not making any efforts to schedule a match it will be taken into consideration when a WO has to be assigned.

Ping

  • The primary driver for server selection is to find a server where the teams have similar average pings (+/- 2ms) and to minimize that average.
  • The pings should be the most even for the two 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 EU servers.
  • The highest minping 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
  • Deathmatch mode: 1
  • Teamplay mode: 2
  • Spawn mode: KTX2
  • Powerups: ON
  • Discharge: ON
  • Airstep: OFF
  • Jawnmode: OFF
  • Antilag: 2
  • Fallbunny: ON
  • Teamoverlay: OFF
  • No berzerk, midair, instagib or other unusual modes.
  • If a team requests /nospecs, the other team is obliged to comply.

Client Settings

  • Allowed clients: ezQuake 3.2.x or 3.6-alphaX
  • Allowed ruleset: smackdown, qcon
  • Allowed proxies: qwfwd, Qizmo 2.91

Match Reporting

  • The captain of the team that wins has to report the match in the #reports channel on Discord.
  • A report consists of screenshots and server-side MVDs.