chuck4abuck Posted July 27, 2010 Share Posted July 27, 2010 Hello , in the pass few days we have seen the same with different guids and when doing pb_plist this comes up Punkbuster client: 5 f69aedd(unkn) ok while the rest show (valid:and a #) this same person shows that each time he logs on the server . i'll appreciated the info Quote Link to comment Share on other sites More sharing options...
Everson Posted July 28, 2010 Share Posted July 28, 2010 Add the following to your Punkbuster config file: pbsv.cfg pb_sv_GuidRelax 0 //[1=UNKN, 2=WRONGIP, 4=DUP (add desired values)]pb_sv_task 0 300 pb_sv_guidrelax 0 // Reset GUID relax This should verify that all clients connecting have valid GUIDs. 2 Quote Link to comment Share on other sites More sharing options...
chuck4abuck Posted August 12, 2010 Author Share Posted August 12, 2010 quick question , has anyone experience any private cheaters coming on with the same erro on their guid , like it was a fake guid ? Quote Link to comment Share on other sites More sharing options...
Everson Posted August 12, 2010 Share Posted August 12, 2010 Did you set your GUID relax to 0 as instructed above? Checked your other config's for a GUID relax variable? and then restarted PB? Quote Link to comment Share on other sites More sharing options...
Benway Posted August 12, 2010 Share Posted August 12, 2010 guid (auth:unkn) is common during clients pb autoupdate and pb init. there is a grace period / a timeout, after that a #101 - #141 kick (click) would follow. 3 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.