Proof
Bans for cheating on our servers should have solid proof.
BF4DB’s Ban Policy
Credit to BF4DB’s Ban Policy
In order for a player ban to be made by BF4DB, the following conditions must be met:
Last Updated: 03-04-2019
ACCEPTING THESE TERMS
By accessing any part of the Service, you are agreeing to be bound by the terms of this Policy. If you disagree with any part of this Policy, please do not use the Service. Clarifications of this Policy will be made available upon written request to [email protected].
PLAYER GAMEPLAY RESTRICTIONS
Players who are banned by BF4DB will be subject to removal from servers running in the Ranked game mode that are also running the BF4DB Procon plugin at the discretion of the owner of the server. Players who are banned by BF4DB will be subject to having their information streamed to BF4DB on servers running in the Official game mode that are also running the BF4DB Procon plugin but will not be removed. Player information (including PBGUID, EAGUID, IPv4 Address, and Username) is streamed to the Service regardless of game mode, as long as the server is running the BF4DB Procon plugin. Any new account created by a player that is banned will also be banned if it determined to be the same individual.
BANNING POLICY
In order for a player ban to be made by BF4DB, the following conditions must be met:
Linked Accounts:
- Accounts having overlapping IP and timestamp information will be considered a linked account. Player information streamed to the Service can be used for this purpose.
- If an account is currently banned by BF4DB, all other accounts that are positively identified as a linked account will receive a ban for “Linked Account” as well. Similarly, if the main ban successfully appeals, all other alt bans will be lifted.
- Accounts having the same Gravatar will be considered linked, and treated appropriately.
Stat Evidence:
- Stat-based bans will be considered on a case by case basis – any bans based specifically on stats must be detailed by the admin;
- Abnormal ACC (accuracy);
- Abnormal HSKR (head shot kill ratio);
- Abnormal DMG (damage per hit);
- Round Evidence:
- Abnormal stats for that round;
- Abnormal spotting ribbons per round;
- No weapon based kills, magic bullet;
- Indication of pick-ups used in a round unavailable to that specific map;
Video Evidence:
- All video evidence must be a minimum of one minute in length, although two minutes is preferred to show context of the video.
- All videos must be unedited, with a preferred resolution of at least 720p.
- Videos that are incomplete, muted, edited, modified, or not the original upload may not be used.
Punkbuster Evidence:
- Punkbuster Violations may ONLY be used as supporting evidence in a case against a player, per our policy change (read more here).
- Punkbuster Global bans may ONLY be used as supporting evidence in a case against a player.
- Punkbuster Screenshots submitted must be unaltered and unedited.
- Third-Party software that has the capability of overlaying any kind of crosshair is not permitted by EA TOS and will result in a BF4DB ban for “Dirty PBSS”.
Third Party Evidence:
- Accounts on known cheat or script sites with matching usernames are circumstantial and cannot be the basis of a ban, but may be used as supporting evidence.
- Bans issued by other Anti-Cheat services for any Punkbuster-related issue will NOT be enforced on BF4DB, per our policy change (read more here).
- Resources from ACI (History Tool screenshots, etc) are not to be posted publicly, and must be submitted privately to any Moderator, Administrator, or Director. Other third-party service policies on data sharing must be respected, and any violating information will be removed.
- Bans that are issued by clans, communities, or individual server administrators will not be accepted without evidence to support the hacking/cheating claim.
Fair Fight Resets / Bans:
- Any evidence of a Fair Fight reset and/or ban will result in a BF4DB ban being issued.
Terms of Service Violations:
- Those players who are found to be violating EA’s Terms of Service will be flagged for ToS Violations. This flag will only be added to the offending account, and will not transfer to other accounts owned by the same person.
Glitching:
- Glitches considered to be “game breaking” will result in a ban if proven to be used maliciously. This includes, but is not limited to, invisibility. These will be evaluated on a case-by-case basis.
Software Enhancers:
- Software designed to give the player an unfair advantage (e.g. ASUS’ Sonic Radar, mouse macros, etc.) are violations of EA’s Terms of Service, and will result in a permanent ban.
Server Crashing:
- Individuals being positively identified as being responsible for (or assisting another individual in) intentionally crashing or otherwise disrupting server operations through the use of “crash tools”, exploits, or any other means, will be issued a permanent system-wide BF4DB ban.
- The Directors reserve the right to determine what constitutes sufficient evidence on a case-by-case basis, and all evidence used in a decision will be made available in the individual ban thread.
- Crashing any official BF4DB server will be considered a cyberattack, and will be fully investigated. All information found during the course of the investigation including, but not limited to, IP addresses, GUIDs, EAGUIDs, or other account information will be made available to any law enforcement agency, server hosting provider, or EA/DICE upon request. By joining our servers, you are agreeing to these conditions.
- Those banned for server crashing will also be banned across all media platforms controlled by BF4DB including our website and Discord server.
- Bans for server crashing are lifetime, permanent bans, and will NOT be able to be appealed.
Appeal Escalation:
- Individuals who have posted a ban appeal may escalate their case upon request, provided their ban has not been issued as a result of a Punkbuster Violation. Appeals made for Punkbuster Violations cannot be escalated, as in order for the ban to be lifted, Evenbalance must admit an error was made when the violation was registered.
