TABLE OF CONTENTS:
1. GENERAL ORGANISATION
1. GENERAL ORGANISATION
1.1. (Dates and place)
North American Tournament 10 will take place on August 17th and 18th at 12:00 EDT. All games will be played on the North American server.
Tournament Hosts are:
(skype : commanderriker123 ; email : email@example.com; char code: 922 EU/NA)
(skype : majorgster; email : firstname.lastname@example.org; char code: 194na 322eu)
(skype : lordsvit ; char code: 931 EU/NA)
(skype : lubbers.r ; char code: EU: 970 NA: 335)
Hosts have final decision on all matters.
Host can appoint Judges at any given time. Judges have powers and duties of Host except for Rules changing and appointing of Judges.
a) Important announcements are published on the Tournament’s website, www.learnstarbattle.com/NA10.
b) SBT is the name of Tournament’s general in-game chat channel. Captains meet on CSBT chat channel.
c) Each team is provided with it’s own private channel on free TeamSpeak 3 server. Host, Captain and other team members designated by Captain have Channel Admin powers. Created channels for in-game tournament play will have a maximum of 7 players. Using TeamSpeak 3 is not mandatory.
d) Players will try to contact the Host and Judges through their Captain as much as possible.
Prizes are in-game special ship models, ranks and other non-profitable prizes. Prizes to all participants and winners are awarded after the Tournament. Prize info can be found at:
2.1. (types of participation)
All individuals are eligible to participate :
a) registers individually (freelancer),
b) is registered by team Captain (team)
Individual players register by filling out a registration form on the website with NA character code and any other contact data (for example Player.1777 [optional contact data]). Additional information about game experience is welcome (ships, number of games, team vs team experience etc.). The player is then placed in the freelancer pool.
b) Freelancers teams are formed from Freelancer pool. Host designates captains, assigns teammates and provides any support needed.
Captains register their teams by posting the team roster on the tournament website.
a) The minimum number of players for a team is 6, maximum is 12. Captains can register teams with less than 6 players and add additional players until registration closes. Captains can designate up to 2 players to act as co-captains.
b) Registration for teams closes Sunday August 11th at 11:59 A.M EDT.
c) Teams are allowed to edit their roster until Thursday August 15th, 11:59 P.M EDT. Any team that schedules their first round match prior to this date and time will not be able to edit their roster after the match has been played.
d) Host assigns freelancers to teams with less than 6 players if captains cannot assemble full team and/or merges partial teams.
e) Only roster changes posted on the tournament website are valid.
2.5. (seeding system register)
Top 2 seeds will be determined by top 2 placement in WSBT2.
3.1 (match team leaders)
Co-captains act as match leaders if the team Captain is not present during a match. If neither Co-captains or Captains are present, a designated match leader can act as the Captain.
3.2. (match scheduling)
If captains have not already arranged the game lobby, they will find each other in the CSBT battle.net chat channel at least 10 minutes before a match to do so. The game schedule will be posted and updated on the tournament website.
a) Captains may agree on playing a match earlier during Tournament days. Notify a host if this occurs.
b) Teams are allowed a 15 minute break between the end of their previous game and the start of the next one. Captains may agree on an earlier start time if both teams are ready.
c) Lobbies will forcibly start no later than 10 minutes after a scheduled start time if 3.2b is fulfilled. The lobby shall start regardless of if both teams are ready.
d) Captains may agree on playing a match during Tournament week (August 11th – August 16th). A host must be notified and give consent.
e) If a team does not show up for the scheduled match that team forfeits the match. If both teams fail to show up for the scheduled time, both teams will forfeit.
3.3. (lobby hosting)
Top team in bracket hosts the lobby. All games will be played on the NA server, except upon exception by a tournament host.
3.4. (referees and spectators)
a) Referees are not allowed.
b) Spectators must be tournament hosts, judges, or casters. Other players are not allowed to spectate.
c) Spectators must message the lobby host for an invitation to the lobby. A captain cannot refuse to invite an official caster or a tournament host to the game.
3.5 (official casting)
Official casters cannot be refused from casting a game. Sign-ups for casters will take place on the website. Acceptance of application will be decided by the tournament hosts.
a.) Casters will ask both teams prior to each game permission to enter the teams Teamspeak channel while the game is live. Captains can deny casters access to the teams teamspeak channel at their discretion.
b.) A caster will join the teams channel in a separate tab. The caster will then mute his sound in the teams channel until the time at which he wishes to listen in on the live chat. When the caster listens in he will keep his microphone on mute but unmute his sound.
c.) Caster’s can only listen in on a teams channel for roughly 1 in game minute once every 8 in-game minutes. If both teams agree to allow the caster access to their channel during the game the caster cannot join the same teams channel twice in a row. Rather the caster must alternate between teams every 8 in-game minutes.
d.) If only one team grants the caster access to their channel, the caster can listen in to their channel once every 8 in-game minutes.
3.5. (game mode)
Matches are to be played in 6v6 Classic Unrated mode.
3.6. (replacement of missing player)
Match teams consist of 6 players.
a) Captains may agree to do a 5v5 game if either team does not have 6 players present. If the opposing team leader does not agree, the match shall be forfeited or played as a 5v6.
3.7. (match starting)
Providing that the conditions in 3.2 are met, the lobby host starts the game when both Captains signal their teams as ready. Accidental game starts shall result in the game being remade.
3.8. (stream delay)
Live stream delay shall be set to a minimum of 8 minutes.
4.1. (ship limit)
Ship limit is 2 of each type. Randoming is allowed. Random counts as a separate ship type.
Match must be remade if drop occurs before 20 seconds mark. After the 20 second mark, a team can use the resume from replay feature, see 4.3 for further details.
4.3 (re-start from replay)
In the event of a player dropping due to technical or network reasons, each team is allowed one restart from replay per game.
a.) The team with the dropped player is responsible for setting up the lobby. If a player drops from a team that has already used its re-start from replay, the game will continue and is not allowed to restart from replay.
b.) Each team is limited to 3 restart from replays for the entire tournament. Additional restarts may be allowed with Host consent.
c. ) A restart from replay must be used immediately after a drop has occurred. If a team decides to continue without using a restart from replay, they cannot change their decision later in the game.
c.) Details on how to restart from replay will be posted.
4.4. (in-game chat)
Teams are to keep chat in ALL-chat to a minimum. Bad manners (BM) and excessive amounts of spamming are forbidden and subject to sanctions by hosts. Technical issues are an exception.
Pausing is allowed after typing “PP“ to opponents. Unpausing requires statements from both Captains about team readiness. The opponents team-captain must unpause the game (countdown is 5 seconds minimum). Pause limit is 3 per team. Both Captains or Host may agree to ease this restriction.
a) When a lag window appears, the game must be paused if possible to allow the player to fix his connection. Rule 4.5. applies. Drop voting is not allowed.
b) When a lag window does not appear rule 4.5. applies.
c) An identified lagging player who cannot fix his connection within the teams pause limit must leave the game. Failing to do so results in forfeiting the match.
4.7. (terms of surrender)
A (Co-)Captain can surrender by typing “GG“ to opponents. “GG“ cannot be revoked. Teams are not obliged to play after surrender.
a. Captains (or an appointed member on the team) will upload uncompressed replays to their assigned TeamSpeak 3 channels. Replays must be submitted no later than 15 minutes after the game has finished.
b. The punishment for not uploading replays on time is a forfeit.
c. Replays are named as followed:
TO NAME YOUR REPLAY:
Match Number (W= winners bracket / L= losers bracket) specified in bracket. Include the zero in the match number if applicable (i.e. W01)
(w) Denotes winner
5.1. (general placement/advancement rule)
NA10 is a double elimination tournament. The first and second place teams in WSBT 2 will be placed in separate groups. If either one of these teams are unable to participate it will fall to the following top finishers. The rest of the seeding will be chosen by a random number generator.
For example, if there were 16 registered teams in NA10 The number one and two seeds will be placed as below:
The selection of the rest of the seeds will be casted and take place live Sunday August 11th at 3:00 PM EDT. Teams defeated in the Winners bracket fall to the Loser’s bracket.
5.2. (number of matches per game)
a) All matches in Top Brackets are Best of 3 (BO3).
b) All matches up to Loser Bracket Semi Finals prior to match #28 are best of one (BO1).
c) Loser Bracket Semi Finals and Loser Bracket Finals are both Best of Three (BO3).
d) The finals will be a Best of Three (BO3). If the winner of the Loser’s Bracket wins the best of 3, a second Best of One (BO1) shall be played.
5.3 (match selection)
Placement in brackets will be selected by random. Placement will be casted live Sunday August 11th at 3:00 P.M EDT (9:00 P.M CET). A random number generator will be used to determine placement. This will also act as the captains meeting.
Hosts can inflict the following punishments:
a) rebuke of player, team or other interested party in private message,
b) public reprimand of player, team or other interested party,
c) match ban of player or team (including forfeit),
d) tournament ban of player, team or other interested party,
e) disqualification of player or team from tournament prizes,
f) next EU and/or NA tournament ban of player or other interested party if future tournament host recognizes this punishment.
6.2. (right to appeal)
Interested party, player and/or Captain on behalf of teammate or team can appeal to Tournament Hosts against punishment inflicted by Judge. Appeal against punishments 6.2 c) and d) must be sent before matches in question start or in 2 hours after end of last of matches in question which were already played.
6.3. (publication of punishments)
All punishments except 6.2. a) are posted as important announcements.
6.4. (code of conduct reminder)
Using bank file modified in unintended way or modifying game to gain unfair advantage will be dealt accordingly on both Star Battle and Battle.net level, irrespectively of Tournament Rules.