The Gathering - Game-compo rules

Game-compo rules

By Joakim Espevik
Published: 11. Mar 2008, 23:30

Here are the rules for all the game-compos

Command and Conquer 3: Tiberium Wars
Wartcraft 3: The Frozen Throne
Counter-Strike: Source
Counter-Strike 1.6
Quake 4
Call of Duty 4

Command and Conquer 3: Tiberium Wars

The tournament:

Game version: Command and Conquer 3: Tiberium Wars v. 1.09
1v1
Double elimination
All games will be played as bo1 until there are 8 players left. After which, the games will be played as bo3.
The looser brackets starts in round 3, which means that players who lost in round 1 and 2 are out of the tourney. If you loose in round 3 or one of the later rounds, you will be moved to the looser bracket.
All games in the loser bracket will be played as bo3.
The winner of each mach is determined upon either of the following conditions: 1. The opponent gives up, or 2. The base of the opponent is completely destroyed.
The winner have to report the game on partyticket.net within 15 minutes after the game is finished. The looser must also go to partyticket.net and accept the result.
The defeated player renounces his right to complain on the match by accepting the submitted result on partyticket.net

General rules

Before joining the tournament, the player must read and understand the rules. Any change of rules will be listed on gathering.org.
Each player can choose the race he or she wants. Choosing random is allowed, as well.
Each player must save the replays of each match. This is due to potential disruptions among players, or any other problems for that matter.
Players are required to enter the “Tournament 1” lobby at least 10 minutes before the game is scheduled to commence. Playing via LAN or Hamachi is allowed if both players wish so.
If a player does not show up in time for a game (that is, 10 minutes prior to the scheduled event), the opponent will win on walkover.

Game settings

Game speed: Maximum
Initial resources: 10,000
Broadcast: Off
Add random crates: Off

Maps

Tournament Arena
Tournament Rift
Small town USA
Pipeline Problems

All BO1 games will be played on Tournament Arena. BO3 games will start with Tournament Arena and be followed by the choice of the defeated player.

Disconnecting and cheating/abusing

Any use of cheats (maphack etc.), intentional disconnection or bad behaviour may result in disqualification.
Further exploitation of the game's system that is not mentioned in these rules is allowed.
Any disconnection or desync occurring within 3 minutes after the match has started will result in a rematch (if one of the players believes he clearly would have won the match, the replay may be forwarded to the administrator, who in turn may or may not decide whether to restart the game). If a disconnection occurs 3 minutes or more after the game has started, the players may agree to do a rematch, or let the administrator decide the winner. Should the deciding of a winner from the replay be impossible, a rematch is required.
If an administrator finds a player's behaviour innappropriate or another problem occurs, it may lead to consequences, such as disqualification, even though it is not mentioned in the rules.

Rules written by: Simen Li Løkaas (Metalon) and Daniel Laberg (Zeo) from Event:Game

Any changes or updates to rules will be notified on gathering.org. All participants are expected to know and follow all the rules; not knowing them is not valid excuse for not following them.

Warcraft 3: The Frozen Throne

The tournament

Game version: Warcraft 3: The frozen throne v.1.21b
1v1
Double elimination
All games will be played as bo1 until there are 8 players left. After which, the games will be played as bo3.
All games in the loser bracket will be played as bo3.
The looser brackets starts in round 3, which means that players who lost in round 1 and 2 are out of the tourney. If you loose in round 3 or one of the later rounds, you will be moved to the looser bracket.
All games played in the looser bracket will be playes as BO3
The winner of each match is determined upon either of the following conditions: 1. The opponent gives up, or 2. The base of the opponent is completely destroyed. The winner have to report the game on partyticket.net within 15 minutes after the game is finished. The looser must also go to partyticket.net and accept the result.
The defeated player renounces his right to complain on the match by accepting the submitted result on partyticket.net

General rules

Before joining the tournament, the player must read and understand the rules. Any change of rules will be listed on gathering.org.
Each player can choose the race he or she wants. Choosing random and Late pick is allowed, as well.
Each player must save the replays of each match. This is due to potential disruptions among players, or any other problems for that matter.
Players are required be ready at least 10 minutes before the game is scheduled to commence.
Playing via LAN or using Hamachi or the latest version of GG Client is allowed if both players wish so.
If a player does not show up in time for a game (that is, 10 minutes prior to the scheduled event), the opponent will win on walkover.

Game settings

Gamespeed: Fastest
Lock Teams: Yes
Teams Together: No
Full shared unit control: No
Random races: No
Random hero: No
Observers: Full Observers
Visibility: Default

Maps

Terenas Stand
Twisted Meadow
Turtle Rock
Echo Isle
Gnoll Wood

The player seeded highetst starts eliminating a map followed by the second player eliminating another map (veto). With this done there will be 3 maps remaining, these are the maps that will be played that current BO3. The player seeded highest will eliminate one of the 3 remaining maps, then the one other player will eliminate another. This leaves 1 map, which is the map that will be playes the first round of the BO3.
The player that lost the first game will choose the next map, which means he can choose between 2 maps.
The same map may not be played twice during one BO3 match.

Disconnecting and cheating/abusing

Any use of cheats (maphack etc.), intentional disconnection or bad behaviour may result in disqualification.
Further exploitation of the game's system that is not mentioned in these rules is allowed.
Any disconnection or desync occurring within 3 minutes after the match has started will result in a rematch. If a disconnection occurs 3 minutes or more after the game has started, the players may agree to do a rematch, or let the administrator decide the winner. Should the deciding of a winner from the replay be impossible, a rematch is required.
If an admin finds a player’s behaviour inappropriate or another problem occurs, it may lead to consequences, such as disqualification, even though it is not mentioned in the rules.

Rules written by: Simen Li Løkaas (Metalon) and Daniel Laberg (Zeo).

Counter-Strike: Source

1.0 General Information

1.1 Tournament Overview

Game Version Played: Counter-Strike: Source newest available version. Only the newest version will be accepted.
Server IP: Will be advertised by Event:Game in the ship in #tg.css.
Players: 5 vs. 5
Maps: 1 (There will be played two maps in the TG final)
Rounds per map: 30
Winning: The first clan that has 16 rounds have won the match. (not in The Grand Finale) Team change at 15 rounds (mr15).
Time per round: 1:45 minutes
Game Play: Single Elimination will be used for the entire duration of the tournament.

1.2 Tournament Staff

The CS: Source head admin is Jonhoo, but questions can also be directed to Jan-Richard Bjerkås (Event:Game Chief). You can contact us on the event IRC in #tg.game @ Quakenet.

2.0 Participants

2.1 Signups

All signup will be done online through partyticket.net.
Five players must be registered under the same team to be eligible for a tournament spot.

2.2 Teams and Participants

When all the players for your team have signed up, they will be the only players you may field in your player line up for each match. A player can only play for one team. A clan may enter more than one team but players cannot be transferred between teams. Players can not be transferred across parts of the tournament.

By registering and participating in The Gathering tournaments, all participants agree to abide by the rules of the tournament.

3.0 Tournament Format

3.1 Matches

Only de (demolition) maps will be played throughout the CS: Source tournament. These will be picked from the following:

de_nuke
de_inferno
de_cbble
de_train
de_dust2

3.2 MR Rules

The entire tournament will use MR15 rules, with a round time of 1.45 minutes except for the finals. There is no time limit. Both teams play one map, for 15 (MR15) rounds as both Counter-Terrorist and Terrorist. Matches will be won by the team that scores 16 rounds first. Sides will be decided by another knife-round or mutual consent.

3.3 Draws

Draw results are not permitted at any stage in the tournament. If there is a tie (15 - 15), there will be MR3 gaming rules. The first team that achieves 4 rounds are winners. Start money on MR3 is 800$. Sides will be decided by another knife-round or mutual consent.

3.4 Finals

The finals will be played in the game-park near the game crew-area. You are allowed to bring only your own mouse, mouse pad, keyboard and headset. If you wish you use voice-com you must bring your own microphone/headset with microphone. (Standard minijack-connection, fancy stuff as customizing of the compo-machine setup will not be allowed).

During the Grand Finals, two MR15 games will be played on two different maps. In other words, the teams will first play 30 rounds on one map with team change after 15 rounds. Then the teams will play on another map until one team reaches 31 round wins in total with team change after another 15 rounds. The team to reach 31 round wins first have won this years CounterStrike Source compo at The Gathering 2008.

In the case of a draw, standard rules shall apply.

4.0 Match Servers

4.1 Server settings

See bottom

4.2 Spectators & SourceTV

No spectators of any kind will be allowed in game other than the designated admin for that game. SourceTV will be running throughout the tournament, but will not be available for the public except in the finals. It will only be running for capturing game demos. We cannot promise to have the demos available at the event, but will be available for download on inquiry within a week.

4.3 Passwords

All tournament servers will have a passwords assigned. To connect to the servers, follow the IP with the password when connecting via the console. You will be given the password from the tournament staff at Event:Game in the ship before the match at #tg.css.

5.0 Match Rules – General

5.1 Match Starts

If one or both teams are missing a player, they will have 10 minutes to get their player in after the scheduled start-time. If one or both teams do not have all players in-game within these 10 minutes, the team with most players in the game will win. If both teams have the same number of players in the game, the game will begin and the rest of the players can join as they are ready. If they do not show up, the game will be continued as normal. If one team gets more players than the other, the game will also be played as normal.

All members of a team must have a unique clan tag; each member on the team must have the same tag so we can separate the teams from each other. This means that if your clans name is TCP, all clan-members must have the same prefix. (Read: Not [TCP], -TCP-, ]TcP[ etc. You must choose ONE!)

The only acceptable excuses for missing the scheduled start of a match are:

Network failure
Server failure
Power failure

The allocation of teams to terrorist and counter-terrorist will be decided via a knife round or by the mutual consent of the two teams.

5.2 Server Crashes

If the server crashes during a game before the 5th round, the whole match will start all over again. If not, the server will be restarted, the score stays the same and mp_startmoney will be set to 4500.

5.3 Pausing and connection losses

If one or more players drop out of the game, the game must be paused. The team then has 5 minutes to get the player in-game again. The teams are allowed to get a reserve in the game, but if the team is not complete within 5 minutes, the other team can claim victory. Only one pause is allowed per team per match. Pausing happens in freeze time or at end of round.

5.8 Voice Communication

A Ventrilo-server will be available during the matches. There will be public channels for just chatting but also password protected channels for every team if the teams wish to use them. Only official Ventrilo can be used.

5.9 Demos and screenshots

A full demo of the match will be taken by the server using SourceTV. In-eye demos are therefore not required.

6.0 Game-play Rules

6.1 Cheating

Any form of cheating is not allowed. If cheating is detected, this must be reported to the game crew immediately. By immediately is meant that the game should be paused, and the admin should be contacted before any further gaming goes on. Should you suspect someone of cheating, please take an in-eye demo demonstrating why you feel the other team is cheating.

It is entirely up to each team to contact an admin in the case of any questionable actions, admins will not necessarily be watching every match unless complains occur. The team that has a cheater will be disqualified from the entire competition. If a team is in any way interfering with another team while they play or prepare to the game they will be disqualified. Preparation is defined as, but not limited to; sleep, practice games and/or planning.

6.2 Map Exploits

You are not allowed to abuse bugs on the map to gain advantages under any circumstances. If one of these exploits happen by accident (which will be decided by game-crew), up to 5 rounds goes to the opposite team. If less than 5 rounds remain until half game/endgame the team will only loose the remaining rounds to half game/endgame.

Bunny jumping is allowed with a maximum of three people participating. That is, two people helping a third.

Make sure you understand what exploits means. If in doubt, contact the Event:Game crew

Remember to report these cases to Event:Game crew!

Server settings

rcon_password "given_to_cl"
hostname "The Gathering 2008 Official CS:S Server"
sv_password "given_to_cl"
log on
sv_lan 1
sv_unlag 1
sv_airaccelerate 10
sv_allowdownload 0
sv_allowupload 0
sv_cheats 0
sv_maxrate 25000
sv_maxspeed 320
sv_maxupdaterate 120
sv_minrate 20000
sv_minupdaterate 80
sv_pausable 1
sv_alltalk 0
sv_aim 0
sv_airmove 1
mp_autokick 0
mp_autocrosshair 0
mp_autoteambalance 0
mp_allowspectators 0
mp_buytime .25
mp_consistency 1
mp_c4timer 35
mp_fadetoblack 1
mp_falldamage 0
mp_flashlight 1
mp_forcecamera 1
mp_friendlyfire 1
mp_freezetime 15
mp_fraglimit 0
mp_footsteps 1
mp_hostagepenalty 0
mp_limitteams 0
mp_dynamicpricing 0
mp_timelimit 0
mp_logdetail 3
mp_maxrounds 15
mp_playerid 0
mp_roundtime 1.75
mp_startmoney 800
mp_tkpunish 0
mp_winlimit 0
mp_maxrounds 0
mp_timelimit 0
mp_tkpunish 0
mp_spawnprotectiontime 0
cl_interpolate 0
cl_lagcompensation 0
tv_enable 1
tv_autorecord 1
tv_maxclients 0

Counter-Strike 1.6

General

Competition Method: 5 vs. 5 (Team Play, 5 players per team)
The first team to win 16 rounds wins the match.
Extra rounds will be played until the winner is decided
Admin may install third party program and/or join as an observer for tournament operations purposes, such as verifying match results or gathering match data.

General Game Setting

Rounds: 30 Rounds (Max rounds format): 15 rounds as Terrorists and 15 rounds as Counter-Terrorists per team (If a team scores 16 rounds first, the match is ended immediately.)
Victory Condition: The first team to win 16 rounds.
Round Time: 1 minute 45 seconds.
Counter-Strike, Terrorist will be announced before the match or decided by coin toss.
In the case of a tie after regulation, 6 extra rounds will be played. (3 rounds as Terrorists / 3 rounds as Counter-Terrorists per team)
Extra Round restart money: $16,000
In the case of a re-tie after 6 extra rounds as stated above, 6 more extra rounds will be played until the tie is broken.
Official Maps: De_Dust2, De_Inferno, De_Nuke , De_Train
Each map may be modified by the TG.GAME committee. Players will be informed before the tournament of any such modifications)
Only players that are registered on the team, at least before the signup stage 2, are allowed to play. A player can only be on one team, meaning that you cannot play for two different clans in the competition.
Only team leaders are allowed to use public in-game messages (messagemode1) within a match. The rule also applies when dead. Use of messagemode1 by any member other than the team leader shall result in a warning. Other team members must only use team message (messagemode2), while in a match.

All gamers must record INEYE demo!

The demo/screenshot must be saved on your harddisk for at least 48 hours.

Approved Grenade Amounts Per Round

Flashbangs: 2
Grenades: 1
Smoke Grenades: 1

Approved commands

Adjust_crosshair
Left hand
An user can use Activate In-Game-VGUI Command

Default skins must be used.
Any other use of map or program bugs can result in a warning at the minimum or loss by default for the offending team after deliberation and decision by the board of referees at its sole discretion.
The gamma rate can be changed in the video graphic driver.

Tournament Server Settings

mp_autokick 0
mp_autocrosshair 0
mp_autoteambalance 0
mp_buytime 0.25
mp_consistency 1
mp_c4timer 35
mp_fadetoblack 1
mp_flashlight 1
mp_forcechasecam 2
mp_forcecamera 2
mp_footsteps 1
mp_freezetime 15
mp_friendlyfire 1
mp_hostagepenalty 0
mp_limitteams 10
mp_logecho 1
mp_logdetail 3
mp_logfile 1
mp_logmessages 1
mp_maxrounds 0
mp_playerid 1
mp_roundtime 1.75
mp_timelimit 0
mp_tkpunish 0
sv_aim 0
sv_airaccelerate 10
sv_airmove 1
sv_allowdownload 0
sv_allowupload 0
sv_alltalk 0
sv_cheats 0
sv_clienttrace 1
sv_clipmode 0
sv_friction 4
sv_gravity 800
sv_lan_rate 25000
sv_maxrate 25000
sv_maxspeed 320
sv_maxunlag 0.5
sv_maxupdaterate 101
sv_minupdaterate 101
sv_minrate 25000
sv_proxies 1
sv_send_logos 1
sv_send_resources 1
sv_stepsize 18
sv_stopspeed 75
sv_unlag 1
sv_voiceenable 1
sv_unlagsamples 1
sv_unlagpush 0
sys_ticrate 10000
allow_spectators 1
decalfrequency 60
edgefriction 2
host_framerate 0
log on pausable 0

Allowed Setting Values for Client

cl_updaterate 101
cl_cmdrate 101
rate 25000
m_filter 1/0
hud_fastswitch 1/0
zoom_sensitivity_ratio
fps_max 101
cl_dynamiccrosshair 1/0
gamma 1/3
brightness 1/3
cl_minmodels 1/0
cl_shadows 1/0

Players Must be use TG2008 CS GUI

Following client settings may not be changed (Must use the default values)

cl_weather mp_corpse_stay
mp_decals max_shells
max_smokepuffs fastsprites
ex_interp 0.01 for LAN (0.1 for Online)

Unfair Practices Subject to Penalty

Team members may communicate verbally if they are alive in the match or when all team members are dead.
The player is deemed dead when the screen is completely faded to black. If a bug occurs and the screen doesn’t fade to black, the player is deemed dead three seconds after he/she has fallen.
Any player who has died cannot communicate by ANY means (No gesture or verbal communication will be allowed) with any other team member or opponent until the beginning of the next round.
If a player continues to communicate after he/she is killed, the team may be given a warning or lose by default at the referee’s sole discretion.
Boost (2 jump-assist): Only three players at the same time is allowed to boost. That means: two player can help another player.
The players are allowed to move silently by pressing the Duck key repeatedly. A player found using this method with scripts may be given a warning or lose by default at the referee’s sole discretion.

Bunny hopping is allowed without script.

Silent run is allowed without script.

Binding "+duck" to the mouse wheel is forbidden.

Using "+duck" behind a box is authorized.
C4 must be installed at a viewable location. Installing C4 at a location where a boost is required is allowed. You are not allowed to boost while planting the bomb!
Silent C4 installation is considered bug play. Such an offense may result in a warning or loss of all remaining TR rounds at the sole discretion of the board of referees.
Throwing grenades over buildings in all maps are allowed.
Any use of the flash bang bug will result in a warning at the minimum or loss by default for the offending team.
Use of personal model/skins (includes weapon skins)
Use of personal map texture
All cheat programs
Use of map bugs in play (e.g. Map swimming, auto aim, etc.)
Use of unfair but available scripts (e.g. silentrun, attack+use, centerview script, norecoil script, etc.)
The server master can and will check for the use of any unfair practice or script, even those not listed above, during each match.
If referee decides that external conditions (Press, Team Leader, Player, Spectator, etc) give unfair advantage to a player, the team may be given a warning or lose by default at the referee’s sole discretion.
If a problem occurs with flash bang bug, the referee reviews the demo file and the offending team loses the round. The match continues normally.
HLTV Proxy will join the game servers for Tournament Broadcast
1. To test for HLTV flash bugs, players must follow the directions of the server master or referees.

If disconnection occurs during a match

If all the players cannot play due to an unintended, unforeseen accident such as server stoppage,
1. - Before the 3rd round starts: restart the match
2. - After the 3rd round starts: Disconnected player must re-connect to the server. The round is continued unpausing, and if the disconnected player cannot connect to the server, all players must wait during the freeze time after the round until the disconnected player connects to the server. At this time, the match may continue by unpausing. (Not a restart)
If up to 3 of all players are unintentionally disconnected: The score for that round is discarded. The game is paused after the round during the freeze time, and all players wait until the disconnected players are connected to the server. When all players are connected, the match may continue by unpausing the game.
In the case of intentional disconnection, the referee may decide to end the match with the offending team losing by forfeit.
Protests can only be filed by the team leader (i.e.: a player that represents the team)
1. - If a player does not agree to any rules, he/she can express his/her protest to a referee before the completion of a match. Any intentional refusal to connect to the match server can result in a default loss for that team with the decision to be made at the sole discretion of the referee.
If a rematch is decided by the head referee, the team that does not follow this decision will be subject to disqualification.

These rules are for the Gathering 2008 Counter-Strike competition and are subject to modification in the following aspects.

Use of most recent patch/version release of each official game within The Gathering committee’s own discretion.
In-game settings and required factors necessitated by use of most recent patch version/release
Cheat Protection Program release and/or cheat protection functions

Game Admin exclusive rights(IMPORTANT!)

TG.GAME can change this set of rules if it’s needed. This rule is only used if there is special reason for it to be done!

For any kind of questions or anything game-related. Visit us at our IRC channel. #TG.GAME @ Quakenet (ex. irc.quakenet.org)

Please note that this information/page might receive updates up to and during the party.

Quake 4

Tournament

Double elimination with best of three maps
Each player chooses one map and the player with highest seed picks first map
Each player needs to announce BEFORE the match starts which map he chose.
If the score is 1 - 1 after 2 maps then each player chooses one map away and the remaining map will be number three.

Disconnecting from server under match

If a player disconnects when he's loosing, it will be a forfeit to the opponent.
If a player disconnects when he's winning, the match will be played again.

Timeaspect

Each participant needs to be in the #quake4.no channel during the tournament. (Quakenet)
Game-crew expects that the matches will be played when the time is set for matches.
If a player dosen't show up in the time of 20 mniutes, he will forfeit.

Screenshot, demos and rapporting of the results

Each opponent have a responsibility to take demos and screenshot of each match. This is IMPORTANT since the gamecrew won't be spectating the matches. When the match is over, the winner needs to report the results to th0 at #quake4.no
If it will be a match conflict the screenshots and demo will be used as evidence.
It's the newest patch and mod of Quake 4 and Q4max which will be used, information about which version will be announced at the website, forums and #quake4.no
Ip and password will be given from the gamecrew before matches on #quake4.no

Maps that will be played in the tournament

Moson
Placebo effect
Phrantic
Ravage
Torment

Questions? Contant us at game at gathering dot org

Call of Duty 4

20.March 03:38: Rulechanges!
Due to popular demand we have made som changes to our rules regarding Cod4.
The rules are updated with the changes.

1. General

Single elimination in all the preliminary rounds until there are 16 teams left. Then the 16 teams play against the 16 seeded teams. Double elimination (with upper brackets and lower brackets) will be used after that.

The ruleset will be Crossfire Cup with some modification using PAM 4.0Final.

Red-dot removed due to balancing issues.
Sniperfix
Nosway
5 Seconds Planttime
7 Seconds Defusetime
45 Seconds Bombtimer

Gametype: 5on5 Search & Destroy
It will be MR12 (Max Rounds 12)
Roundtime is 2 min
First team to win 13 rounds wins the match.
Every player must remember to record demo each match, and keep them at least 24 hours after the match has been played.
No boosting, only places ingame you can jump without any helpbug abuse may be used.
Bug abusing will get your team banned from the tournament.
To decide sides the teams are to engange in a knife-round, the winner of this round decides wich side they start on. If one of the teams uses any weapons besides knife they loose the knife-round.

In the final there will be played 2 maps, where each team chooses a map to play. The team that comes from the looserbracket has to win both maps to win the tournament. If both teams chooses the same map, the looserbracket team has to choose a new map.

2. Communication

ReWrite is the tournament director and you can find him at #tg.game@Quakenet and in the gamearea.
All teams need to have a Clanleader (CL for short) that are responsible for all communication with the gamecrew.
CL should be the same troughout the LAN, this will make the job easier on us in gamecrew.
All CL`s should be at the IRC channel #tg.game on Quakenet, information regarding the tournament will be given here.
If you need to adress a member of the game-crew on IRC, remember to give us information regarding wich clan you represent before anything else.

3. Behaviour

We request that you behave in a orderly fashion. Rasism, fighting etc is not "orderly". You have been warned!

4. Server

If the server crashes during a game before the 5th round, the whole match will start all over again. If not, the server will be restarted, the score stays the same.

5. Thecnical problems

If 1 or more players experience computer crashes during the match, the game can then be paused to get the player in again within 5 minutes. Only one pause is allowed per team per match. Pausing happens in freeze time or at end of round.

If 1 or more players have network issues that hinder them to connect to the game, report it asap to the gamecrew so we can help to resolve the problem.

6. Cheating

7. Other

The result of every match shall be reported by the winner on Partyticket.net, the loosing team should verify the score asap after the match. If the loosing team fails to verify the score within 15 minutes, contact the Event:game crew.