Information

CGi Specific Rules

- Teams are allowed to play their games on a private server, but both teams must agree with this.

- Teams are to only use players registered to their CyberGamer TF2 team. Mercenaries are allowed to be used as long as their use is clearly stated to the other team. Mercenaries are not to be used in place of an available registered member, and abuse of this privilege can lead to action against offending teams

- Pro_Dustbowl is to be played in ABBA format, Best of three rounds.

CGi Maplist
cp_well
cp_granary
cp_badlands
cp_gravelpit
cp_prolane_v3
cp_pro_dustbowl

CGo/ TF2 General Rules

Teamsize: 6 (Six)

Notable Server Settings
tf_weapon_criticals "0" (No random critical hits)
tf_damage_disablespread "1" (Consistent damage)
tf_tournament_hide_domination_icons "1" (Domination icons hidden)
tf_use_fixed_weaponspread "1" (Consistent shotgun spread)

Class Limits

2 x Scout
2 x Soldier
2 x Pyro
1 x Demoman
1 x Heavy
1 x Engineer
1 x Medic
2 x Sniper
1 x Spy

Weapons and Unlockables

All weapons/unlocks are allowed to be used in matches EXCEPT for the Scout's unlockable "The Sandman."

Teams or players caught using forbidden unlocks may be punished with suspensions or match forfeits by admin discretion.

Map List
Standard Maps
cp_gravelpit
cp_well
cp_granary
cp_badlands
cp_fastlane
cp_yukon_final
cp_freight_final1

Custom Maps
cp_prolane_rc3
cp_pro_dustbowl
cp_gullywash

- It is strongly recommended that players download custom maps prior to starting a match. There will not be allowances for people to download the map after a match's schedules start time.

Map Rules

cp_well
cp_granary
cp_badlands
cp_fastlane
cp_freight_final1
cp_gullywash
cp_prolane_rc3
cp_yukon_final

In these 5CP maps, the winner is decided by the first team to score 5 round wins or the team which has the most round wins after 30 minutes. Tournament mode enforces scoring; in case of a tied score teams should ready up again, with play continuing until the next round win. The first team to score a round win in this tiebreak will win the match.

cp_gravelpit
cp_gravelpit is played in a 'Best of 3 rounds' format. The winning team is decided by the first team to win 2 rounds, with a round being defined as a turn of attacking and defending. A team wins a round if they capture the most points, or capture the same number of points in a quicker time. A third round is only to be played for tiebreaks.


cp_pro_dustbowl
One round of pro_dustbowl is played, with a round being defined as each team having a turn at attacking and defending. The winner is decided by the team which captures the most points, or captures the same number of points in the quicker time. Tournament mode records capture times, and should correctly indicate the faster team.

Match Protocol

Choosing Teams

The team which issued the challenge may decide whether to start as red or blue.

Players should only join the team that they have been assigned to.

Minimum Players

A minimum of 5 players must be used by a team to play in a match. This number may include a mercenary.

Teams must be ready to play 15 minutes from the scheduled match time. Additional time may not be used to allow a 6th person to join, however this person may join after the match has started.

A team forfeits if they are not able to have 5 players ready after 15 minutes, barring a temporary technical problem. Teams should allow some leniency for temporary technical issues with individuals.

In-game Name
Any competing member in a CyberGamer match must use an in-game username similar to their CyberGamer log in username. This rule is in place to help prevent confusion regarding a member's identity. Failure to use a name similar to your site name without proof of your legitimate membership in the roster may result in action against the offending player or the team he played for.

Ineligible Players
The CyberGamer site will assign "ineligible" tags to team members who sign up following an issued or received challenge. The player tagged as "ineligible" will not be allowed to play in any CyberGamer matches for their team whilst this status is in effect. Breaching of this rule may result in action against the team and/or individual. Any observation of an ineligible player should be reported via a match dispute.

Point Of View Demo

All players are strongly recommended to record a personal demo in matches. Demo recordings are highly valuable in disputes, and a failure to provide a demo in a dispute could lead to no action being taken. Demos can be recorded by entering the following command into the in-game developer's console:
record filenamehere

Mercenaries

A mercenary is defined as a player not registered to a competing team in a match. Mercenaries may be used in the event of a player shortage.
Only ONE mercenary is permitted to be used by a team at once. All mercenaries must be declared by the team using the player and approved by the other team before match start. Mercenaries are not allowed to be used in place of an available registered player.

In the event of a mercenary being acquired mid-game, declaration and approval is still necessary, and teams should cooperate to try and communicate the issue. Keep in mind the opposing team has full say over whether you are allowed to use a mercenary

Match disputes involving mercenaries where proper procedure has not been followed can result in match forfeiture or other action. Teams are encouraged to record a demo in matches involving mercenaries, as we may not be able to make any rulings in disputes without evidence.

Player Connections and Servers

Player connections are the sole responsibility of the individual. Should an issue arise regarding widespread connection problems to the server, then both team captains of that the match should make a dispute and the match will postponed. Postponement of matches will be done so through the dispute section. A CyberGamer admin will reply back and sort the matches out.

If an appropriate alternative server is available, whether a bookable or clan server, teams should try their best to complete the scheduled match on this server. In cases where teams cannot communicate, or a server cannot be found 30 minutes after scheduled start time a dispute should be entered. Teams should allow for an extra 10-15 minutes for the server to be set up. Organisation of alternate servers should be fully communicated between teams, and a lack of communication is not grounds for a forfeit. However, if a team is found to be deliberately unhelpful or cooperative, action may be taken, such as a round forfeit.

Match Completion

After a match has been successfully completed, both teams will need to agree on the score and team captains should enter the result into the fields on the match page. A screen capture of the match result is recommended in case of dispute. Failure to enter a result or deliberately entering a false result may result in match forfeiture or other action against the team.

Other Rules and Enforcement

Exceeding Class Limits

If a player changes class in such a way that their team exceeds the determined Class limit already in play for reasons other than respawning at the current team spawn point or to quickly recover health without reaching the med cabinet may result in action against the player or team.

Team Sportsmanship

Unsportsmanlike behavior will be strictly not tolerated. Such behavior may include but is not limited to:
-Offensive language/banter before, during or after a match
-Deliberately hindering match progress, through lack of communication or otherwise
-Deliberately misleading teams or providing other false information
-Deliberate rule breaking or ignorance
If a team or player is observed exhibiting highly unsportsmanlike behavior the match should be disputed, with evidence provided showing the offense.

Cheating

Using any form of cheat that is designed to give a player a competitive edge over opponents is strictly banned. Such cheats may involve using but is not limited to:
Aim-bot
Wall-transparency or ESP
Trigger-bot
Server configuration bypass
Texture, model or sound modification (Server must be sv_pure 2)

Simply, the client must be run with no modification designed with the purpose of giving a competitive advantage. Please note the section regarding scripts separately. If you are unaware of whether something is classified as a cheat please contact an admin via PM.

Cheating will result in a permanent ban and can include bans to teammates if shown they were aware of your cheating.

Scripts

Most scripting, via the use of console commands, or sets or consoles commands stored in .cfg files is freely allowed. However any scripts designed with the sole purpose of disrupting hit detection, hit boxes or similar is not allowed and can be classified as cheating. As an exception to this, crouch-jump scripts ARE allowed, providing the server limits the number of crouches mid air. If you are unsure of the legitimacy of a specific script feel free to contact an admin.

Exploits and Bugs

Engineer buildings can only be built where they can be damaged by the opposing team with the spawn doors closed.

Jumping over the trains on well during setup time is permitted, however jumping over them via the overhanging lights on red side is not allowed.

Other bugs and exploits must not be used during matches. If a team or individual is observed to be abusing an exploit or bug record their offense and submit a dispute for the match.

Disputes, Administrator Action and Enforcement

Administrators reserve the right to take action against any team or individual at their discretion.

Reporting of any offense is encouraged to take place via a match dispute, available by checking the box on the match page. Once a match has entered into a dispute the administrator team will try to resolve the issue using provided evidence. If there is insufficient evidence from which to make a judgement, action may not be taken. Abuse of the dispute system may result in action against teams or individuals.

If you are in need of assistance or have a question regarding any of the rules, contact an administrator via PM or Steam.