Deathspike
14-10-2009, 19:15
After trying every known problem, it is often a gamble to find out what goes wrong in Simple Anti-Cheat. When you feel you've tried everything and have following the appropriate steps in the FAQ, you can take the option to take an analytical report of the encountered problems in your system.
How does this work?
Once enabled, the system will keep track of all the encountered problems during the time you've been in a game. When you finally get kicked from the server because SAC didn't quite accept something, you'll see a console with a numeric identifier indicating a problem area. However; This isn't detailed enough and can be much more detailed. To preserve a higher level of security, this kind of data can only be retrieved by submitting it to the master server. To do this, you'll need a access key. This report will contain detailed information about the encountered problems, but will not contain any private information (other then your IP address, just remember every site you visit keeps track of this though).
How do I get an access key?
This is actually quite simple. You'll simply have to send me a private message asking for an access key. When you've received such a key, you'll have to let the system send a report to the master server. This is actually quite easy. When you launch the game, you simply have to open the console (SHIFT + ~) and enter the following: /sacInternal #, where # is the number you receive. Example: /sacInternal 879871, as shown in the screen shot below.
Once a report has been send, it will say it has been accepted (as shown on the screen shot). When you're done, you'll have to send a new message asking for the report (otherwise it's enormously hard to track all the reports I'm expecting). Just keep in mind that if you're indeed cheating, I will not hesitate to post the results including your IP in a public 'cheater' sticky :).
Why the hell do you do this in such a roundabout way?
It's safer to work like this and we can get in a flaming and heated discussion about security, but let's postpone this until the major bugs are out of SAC all right? Good boy!
Please note, if I am on IRC or you have got me in your MSN/XFire buddy list and I'm signed in, communication about analysis is preferred to be done through this method. Also note you'll need to run DVersion.exe to update to the October 14th update, thank you.
How does this work?
Once enabled, the system will keep track of all the encountered problems during the time you've been in a game. When you finally get kicked from the server because SAC didn't quite accept something, you'll see a console with a numeric identifier indicating a problem area. However; This isn't detailed enough and can be much more detailed. To preserve a higher level of security, this kind of data can only be retrieved by submitting it to the master server. To do this, you'll need a access key. This report will contain detailed information about the encountered problems, but will not contain any private information (other then your IP address, just remember every site you visit keeps track of this though).
How do I get an access key?
This is actually quite simple. You'll simply have to send me a private message asking for an access key. When you've received such a key, you'll have to let the system send a report to the master server. This is actually quite easy. When you launch the game, you simply have to open the console (SHIFT + ~) and enter the following: /sacInternal #, where # is the number you receive. Example: /sacInternal 879871, as shown in the screen shot below.
Once a report has been send, it will say it has been accepted (as shown on the screen shot). When you're done, you'll have to send a new message asking for the report (otherwise it's enormously hard to track all the reports I'm expecting). Just keep in mind that if you're indeed cheating, I will not hesitate to post the results including your IP in a public 'cheater' sticky :).
Why the hell do you do this in such a roundabout way?
It's safer to work like this and we can get in a flaming and heated discussion about security, but let's postpone this until the major bugs are out of SAC all right? Good boy!
Please note, if I am on IRC or you have got me in your MSN/XFire buddy list and I'm signed in, communication about analysis is preferred to be done through this method. Also note you'll need to run DVersion.exe to update to the October 14th update, thank you.