The Team Fortress 2 Tournament is a Double Elimination competition featuring five Control Point maps. The victor of each preliminary match will be decided based on the best of five rounds over 30 minutes. The winner will be decided in a best of 3 maps contest.
Tournament Organizer: Joshua Swindall
Tournament Hosts: Daniel Lindsey
Location: Shelby Center Room 114
Time: 11am-4:30pm
Available Slots: 36 players; 6 teams
Entry Fee: FREE
1st Place Prize: T-shirts
Mode: Control Point
Tournament Setup: BYOC (Bring Your Own Computer)
Maps
- cp_Badands
- cp_Granary
- cp_snakewater
- cp_gullywash_final1
Tiebreaker: cp_gravelpit (maximum 2 rounds per side)
Match Format
- Class Limits: Demo, Medic, Heavy, Engineer limit 1, everything else limit 2
- Matches will be played 6 vs 6 competitive format;
- Banned Weapons: Banned Items List
- Stopwatch maps will be played with no time limit, and the ABBA style, if a decider is needed then a vanilla heavy bash is used to decide who attacks/defends first for the deciding round.
- Random Critical Hits will be OFF (Situational Crits, ie. Sniper headshots, Kritzkreig, will be allowed).
- Fixed weapon spread will be used for shotguns.
Policies
Draws
Draw results are not permitted throughout the tournament. In the event of a draw the two teams will play overtime until a golden cap is reached within 10 minutes (the team to achieve 1 further scoreboard round wins). If no cap is achieved in 10 minutes then whoever is holding middle point at that time will win the round/game.
Use of RCON
It is expressly forbidden to use RCON in any way which may disrupt or lag an opponent’s connection. Or interfere with the game in general.
Voice Communication
Use of voice communication software is acceptable, either with the use of the in-game comms, or utilities such as Ventrillo, Teamspeak, Mumble, Skype etc. A Mumble server may be set up on-site for users to utilize during competition.
Starting your match
A team must have all the members it intends to field in the server 5 minutes before the scheduled start time of the match. If a match is still in progress on your allocated server, await authorisation from an admin before joining the server.
The only acceptable excuses for missing the scheduled start of a match are:
- Network failure
- Server failure
- Power failure
Server Crashes
In the event of a server crash, the server will be restarted and the teams will allow each other to cap up to match the scoreboard of before the crash. The round being played when the crash occurred will be restarted. In the event a server continually crashes the admin will advise you on the procedure and may require you to move to a different server to complete the game.
Rule Changes
The Administrators reserve the right to modify the rules as needed. This includes changes due to software updates or releases, event organizer decisions and all other changes deemed necessary to run a successful tournament. Teams are responsible to check the rules on a regular basis and prior to the event to ensure they are in complete compliance. Teams must understand that rules listed are guidelines to ensure fair and competitive play and are subject to interpretation by the administrators based on the spirit of the game.
Cheating & Exploits
All forms of cheating are strictly prohibited – any player found to be cheating will be banned without recourse.
The use of any forbidden program or file by a team member during a match will lead to the disqualification of that player from the tournament. Disallowed practices include, but are not limited to, the following:
- Exploitation of game/map bugs/exploits that give an unfair advantage.
- Scripts and external programs that provide an unfair advantage, e.g. HL speed cheat.
- Use of custom models and skins. This goes for the player models/skins as well as the weapon models/skins e.g. longer weapons to stick out from behind boxes, bright or oversized skins.
- Use of custom map textures.
- Use of aimbots, wallhacks and any exploitations of the engine.
- Taunt Bug is forbidden
- The tournament admins may inspect your machine for evidence of cheats/hacks; these may be random checks or as a response to a complaint.
- Use of hardware that simulates timed button presses, e.g. a rapid fire script on a keyboard. Binds, macros or any hardware- or software-assisted script that would enable bunny hopping, rapid fire, or any gameplay not permitted within the normal game mechanics.
Default Skins/Models/Files/Maps are REQUIRED
