Rulets for PC: Battlefield 2 - 6v6 please read them carefully and remember to re-check them regularily.
Ladder Activity
- Ladder Matches This Week
- 0
- New Teams This Week
- 0
Previous Champions
- CGi Season 1 - May 2009
Rules
Cybergamer BF2 8v8 Ladder
Finals Structure:
Single Elimination
- Matches will be played on Battlefield2 v 1.50
- Matches will be played on any of the maps listed at the end of this document.
- Matches can be played on any night except Tuesday.
- A maximum of sixteen players may be on your team roster at any given time.
- From time to time, Cybergamer Battlefield admins may need to contact you. Any official communication from/to the admin team and you will be conducted by Cybergamer IM or PM. Hence, you should check the site on a regular basis.
- You can challenge half your rank, or four places - whichever is higher.
For example, if you are ranked 30th, you may challenge to rank 15.
However, if you are ranked 6th, you may challenge to rank 2.
- After a challenge is logged, the defending team has 48hrs to accept the match - otherwise a forfeit will be recorded.
- After a match, if the challenger wins, they will take the defenders place, and the defender will drop a single rank.
If the defender wins, they will be "protected" for 48hrs and immune to receiving challenges.
The challenger, having lost, will then be "vulnerable" for 48hrs and unable to make challenges.
- If you forfeit a game through not responding to the challenge or declining the match, you will be made vulnerable.
- After a match, you must enter either your results, or a dispute, by 2330 AEST on the same night as your match.
- A team cannot challenge the same team twice consecutively. If there are no other ladder options, this will automatically be allowed after seven days.
- Players may only play for one team at a time. Admins can and will access logs to verify if multiple Cybergamer accounts and/or ingame GUIDs are in use. You are locked to one GUID per season, if you are found to have logged into a cybergamer server with a different guid than in previous matches that match will be overturned and the win given to your opponent.
- Players may only play in a match if they were present on the roster when the challenge was submitted.
However, if the opposing team wishes to grant an exemption to this rule, a rostered (but ineligible) player may play, subject to both captains sending a PM on the Cybergamer website to a Battlefield Admin (Listed at end of this document.)
If both teams would like to waive, alter or "bend" a rule for their match, they must contact a Battlefield Admin. This is so that we have a record to refer to in case of dispute. A failure to do so will result in both teams forfeiting the match. Note that this is intended for issues such as start times, unrostered players et cetera, not "ZOMG TEH GUISE KNIFE FITE K?"
- Whichever team holds the lower ranking will play USMC in the first round.
- The time issued on the site is the match START TIME. Servers will be up fifteen minutes in advance to allow players to be in server on time.
Matches must start at the scheduled time - that is, no later than fifteen minutes after the server has come online.
If only one team is present in the server at the scheduled time, a forfeit will be awarded in their favour.
- Rounds are run at 150% ticket ratio (150 tickets) and are 30 minutes in duration.
- There is a maximum break of 5 minutes between halves. If going afk, players should change sides BEFORE they go.
If only one team is ready at the end of this time, they are allowed to live the second round, and kick any players on the wrong team.
- Players should use a tag and alias that is as close to their Cybergamer alias as possible. Minimal deviation will be tolerated.
- Note that while substitutions are allowed at any time, teams may have a maximum of eight players in server at any time. That is, the outgoing player must disconnect entirely before their replacement can connect.
- If a team is unable to field eight players, they should play their fixture with as many players as they have available.
- Artillery is not allowed to be used against the opposing team during matches. Firing it out of bounds is acceptable to prevent accidental usage. If a team kills one of your players with artillery you are to global Artillery breach and request all your players screenshot it and resume play. If the enemy team drops artillery within the map without killing anyone but in the path of your team to stop them moving forward also global artillery breach and screenshot it. If there is an artillery breach both teams are required to complete the game. Any team calling a breach then leaving the server will lose the match.
- If you believe you have cause for a dispute, you should get as much evidence as possible while playing, and review the Battlerecorder files after the match. It is imperative that you play out the match, as if it is ruled that no breach has occured, the match score will stand.
Should the server crash mid-round, the following action should be taken:
- If the server crashes for the first time:
The round should be restarted, and play continued, with any points accrued in the "first attempt" at the round disregarded.
- If the server crashes subsequent to the first crash:
Both teams should lodge a dispute stating the server crashed repeatedly. Where possible, the match will be rescheduled at the same time (eg 1900, 2030) within the next three days by an Battlefield Admin. Hence, it is appreciated for teams to list preferred days. If rescheduling is not possible due to other matches, ladder locks or otherwise, the match may simply be cancelled.
- If both teams agree to continue play on a private server:
The settings must mirror Cybergamer match settings (150% ticket ratio, same map, 15 mins roundtime) and sv.autoRecord must be enabled. BR files should also be made available to both teams.
Should the server fail to come online, the following action should be taken:
- If a Battlefield admin can be contacted in any fashion to assist:
Teams should wait up to 30 minutes after the scheduled start of play. If the server can be brought online, the match will be played as normal.
- If a Battlefield admin cannot bring the server online, or cannot be contacted:
Both teams should lodge a dispute stating the server did not come online. Where possible, the match will be rescheduled at the same time (eg 1900, 2030) within the next three days by an Battlefield Admin. Hence, it is appreciated for teams to list preferred days. If rescheduling is not possible due to other matches, ladder locks or otherwise, the match may simply be cancelled.
- Any player connecting with "CASTER" tags is a match coverage official, and is permitted to be in the server without your permission. They should be treated with respect - a failure to do so may result in punishment ranging from a player kick to a match forfeit.
- It is NOT required to wait for match coverage officials to be ready, unless directed to do so by a Battlefield Admin. If in doubt, the golden rule is that the match will ALWAYS come before coverage thereof.
- RCON is not available to players, to start the rounds simply have a member from each team global team ready and the server will restart the round to go live.
Each dispute will be examined on an individual basis.
The question that will come first and foremost is "How did the violation affect the outcome of the match?". We will take action to neutralise the affected result as we see fit.
Note that we may use other supplementary criteria to assist in our decision making.
Admin decisions are final, and no debate will be entered into.
NB: If you choose to wait past the scheduled match time for the other team, disputes based on the starting time will not be considered.
If a player is caught cheating, or is found to have cheated previously:
- They (The player) will be banned from all Cybergamer events permanently.
- If in a match, their team will be forfeited.
- If in a match, their team will be dropped to the bottom of the ladder.
If a player is caught using a "severe" exploit in a Cybergamer match:
- They (The player) will be banned from all Cybergamer events for a three month period.
Depending on the severity of their offence, their team may be forfeited or dropped to the bottom of the ladder.
Admins will have the final say on what constitutes an exploit. If unsure, contact an admin in advance. As a rule of thumb, if you have to ask, the answer is no.
If a player has a history of cheating through any means or method, but you wish to field them, a Battlefield admin must be contacted for approval.
Note that fielding a player banned for cheating infractions, or a Cybergamer banned player, will result in an instant forfeit and drop to the bottom of the ladder.
Please note that CyberGamer expects you to fulfill all your fixtures to the best of your ability.
Anti-competitive behaviour, including, but not limited to, throwing a match, endless "defense of the uncap", constant ingame abuse and similar will not be tolerated.
Team deletion is a highly probable consequence, at admin discretion. No warning are required.
You have been warned.
- Talnoy - PM @ http://www.cybergamer.com.au/inbox/6988/BF2
All instuctions of listed admins should be followed promptly and in the sense they were given. A failure to do so may result in your match being forfeited.
These rules may change at any time, and it is recommended they are checked before your matches.
All decisions of Battlefield Admins are final - no debate or discussions will be entered into. A failure to adhere to this may result in future sanctions against you and/or your team.
daqing_oilfields gpm_cq 16
gulf_of_oman gpm_cq 16
mashtuur_city gpm_cq 16
road_to_jalalabad gpm_cq 16
sharqi_peninsula gpm_cq 16
songhua_stalemate gpm_cq 16
strike_at_karkand gpm_cq 16
fushe_pass gpm_cq 16
kubra_dam gpm_cq 16
operation_clean_sweep gpm_cq 16
dragon_valley gpm_cq 16
wake_island_2007 gpm_cq 16
zatar_wetlands gpm_cq 16
operation_blue_pearl gpm_cq 16
highway_tampa gpm_cq 16
great_wall gpm_cq 16
midnight_sun gpm_cq 16
operationharvest gpm_cq 16
operationroadrage gpm_cq 16
operationsmokescreen gpm_cq 16
taraba_quarry gpm_cq 16
dalian_plant gpm_cq 16
Finals Structure:
Single Elimination
General
- Matches will be played on Battlefield2 v 1.50
- Matches will be played on any of the maps listed at the end of this document.
- Matches can be played on any night except Tuesday.
- A maximum of sixteen players may be on your team roster at any given time.
- From time to time, Cybergamer Battlefield admins may need to contact you. Any official communication from/to the admin team and you will be conducted by Cybergamer IM or PM. Hence, you should check the site on a regular basis.
- You can challenge half your rank, or four places - whichever is higher.
For example, if you are ranked 30th, you may challenge to rank 15.
However, if you are ranked 6th, you may challenge to rank 2.
- After a challenge is logged, the defending team has 48hrs to accept the match - otherwise a forfeit will be recorded.
- After a match, if the challenger wins, they will take the defenders place, and the defender will drop a single rank.
If the defender wins, they will be "protected" for 48hrs and immune to receiving challenges.
The challenger, having lost, will then be "vulnerable" for 48hrs and unable to make challenges.
- If you forfeit a game through not responding to the challenge or declining the match, you will be made vulnerable.
- After a match, you must enter either your results, or a dispute, by 2330 AEST on the same night as your match.
- A team cannot challenge the same team twice consecutively. If there are no other ladder options, this will automatically be allowed after seven days.
- Players may only play for one team at a time. Admins can and will access logs to verify if multiple Cybergamer accounts and/or ingame GUIDs are in use. You are locked to one GUID per season, if you are found to have logged into a cybergamer server with a different guid than in previous matches that match will be overturned and the win given to your opponent.
- Players may only play in a match if they were present on the roster when the challenge was submitted.
However, if the opposing team wishes to grant an exemption to this rule, a rostered (but ineligible) player may play, subject to both captains sending a PM on the Cybergamer website to a Battlefield Admin (Listed at end of this document.)
Gentleman's Agreements
If both teams would like to waive, alter or "bend" a rule for their match, they must contact a Battlefield Admin. This is so that we have a record to refer to in case of dispute. A failure to do so will result in both teams forfeiting the match. Note that this is intended for issues such as start times, unrostered players et cetera, not "ZOMG TEH GUISE KNIFE FITE K?"
Matchplay Rules
- Whichever team holds the lower ranking will play USMC in the first round.
- The time issued on the site is the match START TIME. Servers will be up fifteen minutes in advance to allow players to be in server on time.
Matches must start at the scheduled time - that is, no later than fifteen minutes after the server has come online.
If only one team is present in the server at the scheduled time, a forfeit will be awarded in their favour.
- Rounds are run at 150% ticket ratio (150 tickets) and are 30 minutes in duration.
- There is a maximum break of 5 minutes between halves. If going afk, players should change sides BEFORE they go.
If only one team is ready at the end of this time, they are allowed to live the second round, and kick any players on the wrong team.
- Players should use a tag and alias that is as close to their Cybergamer alias as possible. Minimal deviation will be tolerated.
- Note that while substitutions are allowed at any time, teams may have a maximum of eight players in server at any time. That is, the outgoing player must disconnect entirely before their replacement can connect.
- If a team is unable to field eight players, they should play their fixture with as many players as they have available.
- Artillery is not allowed to be used against the opposing team during matches. Firing it out of bounds is acceptable to prevent accidental usage. If a team kills one of your players with artillery you are to global Artillery breach and request all your players screenshot it and resume play. If the enemy team drops artillery within the map without killing anyone but in the path of your team to stop them moving forward also global artillery breach and screenshot it. If there is an artillery breach both teams are required to complete the game. Any team calling a breach then leaving the server will lose the match.
- If you believe you have cause for a dispute, you should get as much evidence as possible while playing, and review the Battlerecorder files after the match. It is imperative that you play out the match, as if it is ruled that no breach has occured, the match score will stand.
Server Failures
Should the server crash mid-round, the following action should be taken:
- If the server crashes for the first time:
The round should be restarted, and play continued, with any points accrued in the "first attempt" at the round disregarded.
- If the server crashes subsequent to the first crash:
Both teams should lodge a dispute stating the server crashed repeatedly. Where possible, the match will be rescheduled at the same time (eg 1900, 2030) within the next three days by an Battlefield Admin. Hence, it is appreciated for teams to list preferred days. If rescheduling is not possible due to other matches, ladder locks or otherwise, the match may simply be cancelled.
- If both teams agree to continue play on a private server:
The settings must mirror Cybergamer match settings (150% ticket ratio, same map, 15 mins roundtime) and sv.autoRecord must be enabled. BR files should also be made available to both teams.
Should the server fail to come online, the following action should be taken:
- If a Battlefield admin can be contacted in any fashion to assist:
Teams should wait up to 30 minutes after the scheduled start of play. If the server can be brought online, the match will be played as normal.
- If a Battlefield admin cannot bring the server online, or cannot be contacted:
Both teams should lodge a dispute stating the server did not come online. Where possible, the match will be rescheduled at the same time (eg 1900, 2030) within the next three days by an Battlefield Admin. Hence, it is appreciated for teams to list preferred days. If rescheduling is not possible due to other matches, ladder locks or otherwise, the match may simply be cancelled.
Match Coverage & Ingame Administration
- Any player connecting with "CASTER" tags is a match coverage official, and is permitted to be in the server without your permission. They should be treated with respect - a failure to do so may result in punishment ranging from a player kick to a match forfeit.
- It is NOT required to wait for match coverage officials to be ready, unless directed to do so by a Battlefield Admin. If in doubt, the golden rule is that the match will ALWAYS come before coverage thereof.
- RCON is not available to players, to start the rounds simply have a member from each team global team ready and the server will restart the round to go live.
Dispute resolution
Each dispute will be examined on an individual basis.
The question that will come first and foremost is "How did the violation affect the outcome of the match?". We will take action to neutralise the affected result as we see fit.
Note that we may use other supplementary criteria to assist in our decision making.
Admin decisions are final, and no debate will be entered into.
NB: If you choose to wait past the scheduled match time for the other team, disputes based on the starting time will not be considered.
Cheating
If a player is caught cheating, or is found to have cheated previously:
- They (The player) will be banned from all Cybergamer events permanently.
- If in a match, their team will be forfeited.
- If in a match, their team will be dropped to the bottom of the ladder.
If a player is caught using a "severe" exploit in a Cybergamer match:
- They (The player) will be banned from all Cybergamer events for a three month period.
Depending on the severity of their offence, their team may be forfeited or dropped to the bottom of the ladder.
Admins will have the final say on what constitutes an exploit. If unsure, contact an admin in advance. As a rule of thumb, if you have to ask, the answer is no.
If a player has a history of cheating through any means or method, but you wish to field them, a Battlefield admin must be contacted for approval.
Note that fielding a player banned for cheating infractions, or a Cybergamer banned player, will result in an instant forfeit and drop to the bottom of the ladder.
Anticompetitive Behaviour
Please note that CyberGamer expects you to fulfill all your fixtures to the best of your ability.
Anti-competitive behaviour, including, but not limited to, throwing a match, endless "defense of the uncap", constant ingame abuse and similar will not be tolerated.
Team deletion is a highly probable consequence, at admin discretion. No warning are required.
You have been warned.
Battlefield Admins
- Talnoy - PM @ http://www.cybergamer.com.au/inbox/6988/BF2
All instuctions of listed admins should be followed promptly and in the sense they were given. A failure to do so may result in your match being forfeited.
These rules may change at any time, and it is recommended they are checked before your matches.
All decisions of Battlefield Admins are final - no debate or discussions will be entered into. A failure to adhere to this may result in future sanctions against you and/or your team.
1.5 Maplist
daqing_oilfields gpm_cq 16
gulf_of_oman gpm_cq 16
mashtuur_city gpm_cq 16
road_to_jalalabad gpm_cq 16
sharqi_peninsula gpm_cq 16
songhua_stalemate gpm_cq 16
strike_at_karkand gpm_cq 16
fushe_pass gpm_cq 16
kubra_dam gpm_cq 16
operation_clean_sweep gpm_cq 16
dragon_valley gpm_cq 16
wake_island_2007 gpm_cq 16
zatar_wetlands gpm_cq 16
operation_blue_pearl gpm_cq 16
highway_tampa gpm_cq 16
great_wall gpm_cq 16
midnight_sun gpm_cq 16
operationharvest gpm_cq 16
operationroadrage gpm_cq 16
operationsmokescreen gpm_cq 16
taraba_quarry gpm_cq 16
dalian_plant gpm_cq 16
