-
This is EA's reply. What should I do then? I can't complain about the lack of evidence
Paste the banreason in the ticket:
PunkBuster Server: VIOLATION (AIMBOT) #52120: Zhaobozqwqeqwz (slot #1) Violation (AIMBOT) #52120 [33e29fe5bdfa688d4430b11ded195740(-) 185.211.132.xxx:3659]
Data exception is network delay and packet loss
And this is PB said me：
https://www.evenbalance.com/troubleticket/update_ticket.php?ticketnumber
Ticket Information
Ticket Number: EB2847000946189 Ticket Password: Ticket Status: New I've Agreed to the PunkBuster EULA: Yes Created: 06/01/2018 10:59:24
-
They have not responded to you yet. You need to be patient. Do not create any more threads
-
How many days will PB reply to me in the mail?
-
Can take a week or two, but generally they are faster.
Removed the ticket password to prevent the ticket to get spammed. Never post it in public.
Edited: | 5 years ago
-
So the complaint I uploaded in the last two days won't come back, but I have to wait a few days, because I can't find other materials that I'm not Aimbot so I'm very anxious.
-
You have to wait for a response in the ticket you provided here. As I said, do not post that link anywhere else.
| 5 years ago -
Has there been an update by EB? -
I have found my problem, my GUID is unusual, self start playing the game is an exception, in theory is not playing games, but I have been playing, the network causes PB initialization failed, 0.0001 of the probability actually entered the server, I do not know whether the network or PB bug
-
Has there been any updates from EB on your case?
| 5 years ago
-
No, I have reported the problem in detail, but they haven't had a very good response.
-
Investigating your case now. If nothing is found besides the violation then we will reconsider your ban.
Edited: | 5 years ago -
This is their reply. I have explained in detail why I am being called. They always replied to me like this.Below is my PB complaint file and a reply from PB
[05.26.2018 15:28:44] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:29:09] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:29:33] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:29:57] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:30:21] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:30:47] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:31:11] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:31:35] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.26.2018 15:32:02] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.27.2018 23:10:31] Service Communication Failure: PnkBstrB.exe no heartbeats
[05.29.2018 01:10:43] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.29.2018 01:10:53] Violation (AIMBOT) #52120
[05.29.2018 01:13:07] Violation (AIMBOT) #52120
[05.29.2018 01:24:50] Violation (AIMBOT) #52120
[05.29.2018 01:24:54] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.29.2018 01:37:39] Service Communication Failure: PnkBstrB.exe handshaking failed
[05.29.2018 02:17:27] Violation (AIMBOT) #52120
This is my recent GUID, the running of the Windows firewall and PB that led to the failure of the PB initialization, usually I was unable to enter the server, but I entered and played for a period of time before
PunkBuster Server: VIOLATION (AIMBOT) #52120: Zhaobozqwqeqwz (slot #1) The occurrence of 29fe5bdfa688d4430b11ded195740 (-) 185.211.132.xxx:3659]
Trouble Ticket History: 06/17/2018 19:23:31 - "Alex J" 
Note #2: We do not find this violation to be triggered in error, and it will not be removed.
The supplied GUID has been associated with hacking or interfering with the normal operation of our PunkBuster software and has therefore been compromised resulting in a global ban from PunkBuster enabled game servers. We have no way of knowing who was actually playing with this GUID at the time the violation was triggered. We also have no way to know if the violation was triggered on your specific computer. Our system does not collect personal information and furthermore we have no way to attach a cheat/hack violation to a specific person. This ban will not be lifted as then the person who did trigger the violation would again be able to join PunkBuster Servers using this GUID.
To be clear: we are not saying that you cheated as we have no way to know who triggered the violation. If it is certain that no one playing on your computer ever had a cheat/hack violation triggered by PunkBuster, then your GUID (cdkey and/or game account password) has been stolen by or leaked to someone who has used it on a different computer to trigger the violation. We do not have the means to help you find out who is responsible for compromising your GUID.06/15/2018 02:01:23 - "zhaobozqwqeqwz" Note #1: Ticket submitted to support staff. -
Denied as you did not trigger this violation in error.
| 5 years ago
