[PC - Battlefield 3] #58 Met de langverwachte patch!

Battlefield 3 Conquest
Introduction
Match rules
Optional rules
Maplist
Server settings
Demos and screenshots
GUID's
Miscellaneous rules
Cheating and abuse

Global rules
General
Clans and Players
Ladders
The rating system
Methods of challenging
Arranging matches
Before the match
During the match
After the match
Match conflicts
Last build:
21:12, Nov 16th
1. Introduction

Please take the time to read through our global rules before you start playing in this ladder. These rules not only apply to Battlefield 3 Conquest but all ladders within ClanBase. Knowing the global ladder rules will avoid conflicts and will increase your chances of winning conflicts.

Pay particular attention to our rules on freelancing, linking your accounts and the 24-hour rule, reporting a no-show and the match conflict rules.

The General rules section covers the default punishment for breaking the rules, our right to broadcast matches, the complaints system and what counts as official match rules. The rating system is explained in detail, and provides information about the number one spot.
A list of defined ladder terms can be found here.

2. 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 8on8. If both clans agree you can play with 6 players
No heartbeat: IRNV scope can't be used. The use of it, is prohibited absolutely (therefore who uses it is passibile of penalizations).
A match is played on two maps; each team picks one map. The scores from both maps are added to determine the final score. Matches can end in a draw. If you can't decide which map should be played first, play the map of the challenging clan first.

3. Optional rules

Flag by flag: you can play the flag by flag mode only if both clans agree to that.

4. Maplist

The maplist for Battlefield 3 Conquest is:
Teheran Highway: 32 players Conquest Small (250 tickets)
Caspian Border: 32 players Conquest Small (250 tickets)
Seine Crossing: 32 players Conquest Small (250 tickets)
Operation Firestorm: 32 players Conquest Small (250 tickets)
Noshahar Canals: 32 players Conquest Small (250 tickets)
Kargh Island: 32 players Conquest Small (250 tickets)
Operation Metro: 32 players Conquest Small (250 tickets)
Damavand Peak: 64 players Conquest Large (300 tickets)
Grand Bazaar: 64 players Conquest Large (400 tickets)

5. Server settings

Global server settings:
Punkbuster: ON
FriendlyFire: ON
TeamBalance: OFF
KillCam: OFF
MiniMap: ON
3rdPersonVehicleCameras: ON
CrossHair: ON
Vehicles Spawn Time: 100% (default)
Spawn only on Squadleader: OFF
3DSpotting: ON
MiniMapSpotting: ON
HardCore: OFF
Regenerate Health: ON
Ticketratio: default (250 and 300)
Startdelay: 30s (default)
Vehicles: ON

6. Demos and screenshots

Currently we use the Battlelog Link as the match media. It shows the result and the players. We may change this rule in the future, if more medias like demo are available.

7. GUID's

GUID's are unique identifiers used in games to recognise players. Examples: SteamID, PB guid, CoD2 guid, UT2004 guid, ETpro guid, DMW client nr and Xbox Live Gamertag.
Every player must register his PB guid on the GUID page. Click here to find out how to retrieve and register your GUID. Use the console commands '/pb_plist' or '/pb_power' to show all players' GUID's in a match.
The last change of a GUID can not be done later than 24 hours before a match. Players who did not register the correct GUID more than 24 hours before a match will be considered freelancers.
Only the last entered 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 Master Ban List (MBL) of the PunksBusted admin community are considered cheaters and are not allowed to play in any ladder matches.
For BF3: Every player must register his PB guid on the GUID page. Click here to find out how to retrieve and register your GUID.

8. Miscellaneous rules

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.

9. Cheating and abuse

The cheating and abuse policy applies to all ClanBase 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 ClanBase 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.

Global rules
10. General

If the ladder rules for a specific ladder conflict with these global ladder rules, then the specific rules have precedence.
The proper functioning of the ladder system depends on the sportsmanship of the participating clans. We expect everybody to play by the rules, but also to be flexible when circumstances require it and to be reasonable when an opponent has problems beyond their control.
Not knowing the ladder rules is never a valid excuse for not following them.
ClanBase reserves the right to broadcast every match. This can be done with online game broadcast tools for spectating purposes. The recording of such broadcasts can't be refused by the clans. In many cases ClanBase will allow or ask third parties to broadcast the matches. Spectators may never be charged.
For any questions or comments concerning the ladder or the outcome of conflicts, contact the ladder supervisor by e-mail or CB Private Messages. For any questions or comments concerning the ladder or the outcome of conflicts that the supervisor can't resolve, or for complaints about the supervisor, read here.

Messages not written in English 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.
Agreements and arrangements made in the challenge notes field, on the server or elsewhere are not binding. Only the official ladder rules and settings (maps, optional rules) decided on the challenge form should be followed and be considered as the correct rules. Agreements that contradict the ladder rules will be overruled in conflicts.

For example: In conflicts, we will ignore clans who claim that the opponent agreed that they could use a freelancer on IRC or that the clan had put ‘24-hour rule doesn’t apply’ on the challenge notes and the opponent accepted. Proposed servers are never binding and are ‘suggested’ play locations only.
Disclaimer: references to any gender in any ladder rulebooks within this website do not imply these ladder rules are gender-specific.

11. Clans and Players

Any clan registered on ClanBase can participate in any regular ladder. There are some additional requirements clans must meet before they can join an Invitational ladder described in Invitational ladder rules. For information on how to register your clan on ClanBase, read the FAQ.
It is not forbidden for a player to be a member of more than one clan if the player links their personalities by using the link on the admin page. Any player in more than one clan without linking their personalities will be considered to be a freelancer in all clans except the one they were registered with first, unless the duplicate account is inactive. Account is considered to be inactive if the last login date was over 60 days ago before the match date.

Duplicate accounts will be forcibly merged when they are noticed. Users are notified five days before their accounts will be merged via CB private message to give them a chance to try to prove that the accounts' owner isn't the same. Oldest account will remain as the main account in forced linking. If the oldest account has been abandoned, the next oldest (used) account will remain.
Only players who are registered in a clan on ClanBase can play in ladder matches, and they can only play with the nick (or very similar) they're registered with in that clan. Only players that have been registered as clan member for 24 hours or more are allowed to play for their new clan. Unregistered players, players violating the 24-hour rule and registered clan members who use a different nick or GUID from the one registered on CB will be considered freelancers.

Clans may request another player to be used by the opponent before the match, if their choice is violating this rule. If they cannot replace the player then the match is a no-show.
Once the match starts, neither clan can complain that the other clan is using a player with a different nickname or who hasn't been in the clan for 24 hours. A clan may make a claim of freelancers if their opponent uses a player who has the wrong GUID registered or is an unregistered player, or uses a substitute who is breaking the above rule, or a player changes their name into an unrecognisable nickname during the match.
The above 24-hour rule does not apply to clans that joined the ladder (for the first time only) less than 48 hours before the official match time. The 24-hour rule does not apply to players who were briefly removed from the clan, for instance accidentally by the clanleader, assuming they were in the clan for 24 hours previously. A brief period is considered no longer than 18 hours. Players who are absent for longer than this period will be considered new to the clan again and must be in the clan for a further 24 hours before they are eligible to play.
Using a freelancer in a ladder match will result in a forfeit loss. Using freelancer(s) in multiple matches will result in a temporary suspension of the clan from affected ladders or even all ladders. Violations are accumulated over time. See the punishment guide for specific durations. Freelancers used over a year ago will not count, unless the clan has a long history of using freelancers.

12. Ladders

ClanBase only creates ladders when we believe there's a 'market' for it. When a new game or mod is released, we usually create a European ladder for it first, and country ladders later as the European ladder becomes busier. A game/mod must have been played very actively in CB for a while before we consider making an invitational ladder for it.
If you would like to request a new ClanBase ladder for a new game, mod or an existing game and you think there will be enough interest from other clans to make it competitive - please start a petition (or vote for an existing petition) using this page.
Next, we will consider adding the ladder, based on the popularity of the game or mod and based on our relevant expertise in order to provide a great working ladder. There is no set number of votes that will ensure a ladder or game is added. The ladder/game may be rejected if it has been tried before and failed.
Country/region ladders may be restricted to clans of the corresponding nationality, appearing in the Regional Ladders section of the rules. Not every ladder has these rules, but the restriction for all regional ladders is that matches for country/region ladders have to be played on servers in that country/region, unless both clans prefer not to. When clans play on a server not within the region, neither clan can later dispute the score because of it, as when a match starts – servers and settings are accepted. Disputes need to be settled before the match starts.
It is possible to have special coverage in the ladder pages about interesting matches, interviews etc. if game crew and community are motivated & active enough. Ladders can have a separate coverage supervisor who isn't directly involved in running the ladder.
The inactivity system will remove clans from all the ladders with more than 20 active clans, who haven't played for 8 weeks. Read here for more info. The inactivity system is designed not to work on ladders with no or little activity. Dormant clans will not be forcibly removed from inactive ladders by the ladder chiefs unless they hold the number one spot. Please do not ask us to do so, alternatively challenge more active clans in the ladder.
The gold, silver, and bronze ladder icons can be obtained only in large/active ladders. These icons feature next to the clan’s name.
Playing several matches against the same opponent in a short period of time is considered cheating as it distorts the ranking. As a rule of thumb, never play the same opponent twice in less than one week unless you also play many other matches. Playing the same opponent three or more times in one ladder or over many ladders will result in short-term suspensions as described here. In case of grave violations it will be assumed the matches are fake.
Clans without the required amount of players can be removed from the ladder after 7 days.
When a possible fake match is discovered, both clans involved will be suspended from all ClanBase ladders without warning. Players who create 3 or more fake clan matches gets their accounts removed. See the punishment table.
Clanleaders have 1 week to appeal against this decision, but they must supply proof of the match in the form of screenshots or demos and post them on the war summary page. Players should then mail/CB pm the supervisor that reported them. If supervisor's details weren't included in the clan's suspension/deletion notes, you should email the Chiefs of Ladders
Clan won't be punished for a fake match if all the following criteria are met:
Clan leader didn't arrange the fake match.
The clan (leader or a trustee) reports the fake match to ladder's supervisors via CB PM and war summary page's comments page before 48 hours have passed of the fake match's 'starting time'. Tell in the war summary page also to which supervisors you reported the fake match, including their nick and link to their CB profile.
The person responsible of the fake match is removed from the clan as soon as possible after the fake match is noticed and the clan leader gets online. If it's uncertain who did the fake match, ladder supervisor can be consulted regarding it.

This can only be used three times per year and clans trying to abuse this by reporting matches that aren't actually fake will lose the right to use this for a year.

13. The rating system

ClanBase ladders use a rating system based on the ELO system known from chess. Every clan starts with a rating of 1000 points. After each match, points are added or subtracted based on whether the outcome of the match was a win, a loss or a draw (the score has no importance).
How many points you gain after a win or lose after a defeat depends on the rating difference between you and your opponent before the match. The ELO formula is very complicated, but the following easy examples will give you a good idea:
Beating an opponent with the exact same rating gets you 60 points.
The maximum amount of points you can win for a single victory is 120, but to get this many points you'll have to beat an opponent who is 700 or more points ahead of you in the ranking. You get 100 points for beating an opponent who is 200 points ahead.
Beating lower ranked opponents gets you less than 60 points. If they were 200 points below you you only gain 20 points, if they were 300 points below you only get 10 points, and if they were 400 points below you get a mere 5 points.
If a match ends in a draw you will gain points if your opponent was ranked higher, or lose points if they were ranked lower.
The number of points you can win and the number of points you can lose always add up to 120. So if you can only win 30 points with a victory, you can lose 90 points with a defeat.
Against clans that have played less than 3 matches in a ladder, you only win or lose half the amount of points you could win or lose.
The ladder leader does not have a rating, but is considered to have an infinite rating instead. Top 5 clans can take the top spot by challenging the current ladder leader and beating them in a direct confrontation. If that happens they become the new ladder leader while the old leader will return to the normal ranking with the points they had before. If the challenger loses or plays a draw, the ladder leader’s position doesn’t change.
The ladder leader is not allowed to refuse playing the other top 5 clans without a valid reason (valid decline options are proposed by the system, see Arranging Matches). Repeatedly rescheduling to senseless dates or with non-default match rules or only playing lower ranked clans in order to be able to decline challenges will be considered abusing the ladder system and the clan will risk being removed from the first spot, and suspended. You need to provide the supervisors with valid match IDs (wid) of matches they have declined or we will not act.
Clans at the number one spot who are legitimately beaten may not create a war, accept and confirm the score with a 2nd clan before the score to the original one has been confirmed - so that the 2nd clan gets the number one spot.
Clans outside the top 5 can also challenge the ladder leader, but such challenges can be declined freely. If the ladder leader is beaten then they're switched with the second ranked clan while the challenger gains 120 points. If the ladder leader wins, nothing changes.
In case the number one has been deleted for ladder, cup or C&A violations, the second clan in the ladder is set to number one.

14. Methods of challenging

There are several methods in which to find clans to play against:
Direct challenges
Open challenges
Automatches
IRC requests
LAN matches
Direct challenges are challenges where you challenge specific clans you have selected yourself. They can be made by clicking the challenge cross on the ladder's rating page or recently joined page to the right of the clan's name, or to the right of a ladder's name on a clan's matches page. The challenged clan is required to confirm the challenge, decline it or reschedule the time.
Open Challenges (OC) can be created by members without specifying who their opponent is. Their matches are then advertised and other clans can search for matches they want. The OC creator sets criteria which clans must reach, including judge rating, proposed maps and ladder ranking. Once accepted an OC becomes a regular match where all the rules in this book apply. Clans can create up to 3 OCs per ladder and cannot accept more than one OC from the same opponent.
Automatches are matches randomly scheduled by CB which clans set up with an automatch entry. CB pairs opponents if their entry settings match each other's. Once a match is created from an automatch entry - all the same rules apply as direct challenges. Turning up to the match is obligatory. Clans can make up to 7 automatches per ladder. Times between automatch entries cannot overlap.
IRC requests - Users are allowed to use CB game channels (i.e. #clanbase.bf3) to search for ClanBase wars, within reason. If someone cannot find an opponent straight after making a request they shouldn't spam the request again or they may be removed from the channel.
LANs - Clans should not play ladder matches at LANs as they may be mistaken for fake matches, unless the following precautions are taken:
You arrange friendly matches only, OR
You arrange the match in advance of the LAN and sort out the scores after the LAN has finished OR
You upload demos immediately after the match, or post match screenshots showing the final scores.

15. Arranging matches

The deadline for reacting to a challenge is 7 days after the challenge or 7 days before the war, whichever is later. If by the deadline the opponent still hasn't reacted to the challenge, they get a penalty of 5 points. If the ladder leader ignores such a challenge, they will lose their position to the second clan. You can set an earlier deadline for accepting the challenge, but then there is no penalty if the opponent doesn't react in time.
You can only refuse a challenge from another clan in the following cases:
Reschedule: You want to reschedule the match to another date. This date has to be within 14 days of the original challenge.
Unequal match: There is a gap of 10 ranking positions and 100 points between you and your opponent, or you have more than 1100 points and it's your opponent's first match.
Busy in this ladder: you already have 2 or more matches in this ladder in the next 30 days.
Custom maps: the opponent selected custom maps.
Declinable matchrule: the opponent selected a declinable match rule in the challenge form.
Hibernate: you want to set your clan as inactive in this ladder. You lose 32 points but after that you can decline all challenges. All your scheduled matches are cancelled when you go into hibernation. Hibernation ends automatically when you play an official match for this ladder again.
These options are only available for the ladder leader:
Unequal match: The challenging clan is not ranked in the top 5 of the ladder.
Resign: Using this option will make the ladder leader lose it's position in the ladder to the second ranked clan.
If you don't want to play the match for some other reason, you'll have to contact the other clan (e-mail, IRC, MSN, XFire) and persuade them to cancel their challenge.
A scheduled match can be cancelled until 12 hours before the starting time on the Agenda. The side that wishes to cancel the match will either have to request a reschedule or go into hibernation.
When both clans agree not to play a match it can be cancelled for any reason after its scheduled starting time. Just choose the 'Match was cancelled' option on the result form.
If a match is played without being arranged on ClanBase first, then both sides are depending on each other's sportsmanship to accept the result afterwards. We will not force match results when there was no accepted challenge for that match.

16. Before the match

To find your opponent before a match, you should look on their clan channel on IRC or contact them directly through ClanBase private message (aka CB PM), Xfire, MSN or any other means if you don't use IRC.
If you still haven't managed to get in touch with your opponent 10 minutes after the scheduled starting time of the war, you can fill in a no-show. Report a no-show by posting a clear comment on the war page and tell why the match is a no-show and what you've done to contact your opponent. No-shows reported 20 minutes after the official match time will be ignored.
To contest this, the other clan must also log a no-show report in the match page comments.
If you're more than 10 minutes late, you have to accept a no-show if your opponent insists. If you feel there's a good reason the result shouldn't be a no-show, you'll have to convince your opponent of that.
If one clan is short of players or refuses to start the match with the rules agreed upon in the challenge form, the other clan can demand a no-show to be filled in. Remember that challenge notes, the proposed server and agreements made elsewhere are not considered to be binding rules.
Repeatedly not showing up for matches will result in removal and suspensions.

17. 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, ClanBase can change it to the advantage of the clan that stayed.

18. After the match

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.
In case of a no-show/forfeit it's strictly forbidden to fill in any score (even 1-0), even when both clans agree. Instead you must check the no-show/forfeit box on the result form, which will result in a fixed penalty of 10 points for the clan not showing up or 120 in case of forfeit. No-show/forfeit matches where a score has been entered may be cancelled or changed to a no-show/forfeit without warning.
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).
Both clans do nothing for 4 days, after which the score is accepted automatically.
Clans may not confirm a no-show/forfeit instead of the real score to get more points, unless a no-show/forfeit is the punishment for violating a rule. Clans that put in an excessive no. of no-shows/forfeits instead of the correct score will be suspended. To avoid this, ensure that you report a match as a no-show in the match page comments at the match time.
Clans are expected to have proof of their match being played for one week after the score has been confirmed in ClanBase.
Clans should provide an accurate Player of the Match list. Supervisors may alter or remove a clan's PotM list if the wrong players were added or an excessive number of members were added to the list.

19. Match conflicts

The match conflict system functions as a court room with ClanBase 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.

News • Forums • LAN Events • Downloads • Demos • FAQ • Help Desk • About • Contact • Terms & Conditions • Privacy Policy • RSS RSS

Copyright � 2011 GGL Global Gaming.

Sideshowbobbie	dinsdag 22 november 2011 @ 13:03
	Algemene beschrijving In Battlefield 3 ervaar je de intense werkelijkheid van de oorlog als nooit tevoren. Dankzij Frostbite 2, de nieuwe generatie van DICE’s baanbrekende game-engine, staat Battlefield 3 garant voor spectaculaire grafische effecten, verbluffende verwoestingen en een gameplay die zo echt is dat je de kogels langs je oren voelt vliegen. Met deze FPS-ervaring stort je je midden in een oorlog die al je zintuigen overbelast. Het ene moment sta je op een heuveltop. Je luistert naar het geluid van machinegeweren in de verte. Vanuit het stadje dat je gaat binnenvallen worden luchtraketten afgeschoten en even word je afgeleid door het mooie schouwspel van zonlicht en rook. Het volgende moment ren je door de stad. Je bent omsingeld door de vijand, op de rand van een paniekaanval en je vecht voor je leven. Al je zintuigen staan op scherp en je hoopt maar dat het gebouw waarachter je dekking hebt gezocht je redding is, en niet je dood wordt. Welkom bij Battlefield 3. Algemene informatie Naam: Battlefield 3 Release datum: 25 Oktober 2011 Platform(en): PC, PlayStation 3 and Xbox 360 Uitgever(s): Electronic Arts Ontwikkelaar(s): DICE SPOILER: Video's Battlefield 3 - What We Know So Far (Release, Beta, Maps, Squads, Classes) Battlefield 3 - Teaser Battlefield 3 - Back to Karkand Expansion, Locations & Lighting System Battlefield 3 - Leaked Scans: Singleplayer & Multiplayer Intel Battlefield 3 - Gameplay Debut Trailer Battlefield 3 - GameStar Info & New Screens Battlefield 3 - Gameplay Trailer Analysis FOK! TS server: 178.63.54.5:9987 BoF #1 Rush Server (max 32 slots): NL -=Band of Fok!kers=- Ranked, Rush Much? Admins: jpjedi Civilian Bogardo BoF #2 CQ Server (max 32 slots): i3D.net -=band of fok!kers=- NL Ranked Admins: jpjedi Dekkered Civilian BoF #3 Server (max 16 slots, ranked flyschool): i3d.net - NL -=Band of Fok!kers=- Flyschool ranked #3 Admins: jpjedi Dekkered Civilian BoF #4 NL -=band of fok!kers=- CQ Ranked NL -=band of fok!kers=- CQ Ranked #4 admins: Rp2009 hiddit Band of FOK!ers Platoon: Band of FOK!ers FOK! Knoekploeg Platoon Platoon: FOK! Knokploeg Platoon SPOILER: Fok! spelers Voor hardware vragen: Topicreeks: [Gamepc] Discussie hardware topic Wil je zelf wat toevoegen aan deze OP ga dan naar hier naartoe. [ Bericht 4% gewijzigd door Sideshowbobbie op 22-11-2011 13:39:34 ]
Sideshowbobbie	dinsdag 22 november 2011 @ 13:03
	En weer verder
Spelvout	dinsdag 22 november 2011 @ 13:03
	Ben benieuwd of dat "BF3 has stopped working" is opgelost als je de eerste keer BF3 start.. vanavond maar eens testen.
Sideshowbobbie	dinsdag 22 november 2011 @ 13:04
	quote: Op dinsdag 22 november 2011 13:03 schreef Spelvout het volgende: Ben benieuwd of dat "BF3 has stopped working" is opgelost als je de eerste keer BF3 start.. vanavond maar eens testen. Bij mij niet in ieder geval
Augustus_Thijs	dinsdag 22 november 2011 @ 13:04
	Na die patch wil die stomme game geen enkele server meer joinen, teh fuck
Jorwol	dinsdag 22 november 2011 @ 13:04
	quote: Op dinsdag 22 november 2011 13:04 schreef Sideshowbobbie het volgende: [..] Bij mij niet in ieder geval Bij mij ook niet!
Re.active	dinsdag 22 november 2011 @ 13:05
	quote: Op dinsdag 22 november 2011 13:04 schreef Augustus_Thijs het volgende: Na die patch wil die stomme game geen enkele server meer joinen, teh fuck Same here.
Spelvout	dinsdag 22 november 2011 @ 13:05
	Lekkere patch zo te horen
Re.active	dinsdag 22 november 2011 @ 13:06
	-edit-
jpjedi	dinsdag 22 november 2011 @ 13:10
	Vaag zeg, ik heb de WIKI bewerkt maar niet alle sigs worden weergegeven in de OP. de server informatie is ook weer de oude, die niet meer klopt.
Thybalt	dinsdag 22 november 2011 @ 13:10
	Net gekocht, nu aan het installen, ben benieuwd.
CocaColaLight	dinsdag 22 november 2011 @ 13:10
	Naar het schijnt helpt het updaten van punkbuster. Net even in de middag pauze even een potje gespeeld. Voor mijn gevoel duurt het laden wat langer dan voor de patch. Op een paar servers kreeg ik random meldingen waarom ik eruit gegooid zou zijn. Maar na een reboot mocht ik in eens wel connecten...
Pakspul	dinsdag 22 november 2011 @ 13:12
	Gisteren gewoon 39000 punten gescoord in een potje
JK	dinsdag 22 november 2011 @ 13:13
	Deze javalin raket geeft helemaaaaal geen schade; http://www.telegraaf.nl/v(...)sraket__.html?p=19,2
Augustus_Thijs	dinsdag 22 november 2011 @ 13:15
	Ok, joinen lukt nu wel(maar nog niet bij alle servers lijkt wel). Nieuw 'probleem', of ik schrok me iig dood net . Ik game met keyboard en heb mn gamepad op mn computer liggen voor als ik in een jet stap. Dus ik speel lekker, begint ineens mn kast als een idioot te trillen . Blijkt die patch dus de 'rumble'-functie van mn gamepad aan te hebben geschakeld. En geen idee hoe ik dat nou weer uitgezet krijg
Sideshowbobbie	dinsdag 22 november 2011 @ 13:15
	quote: Op dinsdag 22 november 2011 13:10 schreef jpjedi het volgende: Vaag zeg, ik heb de WIKI bewerkt maar niet alle sigs worden weergegeven in de OP. de server informatie is ook weer de oude, die niet meer klopt. Jij hebt nog een recente post van alle sigs toch? Dan zet ik die er zelf wel even in
jpjedi	dinsdag 22 november 2011 @ 13:19
	quote: Op dinsdag 22 november 2011 13:15 schreef Sideshowbobbie het volgende: [..] Jij hebt nog een recente post van alle sigs toch? Dan zet ik die er zelf wel even in vaag, ik kijk in de wiki en daar klopt het wel.. ik heb je de lijst gepm'd. De server info moet eigenlijk ook geupdate worden.
jpjedi	dinsdag 22 november 2011 @ 13:22
	en de servers zijn er weer op 4 players to start trouwens, dat is het minimum nu. ik log in op #2 om hem te laten starten
Auti	dinsdag 22 november 2011 @ 13:26
	En die crashed..
jpjedi	dinsdag 22 november 2011 @ 13:27
	quote: Op dinsdag 22 november 2011 13:26 schreef Auti het volgende: En die crashed.. ik werd er ook uit gemikt inderdaad, ik log weer in.