Enforced Ban-MD5-Hub Live-MBI

Idea 1:

How would it be enforced if the option is changed as follows Ban instead of the one entry in the all bans for cheaters say 1 days ~ 1440 minutes will be banned, then a manipulation of PBBans.dat more difficult and there is a clear bans which one only writes his own Bans Ban enforced because only Tempbans it.

Furthermore, many servers do not use the überhaubt Ban enforced here, it would possibly make sense to force this option because otherwise it makes no sense, which captures all the cheaters and the other in turn levers Ban sent his own from which he enforced total ban.

Idea 2:

Many servers not use MCI offered the checks out of ignorance of Admins.Wie would be given the option Auto update MD5 extends the checks are live streams so as soon as you which no checks must register manuel? Had also present the new MD5 checks faster to use and efficient hub of the immensely increased.

Idea 3:
Taskmanager for Generic Bind Scan.Mit this option creates the hub with a task Bindsearches for GBS to each game with the highest effi Binds to look after, so you could also servers across the latest Cheats harder defend.do not have their own tasks that can be the Admin Server Manager in its own tasks (messages) deposit.

Idea 4:
PBSS verification via MD5 Checksumme.Da each screen an MD5 checksum of the log file is stored in the adjustment PBSS via IP actually consists of Stoneage.the screen when you upload to the checksum would also be reviewed to ensure authenticity of the screens and you have not only in the logfiles searching due to the long annoying is.

Idea 5:

30 days delay for MBI Pub view.No Server Admin´s is not should Masterbanindex with 30 days delay to see the Fehlbans to avoid the call of a player he really guilty ruinieren.Ist appears to Ban after 30 days for each visible on the HP, he has otherwise 30 days to prove his innocence.

Comments on the IP's found in the MBI provides:

As more and more providers are fixed IP's distribution should be generally no public IP's show because it actually consists of privacy is prohibited (think also in the USA which is the flagship country in terms of democracy and human rights want to be). Thus, should also Hub Live will be corrected in order to prevent privacy abuses.

Furthermore, one should at Bindsearches displaying Rconbinds hide ... here again the subject of data protection ....

Deze post is bewerkt door Bombcat: mei 14, 2009 - 11:14

PBBans uses live banning. We will not be delaying bans - they will always be live to provide servers with the best protection. If a cheater is caught cheating, why allow them to continue playing? Bans are sent to all streaming servers within a matter of seconds, and that will always remain so.

MD5 updates can be provided via PBUCON already. Check the tickboxes in your account manager.

I'm not sure what you're asking for with idea 3. Are you asking for an option to be able to create custom bind scans?

All PBSS are already verified by MD5 checksum, not by any other information. This ensures that the cheater is banned, even if the GUID has been spoofed in the screenshot (if a screenshot contains a spoofed GUID, the log itself will contain the REAL GUID being used by the player). All log information is also automatically extracted - staff do not have to manually search through logs. SGAs do not have to search through log files either - the IP address is optional to be entered, but not essential.

There is no reason for us to delay the public ban lists. Doing so would only benefit the cheaters.

I am not able to understand your last paragraph.