1. General Information

1.1 Introduction

GameArena is running an Enemy Territory Quake Wars tournament available to players in Australia (the Tournament). The Tournament will feature team play only.

Any Australian resident aged 18 years, or older, who meets the eligibility criteria in condition 3 of the Tournament Conditions of Entry, can join the Tournament providing they can join a team by either creating a team or adding additional members to it to meet the required number of players, or by requesting recruitment to an existing team using the select team to join method. Teams must comprise of 8 players.

All servers for the Tournament will be provided dynamically by the Tournament software. After the successful completion of a round, the software will build the requirements for the next round, showing who will play whom, at what time and date, and on what server IP location. All locations will additionally be available by visiting GameArena's The Arena game client 5 minutes before the commencement of a game.

1.2 Outline of Tournament

The game will be played 8on8. Each team must have 8 players with the actual version of the game.

See 2.6 "Scoring" for how the winning team in each match is determined.

In each match the team that wins can play another match, and the team that loses is eliminated from the Tournament.

As noted in 1.1, the Tournament software will determine which team plays which other team in each match and which team will be the challenging team in the first round of that match. Due to the lack of any prequalification data, no seeding will be applied. All teams will initially be allocated to matches on a first come first serve basis.

Depending on the number of teams at the start of the Tournament, during the first match of the series, automatic byes may be applied in order to balance the team numbers for future matches.

Tournament games will be scheduled by GameArena via an automated system and the scheduled times will be emailed to registered players and made available on the Competition website.

1.3 Match Format

The match will take the ABBA format, having two Stop Watch rounds - best of 3 (20-minute long rounds) on one map. The first round Team A, as indicated by the team on the left on the match details, will attack first with Team B defending. The second Stop Watch round on the same map will start with Team B, as indicated by the team on the right of the match details, attacking first and Team A defending.

1.4 Punkbuster

The most current version of Punkbuster will be enabled on the server. Players must have the same version of Punkbuster running on their computers to play in the Tournament. Players should ensure they have nothing installed that will cause a Punkbuster violation.

If a user does not have the correct version of Punkbuster, the game does not allow that person to play. For General Punkbuster support, please the EvenBalance website at http://www.evenbalance.com/index.php?page=support-etqw.php.

1.5 Communication with GameArena

All teams are required to ensure that their contact email address listed on their team information page is up to date and checked regularly, and that their team captain's email address in their GameArena profile is also up to date and checked regularly.

This is the primary means of contact, and all rule changes, important announcements etc. will be made through these email addresses.

All players, especially team captains, are encouraged to check the GameArena Enemy Territory Quake Wars Tournament site regularly for any updates or information in relation to the Tournament.

2. Playing the Match

In this section, we describe what should happen while a match is being played. If there are any problems (server crashes, players spawning on the wrong team) please see Section 3.

2.1 Time Limit

All matches will be allocated a maximum of 2 and a half hours to be completed. This should be more than adequate to allow for an entire match. If the server time runs out before a match is completed, the match will be decided by the rules in the scoring section (see section 2.6).

If a team can prove that their opponents have deliberately wasted time, the time wasting team may suffer a forfeit. Time wasting can include demanding extra time to have players connect, demanding map restarts due to players spawning on the wrong team etc.

2.2 Joining the Server

The match server will appear at the time of the booking in the "Server Bookings" tab in The Arena.

At any time during the match, a Referee (including a GameArena Staff member, GameOp or Tournament Manager) may join the game for admin purposes.

Each team must be ready to join the server at the time it starts. Teams are allowed 10 minutes to connect to the server and be ready to play. Any team that has less than 8 players on their team after this 10 minute period forfeits the match.

At no time may a team have more than 8 players connected to the server.

The red team will play as the GDF side first, and should join that side when they join the server. The blue team will play as the Strogg side first, and should join that side when they join the server.

Each team must be ready to join the server at the time it starts. Teams are allowed 10 minutes to connect to the server and be ready to play. Any team that has less than 8 players on their team after this 10 minute period forfeits the match.

2.3 Preparing for the Match during Pre-Game

Each team must nominate one of their players to be a 'spokesperson' for the team - the person that will speak on behalf of the team during the match. This is the person that the Referee will ask questions of, who will announce that their team is ready, etc. It is expected (but not required) that this person be a captain of the team.

If a Referee has not joined after 5 minutes of the server starting, the teams should decide (through their spokespeople) which team will handle the administration of the server for the match. If the teams cannot agree, the GDF team will select a team member to Referee. Each team should have at least one member in every war that is familiar with the commands needed to administer a match - please see section 6.1 for the few commands required.

2.4 Starting the Match

The match must start no earlier than 5 minutes and no later than 10 minutes after the server starts.

Once both spokespeople announce that their team is ready, the person administering the match (Referee or otherwise) will issue the map restart command. This will commence a 2 minute countdown, and then play will begin. It is recommended that both spokespeople (or the Referee if present) will announce "THIS IS IT" so that both teams are clear that round 1 is starting.

2.5 Swapping Sides

After the first round of a match has completed there will be a two minute break. The teams MUST swap sides during this time. If a player intends to be away from the computer during the two minute break, they should swap before they leave.

2.6 Scoring

Map wins are added to determine the score: the team that wins a SW round (a map) receives two points; if both teams fail to set a time in a SW round (double fullhold), both teams will get one point only.

The team with the quickest time completing the objective will gain two points. If neither side completes the objective, then each team scores 1 point each. Possible scores after the first SW round. 2-0, 1-1. Possible overall scores after the second SW round: 4-0, 3-1, 2-2, 1-3.

In case the game is tied after the first two rounds, an extra round MUST be played on one of the remaining maps from the maplist. The winning team will be decided on the number of primary objectives completed. Should the number be equal, the times SET on that objective will be used.

2.7 Post Match - Completing the Match Scoring

Each team must enter a result within 4 hours of the match starting (approximately 90 minutes after the match ends). The result will either be the score, or a dispute. Each team is strongly advised to check the score they enter carefully. If the scores entered match, then the challenge will be complete. All scores will be entered by team captains on a results submission page that will appear in the left hand menu. If the scores don't match, GameArena will determine the winner by viewing the supplied screenshots.

3. Resolving Common Problems

3.1 Server Crashes

If the server crashes, both teams should wait for 10 minutes (or as long as required by a Tournament Manager) for the server to restart.

If the server is restarted, the round that was in progress when the server crashed will be replayed.

3.2 Players failing to switch teams

If a player fails to switch sides during the two minute break between rounds because the player is away or has some connection problem, the person (Referee or player) responsible for administration of the match should kick the player from the server. If the player quickly realizes their mistake and swaps to the correct side then they should not be kicked. This decision is at the GameArena administrator's discretion.

If the player that failed to switch teams takes any action between spawning on the incorrect team and being kicked, it is likely that player's team will forfeit the match. The first 30 seconds of any round in Enemy Territory Quake Wars are critical, and this will be taken into account when deciding how much effect the player on the wrong side had on that round.

4. Behavior, Sportsmanship, Disputes and Rulings

This Tournament will be run in a spirit of fair play. All teams are expected to act in a sportsmanlike way. There is sometimes a tendency by people using the Internet to behave in a way that they would not in real life. We strongly encourage all people to treat all other people involved in this Tournament as they would like to be treated - with respect and understanding.

4.1 Player Behavior

All players must behave in a sportsmanlike manner at all times. While we understand that emotions may run high as players can be passionate about the competition, please treat everyone involved with the Tournament with respect.

All players in a match must wear both their team's 'tag' and their GameArena registered nickname (the name that appears in the team list). If the name must be different (e.g. it is too long to fit) it should be very easily matched to the name that appears in the team list.

Some general chat is acceptable, but should be limited and appropriate. If the other team requests silence on the general chat, their request should be honoured.

All players must accept the Referee's decisions as final during the match. If a team disagrees, they are welcome to either dispute the match (if they believe that the result would be different if not for the disputed ruling) or bring the issue up with a Tournament Manager after the game.

Some examples of unacceptable behaviour:

• Abusing any Tournament Manager or Referee
• Abusing any competitor in the Tournament
• Accusing any competitor in the Tournament of cheating
• Excessive foul language
• Intentionally spawning on the wrong team
• Attempting to gain any unfair advantage over other players through cheating or exploiting bugs in the game.

All players should note that the GameArena Terms and Conditions and Code of Conduct apply to all games played as part of this Tournament, and beyond any consequences to their team, any player that breaches the Terms and Conditions or Code of Conduct during a Tournament match will suffer the consequences of that breach as if it had happened on a public server.

4.2 Team Behavior - Bug Exploits / Cheating

Teams must not profit from any player cheating or exploiting a bug in the game. It is the team captains' responsibility to ensure that their players follow the rules.

Teams must not use any player who is not listed in the registered player list (contained in the match information email).

Teams will not be able use any player who is currently banned from playing on the public Enemy Territory Quake Wars servers, or from GameArena generally. (This does not include a ban from The Arena Chat).

Teams must not have more than 8 players connected to the server at any time.

If the team captains have any doubt whatsoever about whether something that the team or a player in the team is going to do may be considered to be a bug exploit or cheating, they should clear it with a Tournament Manager before it is used. Failure to do this is no excuse.

4.3 'Smurfing'

No player may be a member of, or play for, more than one team in the Tournament at any time.

If a player is found to be a member of more than one team, or to have played for a team when their name was not on the allowed players list for that game, they will automatically be banned from the GameArena service (including all games, The Arena Chat, etc) for at least two weeks and be removed from the Tournament. Repeat breaches of this rule will result in permanent removal from the GameArena service.

4.4 Disputes and Rulings

If a team believes that the result of the game was affected by the other team breaching the rules, then they should file a dispute at the end of the match, as well as politely highlighting the rule breach at the time. They should collect as evidence as many screenshots and console logs as is practical while playing the game.

When resolving disputes, the Tournament Managers will pay the highest regard to what is the fairest outcome, and what is best for the Tournament. The Tournament Managers will examine the evidence to determine as closely as possible what the outcome of the match would have been had the breach not occurred. Sometimes it may take up to 72 hours or more to resolve a dispute. Teams are asked to be patient. Please note that until the dispute is resolved, the behavior of the teams will be considered to be part of the match, so abuse of the other team either through the dispute system or anywhere else will be taken into account when deciding the result.

4.5 Cheating and 'Exploiting'

Cheating does not really need to be defined. Any attempt to gain an unfair advantage is cheating. This includes modifying the game files, running memory resident cheats, or anything else beyond the normal scope of the game.

'Exploiting' refers to exploiting a bug in the game itself to gain an advantage. This may take the form of setting a variable to a value that gives an un-expected result, using a 'hole' in the map to gain access to an area that was not expected etc. Anything beyond what the programmers intended is considered a bug, and using a bug to gain an advantage is considered an exploit.

Because of the difficulty of defining what is a bug that is being exploited, what is just a 'little odd' or something that has been accepted by the community as part of the game,any team that intends to use anything that MAY be considered an exploit must verify that it is acceptable with a Tournament Manager BEFORE the match commences.

5. Server Settings

5.1 Server Config

The serversettings to allow MCP destroying when off-course will be disabled, meaning that if the MCP drives off-course and is disabled it will stay at this position.

set si_motd_4 "^DGameArena ^3Comp"

set si_pure 1
set si_rules sdGameRulesStopWatch

set g_warmup 0.25
set g_warmupDamage 1
set g_autoReadyPercent 0
set g_autoReadyWait 0
set g_gameReviewPause 0.5
set si_gameReviewReadyWait 0
set si_readyPercent 100

set si_disableVoting 0
set g_votePassPercentage 51
set g_voteWait 0
set g_kickBanLength 0

set bot_enable 0
set bot_minClients -1
set bot_uiNumGDF -1
set bot_uiNumStrogg -1

set g_allowComplaint_charge 0
set g_allowComplaint_explosives 0
set g_allowComplaint_firesupport 0
set g_allowComplaint_vehicles 0
set g_complaintGUIDLimit 0
set g_complaintLimit 0
set g_maxPlayerWarnings 0

set si_maxPlayers 16
set si_minPlayers 2
set si_needPass 1
set si_privateClients 0

set net_allowCheats 0
set net_allowServerMod 0
set net_LANServer 0
set net_LANForceAuth 0
set net_serverClientTimeout 60
set net_serverZombieTimeout 30
set net_serverDedicated 1
set net_serverMaxClientRate 25000
set net_serverPunkbusterEnabled 1
set net_updateAutoDownload 0
set net_updateAutoExecute 0

set si_spectators 1
set g_maxSpectateTime 0
set g_muteSpecs 0
set g_timeoutToSpec 0
set pm_spectatespeed 600
set pm_spectatespeedsprint 1500
set pm_spectatespeedwalk 256

set g_logObjectives 1
set g_logProficiency 0
set logFile 1
set logFileName "ga_8v8_$M-$D-$Y_$h.$m.$s.log"
set logTimeStamps 1

set g_autoFireTeam 0
set g_execMapConfigs 0
set g_maxVoiceChats 5
set g_maxVoiceChatsOver 30
set g_noRouteConstraintKick 1
set g_noRouteMaskDestruction 1
set g_playerPushForce 0
set g_showPlayerArrows 2
set g_stopWatchMode 0
set g_teamSwitchDelay 0
set g_useCompiledScript 1
set g_xpSave 1
set g_noRouteConstraintKick "1"
set g_noRouteMaskDestruction "1"

set si_adminStart 0
set si_allowLateJoin 1
set si_antiLag 1
set si_antiLagForgiving 0
set si_antiLagOnly 0
set si_disableGlobalChat 0
set si_noProficiency 1
set si_teamDamage 1
set si_teamForceBalance 0
set si_timelimit 20

pb_sv_enable
pb_sv_update
pb_sv_cvarempty
pb_sv_md5toolempty
pb_sv_taskempty

pb_sv_cvar m_pitch IN -0.022 0.022"
pb_sv_cvar m_pitch OUT -0.015 0.015"

5.2 Map List

Area22
Ark
Island
Refinery
Salvage
Sewer
Volcano

5.3 Restrictions

There will be no restrictions on vehicles, weapons, classes or deployables.

6. Match Administration

6.1 Administration Commands

Before entering any commands, the team captain must enter the server administration password that can be found in their booking email (Captains only).

To login as an admin on the server you must bring up the Limbo menu and go to the Admin tab.

On the Admin tab enter the server admin password after clicking on Admin Login

To start the Match, click on the Start Match tab under the Server tab in Admin

6.2 Notes for match administrators

Please be very careful with match administration. Only take an action with clear agreement from the other team's spokesperson. Excessive pausing of the game, or restarting a round when both teams believe that it is a competition round is unacceptable behavior.

7. Notes

7.1 Match Checklist

This is an example of the flow of a match:

10 minutes of pre-match:

• All players join within 10 minutes of the server booking time.
• Red Team team joins the GDF side,
• Blue Team team joins the Strogg side.
• Each side identifies their spokesperson.
• If the match referee has not joined after five minutes, the spokespeople decide which team will handle server administration.
• When both teams are ready, the person handling server administration gives the map restart command, and both spokes people confirm that "THIS IS IT".

The First Round played and completes.

5 minute break between rounds:

• All players should take a screenshot of the scoreboard at the end of the round.
• All players must change sides, and are strongly encouraged to do this as quickly as possible. If a player intends to take a very quick break during this time, they should change sides before leaving their computer.

Post match:

• Both teams must enter the result or a dispute within 4 hours of the match starting (approximately 90 minutes after the match ends)

7.2 Some Definitions

Tournament Manager:

Includes GameOps that have been designated Tournament Managers (found on the Tournament Rankings page) as well as any GameArena Employee.

7.3 Approved Commentators

GameArena may approve official commentators from time to time. These commentators may enter a Tournament server for the purposes of broadcasting (e.g. through shoutcast software) the game. All teams that compete on the GameArena Enemy Territory Quake Wars Tournament are taken to consent to these broadcasts. The Tournament Managers will advise the community of any approved commentators through the GameArena Enemy Territory Quake Wars forums. GameArena community members are encouraged to approach the Tournament Managers if they wish to become approved commentators and gain access to the GameArena resources for commentating on Tournament games.

ETQW demo software or a similar program is not currently available for Enemy Territory Quake Wars. By playing in this Tournament you agree to have your match spectated in this way.