[Zuthara]

Quote:

Originally Posted by TreePuncher From what I read, I'll assume all reports are sent straight to the master server, no exceptions. With that assumption in mind, I think it'd be nice to have a callback where you decide whether that report is sent to the master server or just dropped. As you said, it's possible to have your admin banned accidentally by using admin commands, and the reason I am giving this idea is because, if that were to happen, the server could just go through whatever logical operation it was programmed to go through and drop the report if the admin was really using his commands, that way, the admin wouldn't have to go off duty for 24/48 hours, and you wouldn't have to review that appeal. Now that suggestion was just in case the plugin doesn't work like that, I did not have time to look at it. Sad, really.

That is already developed on the 1.2 development branch. Hoping to push out an update either tonight or tomorrow morning with some added features for handling ban exceptions (applying exceptions to certain players). There are also a few bugs identified which i'm going to fix in the development branch - only one of them could possibly result in false bans (going at high speed at a speed incline could trigger a fly-hacking flag).

The 1.2 branch will have a number of features gearing the system toward a panel, so that admins can reverse bans issued by their own server. So, if an admin identifies a false ban issued on their server, they can go and reverse this on the panel. I expect the panel to be finished by around 1.3 - 1.4, along with the web API.

Also new in the 1.2 branch on the master-server side will be the beginnings of a web API so that servers can check players for sprunkbuster bans on their own websites and UCP applications. This will likely be released around the 1.3 - 1.4 point.

Also, i'm going to fix the nex-ac lang files to the include shortly. Apologies for the errors, guys.