ZCX Tour

Rules of engagement

The rules below are transcribed from the supplied ZCX Tour rules image.

Active replay map pool
  • 3v3 ZC Melee Map (V2)
  • 3v3 ZC UMS Map
  • ZC Build Test Map

1. Basic guidelines

All players must be registered on this website; check Members before playing. Games use No Rush and Map Max +1 Minute on a map in the active season pool. StarCraft Original is the default; Brood War requires all six players to agree. Create in Melee and remake as UMS to choose races, or set teams directly in UMS. All six players must agree to teams selected in advance. PTZ is the default matchup; PZP needs a vote. Melee Spot games, where players use the race assigned to their Melee position, require a unanimous 6/6 vote.

2. ZCX Tour scoring

To qualify for Tier 1, play at least 20% of the season's total games; Tier 2 requires at least 10%, and players below 10% qualify for Tier 3. If players tie in win rate, the player with more wins ranks higher. Weighted WinRate also accounts for activity: 20% of the total games played is added to the player's WinRate, so playing more games affects the ranking.

3. Hacking and ally attacks

Hacking—changing how StarCraft operates—is not tolerated and results in a one-week suspension. Attacking your own ally (BSing) results in a dodge penalty.

4. Posting AKA and smurfing

If you use more than one gamer tag, post each AKA in the forum's Post AKA thread. Clan changes do not need to be reported. Do not impersonate another player; smurfing results in a one-week suspension.

5. Building, AFK, voids, and observers

Building on the opponent's side of the map (past the middle statue) or in the middle is allowed. A player showing off with no units moving, upgrades, or units queued for more than 15 seconds may be disqualified. A judge can approve a void, or 4/6 players can vote to void a game, including after it has started. If players want to remake after a game has started to let a new observer join, 4/6 votes are required.

6. Disqualification

A gameplay violation can result in a DQ: the opposing team receives a win, while the violating player receives a DQ and non-violating teammates do not receive a loss. DQs count like dodges. The sixth DQ/dodge results in a one-week suspension.

7. Bombing and rushing

Using air units other than a Zerg Guardian to attack Mauls, Pylons, Depots, or Techs is an automatic DQ. If idle air units accidentally destroy one of these buildings, pause and tell the team to destroy the same number of that building; bombing three or more this way is an automatic DQ. Hatcheries, Lairs, and Hives are not Techs; Mains are buildings that harvest resources. MM rushing is banned. Before MM+1 minute, units other than Zerg Overlords may not pass the opponent's wall or the middle statue. Workers may go middle after MM, and clearing sides after MM is allowed.

8. Tripling and middle defense

Tripling is not allowed: it is when all three players on a team attack one opponent, unless all three came through the middle. Pause immediately and tell one attacker to leave; if they refuse, all three are DQ'd. The minimum to count as a triple is six attacking units or three magic units. Middle defense is limited to three Hives and a combined six Protoss/Sunken defenses. Pause and remove excess immediately or risk a DQ. Hatches in the middle are not allowed in PZP games.

9. Zerg base limits and Overlord hunting

Zerg may have at most 51 Hatcheries/Hives: 48 in the base and three in middle defense. A Zerg base may have at most 10 Spores/Sunkens, with no more than five outside the Zerg Main Defense. If an Overlord is hunted in the safe zone behind an opposing Zerg base's walls, pause and have the team destroy the same number of Overlords. Hunting three or more Overlords in the safe zone is an automatic DQ.

10. Dodges, disconnects, and game drops

A dodge is refusing a matchup or leaving before the game ends, and counts as two losses. Not joining UMS or going AFK in the lobby for more than five minutes is also a dodge. More than five dodges in a season results in a one-week suspension; games played while suspended do not count. A disconnect before MM allows five minutes to return and fix lag, with at most one remake of the same matchup; a second disconnect is a dodge. If a game glitch drops two or more players, the game may be remade, voided by a 4/6 vote, or awarded as Op 2 to the team more likely to win. Remakes use the same matchup. Post the reason on the website; Op 2 means 'Game dropped' / 'Option 2.'

11. Pauses, saving, and lag

A pause is allowed up to five minutes. More time requires agreement from 4/6 players. Do not unpause without checking with the player who paused; doing so can result in a dodge. Saving a game counts as a dodge for the player who saves it; if the saver is an observer, no player receives a win. If severe lag makes a game unplayable, a 4/6 vote can void it, award Op 2 to the team more likely to win, or save and remake without a dodge for the player who saved.

12. Season regulations and disputes

Seasons start at 6:00 AM Pacific on the first day of the month and end at 6:00 AM Pacific on the last day of the season month. A season continues until at least 50 games have been played. Use the player's gamer tag when reporting. A winning player from the winning team must report within 24 hours; on the last day of the season, report within six hours. False reports result in a one-week suspension. Submit disputes to the ZCX Tour Game Disputes board by 12:00 PM Pacific on the last night of the season; provide the reply to a judge on Battle.net before the season ends or the dispute is void. After losing two disputes, a player may not dispute again that season.

Automated replay checks

The site currently checks the active map pool, supported 1v1/2v2/3v3 format, a 90-second minimum game length, early leaves, duplicate replays, a six-hour report window, winner detection, and linked/distinct pilots. Rules that require judging gameplay (including DQs, tripling, votes, and disputes) are not automatically decided by replay upload and need staff review.