BF4 ladder rules

#1
BF4 Squad Obliteration 5on5

Game Mode: Squad Obliteration
Team Size: 5on5
Match Media: both scoreboard screenshots

1. Match rules

Game Version: All matches must be played with the latest version of the game.
Teamsize: The default number of players for a match is 5on5.
Two Maps will be played. Two rounds on each map will be played. The amount of destroyed MCOM's of all 4 rounds count for the end result. The team that gained the highest amount of destroyed MCOM's after the 2 maps wins the match.
In case that a map ends in a draw (0-0, 1-1, 2-2, 3-3) is a draw.

2. Maplist

Siege of Shangai
Paracel Storm
Operation Locker
Dawnbreaker
Hainan Resort
Zavod 311
Golmud Railway

3. Server settings

GGC and Punbuster Streaming
The GGC and Punkbuster Streaming Service is mandatory for all matches! Please ensure that your servers are configured properly to avoid any difficulties. The server settings must be checked before the start of the match and may only be contested if they were changed during the match. A protest because of wrong server settings after the match took place will be rejected!

Add the following to your "pbsv.cfg".

pb_sv_AutoSs 1
pb_sv_SsFloor 1
pb_sv_SsCeiling 1000
pb_sv_AutoSsFrom 200
pb_sv_AutoSsTo 600
pb_sv_SsWidth 400
pb_sv_SsHeight 204
pb_sv_SsXpct 50
pb_sv_SsYpct 50
pb_sv_SsSrate 1
pb_sv_SsDelay 3
pb_sv_ssLogging 3
pb_sv_ssTimeout 300

pb_sv_md5toolfreq 50
pb_sv_USessionLimit 10
pb_sv_ucontimeout 300
pb_sv_uconempty
pb_sv_ProtectTag 1 GGC
pb_sv_uconadd 1 69.65.22.152 "pbbhub2-1" "pbbanshub"
pb_sv_uconadd 1 69.65.22.153 "pbbhub2-2" "pbbanshub"
pb_sv_uconadd 1 69.65.22.154 "pbbhub2-3" "pbbanshub"
pb_sv_uconadd 1 85.114.136.131 ggc_85.114.136.131 bf4
pb_sv_uconadd 1 85.114.136.132 ggc_85.114.136.132 bf4
pb_sv_uconadd 1 85.114.136.133 ggc_85.114.136.133 bf4
pb_sv_uconignoreempty
pb_sv_uconignore admin.shutdown
pb_sv_uconignore pb_sv_md5toolfreq
pb_sv_uconignore pb_sv_guidrelax

pb_sv_task 0 3600 pb_sv_ver
pb_sv_task 0 86400 pb_sv_update

pb_sv_load pbsvuser.cfg
pb_sv_load pbsvlog.cfg

pb_sv_writecfg pbucon.use
pb_Sv_writecfg

Global server settings:

punkBuster.activate
fairFight.activate
vars.serverType Private
admin.password ""
vars.serverName ""
vars.bannerUrl ""
vars.serverDescription ""
vars.serverMessage ""
vars.gamePassword ""

vars.alwaysAllowSpectators false
vars.maxSpectators 2

vars.mpExperience SQOBLITERATION
vars.maxPlayers 10
vars.vehicleSpawnAllowed false
vars.commander false
vars.gameModeCounter 100

vars.forceReloadWholeMags 0
vars.autoBalance false
vars.friendlyFire true
vars.idleTimeout 0

vars.teamKillCountForKick 0
vars.teamKillValueForKick 0
vars.teamKillValueIncrease 1
vars.teamKillValueDecreasePerSecond 0
vars.autoBalance false
vars.killCam false
vars.miniMap true
vars.3dSpotting true
vars.miniMapSpotting true
vars.3pCam true
vars.idleBanRounds 0
vars.hitIndicatorsEnabled 1
vars.unlockMode "all"
vars.vehicleSpawnDelay 100
vars.bulletDamage 100
vars.nameTag true
vars.regenerateHealth true
vars.roundRestartPlayerCount -1
vars.roundStartPlayerCount -1
vars.onlySquadLeaderSpawn false
vars.soldierHealth 100
vars.hud true
vars.playerManDownTime 100
vars.playerRespawnTime 100
reservedSlotsList.aggressiveJoin true
vars.roundLockdownCountdown 60
vars.roundTimeLimit 75
vars.teamKillKickForBan 0


4. Demos and screenshots

A scoreboard screenshot of each round is mandatory; showing the player stats, tickets, timecounter.
A screenshot of the scoreboard at the end of each half must be taken and uploaded to the match page within 24 hours.
An admin may extend the upload period of the following matchmedia in special cases.

It is the responsibility of both sides to ensure all screenshots are uploaded to the match page within 24 hours of the end of the match. Screenshots must be uploaded in the following format: .jpg, .jpeg, .png

5. GUID's

GUID's are unique identifiers used in games to recognise players. Examples: SteamID, PB guid.
Every player must register his BF4 PB guid on the GUID page.
The last change of a BF4 PB guid can not be done later than 24 hours before a match. Players who did not register the correct BF4 PB guid more than 24 hours before a match will be considered freelancers.
Only the last entered BF4 PB guid (the one you can see on your account's page) in the changelog will be considered as valid to play with.
Players with GUID's that are listed on the PBBANS and EvenBalance are considered cheaters and are not allowed to play in any AGL matches. Old GUID's from GUID logs aren't valid proof of the person cheating or being banned. It must be verified that the person in question actually triggered the ban before any action will be taken.

6. Miscellaneous rules

Clans are not allowed to share line-ups. Clans should not have more than 50% of their members in other clans, where they are active in the same ladders. Clans will be considered active if they are ranked in those ladders. All violating clans will be warned by email. After this warning, the clans have five days to clear up their members list. Clans still violating the rule after this period will be suspended for 1 month from the involved ladders. Repeated violations will result in a 3-month suspension from all ladders. This rule also applies to ‘multi-gaming’ clans.
If the percentage of players shared is more than 50% of the total number of players in one clan, but is significantly less than 50% in another then only the first clan will be warned. For example, 51% of one clan’s roster also belongs to another clan’s, the other clan has more players so only 30% of its roster is in the first clan – the first clan will be warned, the other won’t.
At least half the line-up used in every match (not 1on1) should be different from those used by any other clan in the same ladder. This does not apply to 2on2 ladders (unless it happens too regularly - both clans use the same line-up in 4 or more occasions) or matches older than 14 days. The following list shows what is not allowed, based on the line-up of two matches, one for each clan:
- 3on3 ladder: two players are the same - 4on4 ladder: three players are the same - 5on5 ladder: three players are the same - 6on6 ladder: four players are the same - 7on7 ladder: four players are the same - And so on

Violating clans will receive a forfeit loss for all of the matches in which they are violating the shared line-up rule. Two or more violations of this rule will also result in suspensions.
If all the players on one team drop because of a technical error, the other team should wait at least 10 minutes before leaving the server.
If one team willingly leaves the server before the match is finished, the clan that stayed is awarded the remaining tickets from both sides.
If the server crashes before 5 minutes of a round has been played, the round will be replayed from the start. If it crashes after the 5th minute, the round should be replayed from the start.
If a server crashes more than 2 times during a match, either clan may demand a server change.
Spectators are NOT allowed on the server.

7. Cheating and abuse

The cheating and abuse policy applies to all AGL ladders. Any cheating or excessive abusive behaviour during a match will result in a forfeit loss. Cheating and/or using suspended players in matches results also in different kind of ladder suspensions.
If both clans cheated and/or used a suspended player in the match, both clans get a forfeit loss.
Ladders are moderated by four methods: join applications, score changes, suspensions and deletions:
Join applications are dealt with by the ladder/mod supervisors to stop fake clans, members with fake GUIDs and countries from the wrong region from entering the ladder.
Matches may be edited to a cancellation, no-show, forfeit loss or a win for the opponent - depending on the ladder rules and severity of the problem. A forfeit loss is the standard punishment for all violations unless the punishment is otherwise stated in the rules.
Suspensions are used to punish abuse of the ladder system and range from short-term to long-term/permanent suspensions, from one ladder only to all ladders. Suspensions are added by the ladder chiefs and assistants.
Punishments are summarised in a table, found here. Clans that are suspended from a ladder may not form the same clan elsewhere to play that ladder, this includes new clans or altered existing clans. The guidelines for determining if a clan with an active suspension has rejoined with a new clan will not be given out so don't ask for them.
If a clan is suspended from a ladder the suspension can be viewed by using the clan's matches page. Appeals to the suspension reporter will only be acknowledged if the accusation against the clan can be proven false. Provide all necessary proof immediately on the war summary page. Members may only contact the ladder assistants/chiefs if the reporter is not mentioned.
Clans or accounts may be deleted without warning as described in the ladder punishments table.
It is strictly forbidden to use accounts of other users, even if the users are in your clan. Such cases will always be considered abuse and subject to temporary bans. This does not apply to players who are forced to share GUID's.
It is not allowed to take advantage of or abuse bugs. Any kind of bug abuse is considered cheating and will lead to a forfeit loss, unless otherwise mentioned specifically in the game-related rules.
All programs or files, either changed game files or new files, that change the game or add to its functionality, or which interact with the game in any way, are strictly forbidden unless other rules specify otherwise. Modified versions of the game's resource files are always forbidden, regardless of what they do. The use of any forbidden program or file by any clan member during a match, leads to a forfeit loss, and could lead to a removal and ban from AGL in major cases.
Programs that do not interact with the game in any way are allowed, even if they can be used and operated simultaneously with the game. Voice communication programs are examples of such programs.
Clans abusing the ladder system in any way in order to gain an advantage or just to be a nuisance will be deleted or suspended from ladder(s). Further punishment may include deletion of the accounts of the person responsible for the abuse, in extreme circumstances. Abusing any clear loopholes in the rules is forbidden, Chiefs of Ladders can punish clans/players for abuse not described in these rules.
All scripts, macros and changes to the game's configuration are not allowed, unless they are specific allowed by this rules. Programs and macros that provide an advantage during game play (e.g. drivers that allow the removing of walls, single shot macros, etc.) are forbidden. Any programs that change the game itself are forbidden.

8. General

Messages not written in English (or Polish) will not be understood and will not be read. Messages containing abusive language will be ignored. Messages will be dismissed by the ladder managers if the controversial issue has not been discussed with the ladder supervisor first, or the ladder supervisor answered correctly but was ignored.

9. Clans and Players

Any clan registered on AGL can participate in any regular ladder.

10. During the match

Once a match has started, its result counts, unless both sides agree it shouldn't. Ping, lag issues or incorrect server settings are no excuse for leaving; you should have checked the server before you started playing.
If one clan walks away from the match, the score at the time when their last player quit can be considered to be the result of the match if the clan that stayed was leading. If the leaving clan was winning but the losing clan could have still won the match, AGL can change it to the advantage of the clan that stayed.

11. After the match

Clans are expected to have proof of their match being played for one week after the score has been confirmed in AGL.
Clans should provide an accurate Player of the Match list.
Either clan can enter the result of a match, unless the other has already done so. A match result can be:
The real score of the match.
A no-show if the opponent didn't show up.
The result reflects the punishment specified in the rules which the opponent violated.
A forfeit if the opponent violated rules with no punishment specified.
Once one clan has entered a result, five things can happen:
The score is edited by the clan that entered it.
The score is accepted by the other clan, and ladder ratings are adjusted accordingly.
The other clan refuses to accept the score, and enters another result.
The other clan refuses to accept the score, making it a match conflict (see below).

10. Match conflicts

The match conflict system functions as a court room with AGL admins acting as judges. A match conflict can be made when the result entered by one clan is not accepted by the other.
If you can't resolve the conflict with your opponent then try entering the appropriate match result first. Only after the opponent changes the result multiple times, you should initiate a conflict. Entering false results will lead to a conflict loss.
The system will not allow the creation of match conflicts during the first 24 hours after the match time, so try to solve the conflict with your opponent by IRC/MSN/Xfire/e-mail or in the match report first. Not making an effort before starting the official match conflict, will result in a conflict loss.
In the conflict both sides must explain the problem in a short but clear and complete way. Both sides should state the match result they claim and only relevant and proven facts may be mentioned. This can be in the match conflict or in the comments located under the conflict case. Failure to make a clear match conflict will lead to a conflict loss.
'Conflict loss' means that a conflict rule (insulting opponent in conflict, entering false score...) mentioned in this chapter was broken. Match score can be a played score like 21-19, no-show or forfeit win (if opponent used freelancer, cheated...) that's based on the rules of other chapters. Winning below means that clan has won according to the match score (can be forfeit/no-show too):
If both clans break a conflict rule, the match score stands.
If losing clan breaks a conflict rule, the match score stands + losing clan might get a warning and/or ladder suspension based on the ladder punishments table.
If clan won by playing and breaks a conflict rule, loser gets a noshow win.
If clan won by forfeit/no-show and breaks a conflict rule, match is canceled.
If the match was tied, breaking a conflict rule leads to a noshow loss.
All proof and information on the match should be written to the conflict page. However, supervisor can use information found in the warpage.
Examples of valid proof are demos, in-game screenshots and server logs that were obtained from a neutral party. Screenshots are used as main means to prove the match's score. Private logs from IRC, MSN etc. or server logs provided by either clan will not be considered to be evidence because they can be easily falsified. If a demo is used as proof of cheating or other malicious actions, you must specify the exact moment(s) (down to the exact minute and second) where the cheating occurred or you will get a conflict loss. Supervisors will not look at entire demos.
Ladder-specific rules tell details on how to request demos and/or screenshots from an opponent. Upload requests can only be made once by both sides. When a requested demo/screenshot upload is complete, the other clan has 3 days (72 hours) to provide all info as how the requested and uploaded items would make proof for their claims; for example exact times that show cheating in a demo. Giving information too late doesn't matter if it's already available when supervisor solves the conflict. Supervisor can give clans more time to give the required info.
Any form of abuse, starting off-topic discussions, making unproven accusations, needless repeating already mentioned facts or any other comments not relevant to solving the case, if done excessively, will result in a conflict loss.
Falsifying evidence in a match conflict results in a ladder suspension as described in the ladder punishments table.
If both clans violated the ladder rules in a way that would award them both a forfeit loss, the match will be cancelled. Such closure of the conflict does not mean proven individual cheating will go unhandled, such cases can be reported to the ladder supervisor by mail/CB pm in order to punish the player(s).
It is strictly forbidden to contact any admin in private to defend your case. Anything you have to say must be said openly. Trying to influence an admin in private will lead to a conflict loss.
Match conflicts are never urgent and the admin will typically let a week go by before looking at a case to give both sides the chance to explain their case. Wait patiently until a decision is made. Only when a conflict is older than one month, you can mail/CB pm the game supervisor. If the conflict involves watching demos, you should wait two months before contacting the game supervisor.
If a clan does not give any new relevant information within 3 days (72 hours) since the last reply, it will be considered they have nothing more to add.
Match conflicts will be judged by the ladder rules at the time of the match and by the match rules agreed upon in the challenge form.
Clans who repeatedly make conflicts will be suspended, if they have no foundation in the rules or they are clearly made for the sole purpose of complicating the match process. Clans who repeatedly violate the ladder rules and force other clans into making conflicts will also be suspended.
Clans are allowed to write conflicts and comments in the language of a regional ladder if the ladder supervisor is from that same region but a translation in English should always be provided as well. In the event the conflict is looked at by another supervisor, everything not mentioned in English will be ignored.
Zablokowany

Wróć do „Battlefield 4”

Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 2 gości

cron