1. ELIGIBILITY

1.1 REQUIREMENTS

a. Every team must read, understand and agree to the rules for participation in the Pro League (the “Rules”). The team captain (as defined in Section 3.2) will be responsible for accepting and agreeing to the rules on behalf of the entire teams roster. Thereafter, each player is expected and required to abide by the Rules, and any failure to follow them will result in punitive measures, including but not limited to all items listed in Section 4.8.

b. Each player may only use their own account.

c. Each player must be thirteen (13) years of age or older pursuant to the SMITE Terms of Service.

d. Each team must have five (5) players present throughout the entire tournament, regardless of whether the team is currently playing, waiting to play, or otherwise occupied.

e. Each player must be at least eighteen (18) years of age or older to be responsible for distributing any cash prizing. Any player under the age of 18 years of age must have a guardian who is eighteen (18) years of age or older in order to receive payments.

i. Each recipient of tournament payments must fill out the proper US tax forms in order to receive any earned prize money.

f. Each team is required to only play with members who have been checked-in by the time defined in Section 3.4c. Each checked-in player must wear the same clan tag.

g. A report for how team winnings will be split will be sent to each team and all who participated following the splits conclusion. Alterations to this proposal must be approved by an administrator.

1.2 RESTRICTIONS

a. Teams and players may only participate in the Pro League that is within their own region.

b. Players may only compete in one (1) HiRez Official Tournament series at one time.

c. Players may use any skins except the following:

i. All Gold, Legendary, Diamond, and Shadow skins

ii. Dark Lord Sun Wukong

iii. Nutcromancer and Galactic Ah Puch

iv. Starslayer Anhur

v. Death Machine and Feaster Bunny Bakasura

vi. Secret Agent Apollo

vii. Chronos 64

viii. Recon Artemis

ix. Other skins may be made unavailable for use only upon an Administrator’s discretion.

d. Gods, Items, or other In-Game content may be banned throughout anytime of the SMITE Pro League. Teams will be made aware of such bans at the earliest convenience of an Hi-Rez Administrator.

e. Players may not change their in-game names, clan names or clan tags at any point without Hi-Rez Studios permission.

f. Hi-Rez Studios has the right to deem any name or tag inappropriate. If a name or tag is flagged inappropriate, teams or players must change it to something that is approved before he/she may be able to compete.

g. Hi-Rez Studios holds the right to deny any representation of unwanted sponsors which can include, but not limited to: Gambling Sites, drugs, illegal activity, pornography, tobacco, competitors.

h. Players can only use in-game names with characters A-Z or 0-9. No special characters may be used.

1.3 QUALIFICATIONS

a. Only teams who have officially qualified from the Spring Split Relegations or advanced from the 2015 Fall Split are eligible to participate in the Spring Split Pro League.

i. In case of a team being disqualified or removed from the Pro League, a replacement team will be determined by an Administrator. Such situations may include but not limited to: failure to field a roster on three (3) matches or five (5) games, or constant unacceptable behavior.

ii. The incoming replacement team does not accrue the previous team record.

b. Teams may only play with the players that were checked in for that given week pursuant to Section 3.4c.

2. TOURNAMENT FORMAT

2.1 GENERAL

a. The Spring Split Pro League will run for 11 weeks starting Thursday, March 24th. Games will be played five (5) days a week: every Thursday, Friday, Saturday, Sunday, and Monday.

b. North American tournaments must be played on a North American server and European tournaments must be played on an European server.

c. Games may only be created upon the instruction of an authorized Hi-Rez Studios representative  (“Administrator”). An Administrator must be present for all games created.

d. Every Game must be created with the following requirements:

i. Name: Determined by creating team

ii. Password: Determined by creating team

iii. Spectate Password: Determined by an Administrator

iv. Region: North America/European

v. Pick Method: Draft – Conquest

vi. Party size: 5v5

vii. Allow Spectators/Record Demo

viii. Spawn Lane Minions

ix. Starting Level: 1

x. Starting Gold: 1500

e. The league structure will be a round robin of eight (8) teams. Each team will play each other twice in two (2) game sets.

f. The top three (3) teams with the best Win/Loss record will be invited to the Spring Split Finals LAN.

g. In the case of a tie in team standings, the following will be executed to break such tie:

i. 2-way tie: The team with the better head-to-head record. If a tie still exists with the head-to-head record, a BO1 5v5 conquest will be played. First or second pick option would be determined by a coin flip.

ii. 3-way tie: The team with the better head-to-head record. If a tie still exists with the head-to-head record, a single round robin would be played between the three (3) teams. If that fails to break a tie, a randomized single elimination tournament will be played with one (1) team getting a BYE.

iii. 4-way tie: The team with the better head-to-head record. If a tie still exists with the head-to-head record, teams will be randomized into a BO1 bracket. Once 2 teams win in the initial bracket, a 3rd place match must be played.

iv. 5-way tie: The team with the better head-to-head record. If a tie still exists with the head-to-head record, teams are randomized in a BO1 bracket with one (1) play-in round. Once the play-in round in complete, the same format as a 4-way tie will be played.

v. 6-way tie: The team with the better head-to-head record. If a tie still exists with the head-to-head record, teams are randomized into a BO1 bracket with two (2) BYEs issued to teams. The other 4 teams will play through similar to the 4-way single elimination bracket.

h. Additional restrictions may be added at any time before or during a Game or Match by an Administrator if a known or “game breaking” Bug is found.

i. Each player shall use his or her best efforts to report any Bugs found immediately at the end of each Game. Any player knowingly using one (1) or more Bugs to his or her advantage will be immediately disqualified from the Tournament.

i. Teams will earn compensation from Hi-Rez Studios based on their placement at the end of the Spring Split.

i. Due to any possible technical issues w/SMITE or its servers, games may be rescheduled on an admins behalf to another day and time not listed on the schedule.

3. TOURNAMENT RULES

3.1 PLAYERS

a. Teams and players are required to be available to play during the schedule times given to them before the start of the Pro League. A complete team must be available no later than the scheduled start time for each game in the Pro League.

b. Teams may not create a Game or start a Match until an Administrator provides the appropriate permission.

c. High standards are expected from every player competing at all times. Each player must follow the SMITE Terms of Service that he or she agreed to upon signing up for an account, including Item 12 (Online Rules of Conduct). Failure to abide by the SMITE Terms of Service may result in punitive measures, including but not limited to disqualification, suspension from future events, and/or termination of your account.

i. Each player must also display well-mannered behavior throughout the entire duration of the SMITE Pro League. This includes before, during, and after splits. Good behavior is expected in all public areas of interaction which include but are not limited to Twitch, Twitter, Facebook, and the in-game SMITE Client. You may also refer to Section 4.6(a)(iii) and (c) for additional rules on player behavior.

ii. Poor or negative behavior towards Hi-Rez staff, sponsors, or other players will not be acceptable and punitive measures will be assessed.

iii. Harassment and sexual harassment towards any player or Hi-Rez staff member will result in punitive measures pursuant to section 4.8.

d. Cheating is strictly prohibited. No player should be manipulating game files, using unapproved game modifications, or any other method by which one may gain an unfair advantage over another player.

i. Any players found cheating are subject to removal of all Hi-Rez Studios related and sponsored tournaments as well as permanently banned in SMITE.

ii. If any player is found using such cheats or injectors during competitive play, all games that were affected due to cheats will be subject to forfeiture and other potential penalties.

e. Collusion, intentionally losing a game, or any other action of a similar or reprehensible nature will not be tolerated. Each player shall use his or her best efforts to compete in a sportsmanlike manner.

f. Players are expected to participate in all games and events. Any player that does not show up to a scheduled match, LAN they qualified for, or intentionally forfeits games will not be paid for that event or those games.

g. Abusing spectator, including but not limited to stream sniping and/or ghosting will be treated as cheating. If a team or player is suspected of cheating, the Administrators reserve the right to take punitive measures.

h. Players are strictly prohibited from using any other persons account for any reason whatsoever.

i. A player is not allowed to use another players account (smurf) for any reason whatsoever. Players in violation of doing so will result in punitive measures including and not limited to the team being disqualified from the league and potential banning of these accounts.

i. If a player account is suspended for at least six (6) days or is permanently banned (even if the suspension/ban does not overlap the tournament period), he or she will not be allowed to participate unless written permission is granted from Adam “HiRezAPC” Mierzejewski.

i. Players must use the name that they agreed upon at the start of the league. Player names may not be changed at any point during the league.

j. Players will be given documents and other requirements at the start of the split. Players are required to have each of these items finalized, signed and/or completed by the beginning of the first week of play. If these requirements are not handed in on time, penalties and fines can exist up to the following:

i. No winnings will be paid to anyone on the team until everyone has successfully handed everything in.

ii. For each week that these items are not handed in, a penalty of 10% of the players winnings may be taken from said players payout.

iii. If any player hasn’t completed these requirements by a specified date after the splits LAN, those winnings are revoked from the player and all other players will finally get paid out that have filled out said requirements.

k. During the Pro League, players may be asked to participate in interviews whether they are live or text based. Teams are asked to be available at all points during a broadcast and have a player available to represent the team for such interviews.

i. Additional content may be required out of players by Hi-Rez Studios at which all players must make themselves available throughout the entire duration of the SMITE Pro League.

3.2 CAPTAINS

a. Each team shall determine who will act as Team Captain prior to the start of the Spring Split Pro League (the “Team Captain”), whereupon such appointment shall be permanent for the entire Spring Split Pro League. The captain will be the main point of contact for Hi-Rez Studios to deliver any information regarding the team but not limited to:

i. Rosters

ii. LAN logistics such as needed forms, travel accommodations and other needed information.

iii. Team availability

iv. Team / player information

v. League communications

b. Each team may designate a backup representative (the “Team Assistant”) should the Team Captain be unavailable due to unforeseeable or emergency circumstances. Written permission is required from the Team Captain to Adam “HiRezAPC” Mierzejewski or Daniel “HiRezDan” McHugh stating said person can act as the Team Assistant on all matters except roster changes. If a Team Assistant is required to act in the Team Captain’s place, he or she shall be responsible for all of the Team Captain’s duties until otherwise instructed by an Administrator.

c. Every Team Captain is responsible for updating the Administrators with any information pertaining to his or her own team as well as making sure that any requested information is provided to the requesting Administrator(s) in a timely fashion.

i. Team Captains are responsible for updating the outcome of matches with the proper Match ID in Teamspeak 3.

d. Each Team Captain must be available at all times to the Administrators for the entire duration of the Tournament. The Team Captain is responsible for making sure his/her team are where they need to be throughout the league.

e. Team Captains are required to use Teamspeak 3 to communicate with the admins. Captains may be contacted through this software and will be held accountable for information passed through this medium. Teamspeak 3 server information will be emailed to each Team Captain in the Pro League.

i. If the Team Captain is not a starter, then the Team Captain must appoint a player, approved by an Administrator, to be available throughout the duration of the tournament in Teamspeak 3 to relay requested information. This includes, but not limited to picks and bans as well as pauses.

ii. Only Team Captains and approved appointed players of participating teams for that day’s tournament are allowed to speak in Teamspeak 3. Any other players or teams using Teamspeak 3 may be subject to punitive measures at an admins discretion unless filling in for a Team Captain, fulfilling Section 3.2b.

f. Team Captains must check-in their first roster and team name the Tuesday before the start of the Spring Split Pro League – Tuesday, March 22nd (11:59pm EST).

i. All necessary items such as the team captain, team logos and branding guides must be sent in at this time as well. If additional assets are requested by Hi-Rez Studios, teams must supply those materials at their earliest convenience.  

g. Teams will be given a deadline at which they must submit the players that they are sending to LAN. Depending on the amount of players Hi-Rez will allow teams to invite to LAN, they must be decided and sent forward to Hi-Rez Studios by only the Team Captain. Once the roster has been submitted and the deadline has past, no other members may be invited unless there are severe circumstances.

i. Only the players submitted may be used at the LAN event.

ii. Teams will be given forms with strict deadlines in order to prepare for the upcoming LAN. Teams failing to submit these forms to Hi-Rez within the deadline will potentially jeopardize their invite to the LAN at which the next team in the standings will be invited.

iii. Teams are required to attend the event during the designated times of travel. Only under unforseen circumstances will a player be able to request a late arrival or early departure.

iv. Invites to LANs are for players, substitutes. team captains, team owners or team managers only.

3.3 Team Owners  

a. Team Owners are defined as the person who owns a team or organization. This person will be the main point of contact and will have the final say for all decisions regarding the team. A valid LLC or Tax Identification Number must exist in order for a team to hold the title of a Team Owner.

i. If a team does not hold a valid LLC or Tax Identification Number, then the Team Captain will act as Team Owner as defined in Section 3.3a.

b. A team owner may only own 1 team in the entire Pro League (includes all regions).

c. Team Owners may own 1 Challenger Cup team (includes all regions). If a Challenger Cup team is sponsored by a Team Owner who also sponsors a Pro League team that makes it to the Pro League, the Team Owner must sell/or drop one of the teams.

d. Team Owners may sell his/her team before a league ends at which the buyer obtains the teams spot and record in said league.

e. Teams may not be sold or changed once a league ends and before or during a LAN. Only after the LAN may changes occur. A deadline date will be given after each split on when such transactions may occur or by a Hi-Rez Studios Administrator discretion.

f. After the completion of a split, Team Owners must submit their roster for the next split if they have automatically qualified. A Hi-Rez Studios Administrator will set a specified date for this roster to be due. If said deadline is not met, that team may lose his/her spot into the next split.

i. An Administrator holds the right to deny any player(s) to be checked in on a team’s roster.

3.4 ROSTER AND SUBSTITUTION RULES

a. Rosters must include a minimum of 5 players who are all signed up under the same clan in-game.

b. Every team must have five (5) signed up players present and ready to play at all times.

c. Team Rosters need to be submitted and emailed each week before the start of the Pro League to Daniel “HiRezDan” McHugh by each Tuesday (11:59pm EST). The roster must include all starters for the week as well as all substitutes that may be used during the course of that given week. A form will be given for captains to fill out each week requesting this information.

i. Teams are allowed to check-in up to eight (8) players, just as long as they are eligible players. A minimum of six (6) players must be checked in and be labeled as starters.

ii. Teams are required to check-in at least one sub each week in case of emergencies. Failure to submit a sub could result in fines or other punitive measures. All subs must be deemed an eligible competitive player.

iii. Players who are checked in and play up to three (3) games in the SPL Spring Split will be roster locked to the one (1) team they played with but may still continue to play in the Challenger Cup.

iv. Players may only play with one team they are checked in on for the duration of the week.

d. In the Spring Split, hard roster locks will go into effect at the beginning of week six (6). Any players who are checked in and play at least one (1) game in week six or later, will be roster locked to the one (1) team they played with until after the completion of the Spring Finals LAN.

e. For a team to change its original starting roster, the team must notify an Administrator the day before the match, no later than 11:59pm EST. A change in the starting roster must include a player that was checked in earlier in the week.

f. In order for a team to use a substitute in the middle of the Tournament, they must notify an Administrator before the start of the game.

g. Players may only be active on 1 team at a time.

h. In the SPL Spring Split, players who are checked in and play a minimum of one (1) or more games will be platform locked to Official Hi-Rez PC SMITE  competitions for the entire 2016-2017 Season and may not participate in the SMITE Console League. This platform lock does not end until the Season’s World Championship LAN has been completed.

i. Any player checking – in for the first time will be given a deadline on required forms as listed in Section 3.1(j) or penalties may be assessed.  

3.5 Free Agents

a. Free Agents are defined as a player who has not competed in the SMITE Pro League at any point of time during the Split.

b. Free Agents are eligible to be picked up at any time of the season. Free Agents are defined as a player who are not roster locked or are not currently competing on a Pro League team.

c. Free Agents must be checked in at the start of each week as a starter or substitute in order to be eligible.

d. Free Agents must abide to the rules that Starters, substitutes and stand-in’s follow.

e. Free Agents must be approved by Hi-Rez Studio Administrators.

3.6 PAUSE / STOPPAGE OF  TIME

a. Pausing in the middle of any engagement such that it would give either of the team’s any sort of benefit or advantage is strictly prohibited.

i. A combat pause system has been built into custom games. When tournament games are played with this option available, all pauses that successfully go through the client will be considered valid. Otherwise, the game will not allow teams to pause during any sort of combat or skill channeling.

ii. If a team is able to pause a game in an engagement even with the combat pause system in place, it will be up to the admins discretion to decide whether the pause was legal or if it is indeed a combat pause.

b. The Team Captain must immediately tell an administrator when a game has been paused. Upon pausing, the captain must give the ingame time as well as the reason for the pause.

c. The Game will not resume (/pause) until clearance from an Administrator is issued and all players are notified and ready to continue.

i. If any player pauses or unpauses the game without permission, it may be considered unfair play (See section 4.6).

d. Each team is allowed a maximum of three (3) pauses per Game. Each pause cannot exceed more than three (3) minutes. If a Game is paused and the team is close to the three (3) minute mark, the team can inform an Administrator that the problem is taking longer to resolve. Without unpausing the game, the timer for the next pause will begin. Once the issue is resolved, the teams will confirm with an Administrator that each is ready to unpause. Only at that point does the pause timer stop. Any additional pauses may be provided by the Administrators.

i. Teams may only use the allowed pause time for their own use.

e. A player may pause the Game if any of the following conditions are present:

i. One (1) or more players have disconnected from the Game due to any form of network disconnect or computer crash.

ii. One (1) or more players are experiencing technical malfunctions related to hardware or software problems.

iii. One (1) or more players are experiencing severe illness.

e. Notwithstanding the foregoing, any pause made pursuant to subsection (d) must follow the restrictions set forth in Sections 3.7(a), (b), and (c).

3.7 ADMINISTRATOR RULES

a. Administrators will be checking each team’s lineup and making sure the players are logged into the proper accounts.

b. Administrators will be in charge of initiating the start of each Game.

c. Each and every pause and unpause must be approved by an Administrator pursuant to Section 3.6.

d. Each Administrator reserves the sole discretion to determine the final outcome and results of any Game and/or Match he or she is presiding over. Notwithstanding the foregoing, Adam “HiRezAPC” Mierzejewski may override any Administrator decision.

3.8 SETUP TIME

a. “Setup Time” means the time between Matches. The designated time will be the moment shortly after the completion of a full match series to the time right before the next match series begins.

b. During Setup Time, every team must:

i. Immediately communicate with the admins on previous match results and match ID.

ii. Consult and prepare with the admins for the next game or match.

iii. Ensure each player’s computer and peripherals are working appropriately.

iv. Use the bathroom or attend to other personal needs.

3.9 SPECTATING AND STREAMING

a. Abusing spectator, including but not limited to stream sniping and/or ghosting will be treated as cheating. If a team or player is suspected of cheating, the Administrators reserve the right to take punitive measures.

b. Players are not allowed to stream matches until the completion of their match on the official broadcast.

4. MATCH AND GAME RULES

4.1 GENERAL RULES

a. A “Game” is defined as an instance of Tournament competition where the outcome is determined by either the completion of the objective (defeating the enemy Titan), a team surrendering, or a team being disqualified.

b. A “Match” is defined as a full set of Games (i.e., a best of three (3) series) that is played until a team wins a majority of the set.

c. This is a 5v5 (Conquest) league. The Team listed as the Home Team will have the choice to select their side as first pick or second pick. In the second game of a two (2) game set, the opposing team will have the option of first pick or second pick.

d. Games must be created as stated in Section 2.1(d).

e. When a team surrenders a Game, it will automatically be given the loss for that Game. If there are any following Games that the same team must play in, such as the second Game in a best of three (3) series, that team is required to play.

f. A team may not surrender before the 10-minute mark in-game. Surrendering before the 10-minute mark in-game will result in punitive measures.

g. In the event a team forfeits or fails to field a roster for a scheduled match, said team will not receive prizing for that match and additional fines may be assessed.

i. Any player that does not play in a game will not be paid for that game.

h. When a team is disqualified from a Game, Match, or the Tournament, it will automatically be given the loss for that said Game or Match, as well as potentially being removed from the remainder of the Tournament.

i. Any team that is disqualified from the Tournament will forfeit all prizing, outstanding per diem, and benefits that they may have earned related to the Tournament. Disqualifications may be awarded after the tournaments completion OR prior to the tournaments completion but after a teams elimination.

ii. Any team that refuses to play games in the Spring Split Relegations will forfeit all prizing and benefits that they may have earned related to the Tournament.

4.2 PICKS AND BANS

a. Picks and bans for Games will be handled in the following format: Where the first team picking is A and the second team picking is B, character bans will be conducted in the order of ABABBABA and character picks will be conducted in the order ABBAABBAAB.

i. The option of first pick or second pick will be determined as listed in 4.1(c) and (d).

b. As indicated in subsection (a), each team may ban up to a maximum of four (4) characters each Game.

c. All picks and bans must be executed through the automated process within the SMITE client, and any use of chat for the same is strictly prohibited.

d. Players are expected to hold their game until notified by an admin such that the broadcasters can broadcast picks/bans.

e. In the event that a team does not select one (1) or more picks or bans within the allotted time frame, the following may occur:

i. Bans : If a team fails to ban during the allotted banning time, that team will remain without that ban in place. Only under severe technical difficulties will a remake be allowed in order to place the intended ban.

ii. Picks : If one (1) or more players fails to pick during the allotted character select time, the Team Captain shall contact an administrator and explain the problem. The game will be remade. Each team shall only be allowed one (1) Game remake per Match due to a failed pick, provided any prior remakes for the Match were unrelated to the character picks or were the result of unforeseeable circumstances outside of the non-picking team’s control.

iii. Pervasive failure to pick/ban in a timely manner will result in punitive measures – as listed in Section 4.8.

f. The newest god will not be available until after the god has been available in ranked for seven (7) days. This ban does NOT count towards the bans that each team gets.

4.3 PUNCTUALITY OF PLAYERS AND TEAMS

a. Each Game is expected to start within one (1) minute of an Administrator’s request. If a Game does not start within the one (1) minute period, any teams present must contact an Administrator immediately with a compelling reason for the delay.

i. If a team is consistently late, punitive measures may apply including but not limited to loss of pause time and fines may be assessed.

4.4 DELAY OF GAME

a. There are scheduled times during which each game must be played. These time restraints must be followed by all players. Setting up tournament area, using the bathroom, and getting food or drink are all examples of what time between matches is used for.

b. Team Captains shall tell an Administrator about any delays that may overlap a games schedule time.

c. During the Tournament, some Games may be requested to be held or gated based on the Tournament schedule.

i. Teams are required to check with an Administrator and verify whether the next Game is on time. This process is to ensure everyone is communicating and informed about the Tournament schedule.

ii. In special cases where one (1) or more Games must be held over thirty (30) minutes, Administrators will be in close contact with the affected teams. Players must remain in the Tournament area during this time and be prepared to play upon notice.

iii. An Administrator holds the right to postpone any game or match to a later date based on severe circumstances.

d. In the case of a player’s client loading slowly or a Game crashing upon loading, an immediate pause may be issued until all ten (10) players successfully load in and connect. The applicable Team Captain shall notify an Administrator of this process immediately upon pause.

4.5 PLAYER DISCONNECTS

a. If a player fails to load into a Game or disconnects during a Game where no character kills have occurred and the in game timer reads ten (10) seconds after the minions have spawned or less, the following shall apply:

i. Either Team may request a remake of the Game. Any remake must be approved by the appropriate Administrator. Players must continue playing the original Game until an Administrator approves the remake. Remake requests from an individual team will only be awarded once per Game, unless otherwise determined by two (2) or more Administrators.

b. If a player disconnects during a Game where character kills have occurred or the in game timer reads greater than ten (10) seconds after minions have spawned, there will be no remake unless otherwise determined by the head Administrator.

c. The substitute player checked-in pursuant to Section 3.4 may be used between remakes, provided it is approved by an Administrator.

d. In the event of a remake, both teams must pick and ban the same characters as in the previous Game. However, players may exchange which characters they are playing.

4.6 UNFAIR PLAY / MANNERED PLAY

a. The following are considered unfair play:

i. The use of any type of injector, cheat, map hack program, or any other third party program or device as further described in Sections 3.1(d).

ii. Intentional pausing, as further described in Section 3.6, or disconnecting.

iii. Unsportsmanlike conduct, including but not limited to inappropriate actions directed toward other players, the audience, Administrators, or other Hi-Rez Studios personnel, or inappropriate actions directly affecting the Game such as intentional feeding or collusion as further described in Section 3.1(e).

iv. Interacting with any livestream chat on Twitch or any other similar website prior to the official broadcast showing the Game is complete.

v. Violating the SMITE Terms of Service as further described in Section 3.1(c).

b. Private messaging another player during the Tournament is strictly prohibited.

c. Each player shall use his or her best efforts to act as a well-mannered individual throughout the tournament. Examples of poor manners include, but are not limited to, the following:

i. Constant emote spam in-game, including taunting.

ii. Verbally taunting another team or player.

iii. Sending messages to a player before, during, or after a game.

iv. Spamming any unnecessary pinging in game, including during a pause.

d. If a team shows signs of not trying or not putting forward the best roster for their team, we reserve the right to evaluate the situation and disqualify that said team.

4.7 GAME VICTORIES

a. Each Game must be played until the final objective is completed (destroying the opposing Titan) or until a team surrenders in order to receive a victory.

b. In the event of a Tournament server crash or malfunction, any affected Game(s) will be remade from the start unless Adam “HiRezAPC” Mierzejewski has agreed to award a team with the victory. In the event of a crash or malfunction, a team will have won if all of the following are met:

i. The game has lasted more than 20 min

ii. The gold differential is 12k+

iii. They have destroyed two enemy Phoenixes and have at least one tower in all lanes

4.8 PUNITIVE MEASURES

a. If any player or team violates a rule contained herein, the player or team as a whole may be subject to disqualification, including forfeiture of any and all payments from Hi-Rez Studios associated with the Tournament. Other punitive measures may include, but are not limited to: loss of god bans, loss of pause time, suspension or prohibition from participating in future Hi-Rez Studios’ events.

i. Rules are enforced and handled by Hi-Rez Studios Administrative team. Teams do not have the option to decline any penalties being assessed onto their opponents.

b. In addition to Section 4.8(a), if a team or player fails to abide by Hi-Rez Studios requirements, it may result in teams and/or players to be fined. Each fine will be documented and a written notice will be issued with the fine. Fines are determined by Hi-Rez Studios.

i. Examples to when fines may be applied due to a player include, but aren’t limited to misbehavior by a team and/or player, delay starts or complete absence to games, not having required documentation completed by deadlines, violation(s) of rules.

5. POST MATCH RULES

5.1 GENERAL RULES

a. Players shall not type or otherwise participate in any livestream chat until coverage of any Game they were participating in has concluded. This includes during any Game pause. The purpose behind this restriction is to avoid spoiling events to the audience because all broadcasting is sent out on a delay.

b. If a team wins one or more prizes, the email address given on the check-in form will be used to continue communication with the team. Hi-Rez Studios will need to obtain contact and shipping information from each player receiving prizing throughout the tournament. Prizing will be subject to domestic and international tax laws. All players will be required to complete tax information forms before prizing is awarded.

6. RULES DISCLAIMER

All rules are subject to an Administrator’s interpretation. Hi-Rez Studios reserves the right to modify, add, or delete rules at any time, without prior notice and/or reason. Unless otherwise stated, all decisions made by an Administrator pursuant to these rules are final and binding upon all applicable parties. If you do not agree with all of the rules and stipulations listed above, you may not participate in the Tournament. By requesting entry into the Tournament, you represent and warrant to Hi-Rez Studios that you have read, understand, and agree to these rules and stipulations, and promise to act in compliance with such rules and stipulations at all times.