[Zuthara]

Quote:

I took a quick look at source code and it seems that only bans issued by NexAC are sent to master server.

At the present moment, I don't have the ability to write an entire anticheat system from scratch.

Quote:

call a callback when a global banned player connects instead of auto kicking it

The whole idea behind Sprunkbuster is to create a blacklist of who the cheaters are in the SA-MP community. I have a plan to implement local whitelisting, but it may take a little while before it's ready because i'm trying to move all of that sort of stuff to a control panel.

Quote:

I see you allow servers to issue global bans since they are registered on your master server. What if some malicious SA-MP servers send fake global bans? You should reject all bans unless issuer is trustable.

I was hoping to keep this ambiguous, but I guess i'll elaborate a little bit on how this works.

Basically, all bans are sent into a review queue before they are permanently enforced. All bans can be traced back to individual servers by an API key unique to the server. Servers which send false bans (by triggering one of many tracking systems) get their API Key automagically suspended by the system. As of the present moment, any ban that is issued and added to the review queue is a 12 month ban (which will change once the review system is activated).

Future updates will issue a 48 hour ban to any player suspected of cheating and submit the global ban request to a review queue. The requests in the queue will be reviewed by a human, and either approved (made permanent) or rejected (reversed). The next big task is to make the proper panel.

Quote:

I took a quick look at source code and it seems that only bans issued by NexAC are sent to master server.

Once multiple cheating attempts are logged, the player is globally banned. The idea is to automate the system while also preventing as many false bans as possible. At the current moment, I can guarantee that most bans issued by the system are correct based on information gathered during testing. As of now, admin fly commands result in a ban, and driving too fast uphill can result in a ban - these will be fixed tonight.


---

So, based on above suggestions, i've compiled the following list of things i'm going to be doing tonight for the 1.2 development branch:
TO DO List:
- Add nex-ac language files into the downloadable package.
- Add a callback for handling bans
- Add local whitelisting
- Add a hook for OnCheatDetected
- Security updates to prevent flooding.
- Fix two bugs resulting in false bans.
- Start on Sprunkbuster cloud panel.