Suggestions For Logloc

My acquaintances and I have been debating about new possibilities and ideas for the newly implemented recording plugin, LogLoc. We would like anyone to contribute (sensible, possible and effective) ideas for this. I am simply presenting what we have come up with so far.

Hack patterns could be coded into the system. Hacks could be tested to see how they work. This would not auto-ban or auto-kick, but set off alarms for staff to review. And no, this wouldn't be overly sensitive or unsensitive, because a player would only be suspicious if they set off, say, 20 alerts in a short period of time, continuously.

In credit to @JackShadowPyrez, auto-clicker clients could be detected if we can access invisible data, like cps (clicks per second). More detail will be provided by Jack.

This plugin could also monitor the chat as well, and take logs of certain words which trigger the system. The message would then be automatically put on a seperate database (not the console) and staff could review it. Of course, it would also "log around the last 50 and following 10 chat data from that point in case someone made the player say it" (quote from Jack).

There is a lot of possibility and potential here, for this plugin. Of course, we want this to be as unique, yet effective as possible. Thanks.

 

What types of patterns do you think it should detect? It's very difficult to make a hack detector.

 

Yes. Due to packets and ping, hack detectors can be very difficult to be accurate because there's no real way to differentiate between hacks and lagging in many cases. Or, rather, from a code standpoint, hack detectors tend to consistently believe someone who is lagging is hacking. Trust me, lagging players can cause more than 20 alerts in a short period of time....

 

Yup. If anyone can think of patterns that happen with hackers but not laggy players, post here.

 

Another idea:
Perhaps we could implement auto banning people if two or more have the same ip adress and different names. I don't know how it could auto detect people that have changed their name and make exceptions, but it might have to be manually added in.

Note: Hack pattern testing starts this weekend on a private server between few of my friends and myself.

 

UUIDs are used. They stay the same after name changes. Siblings and friends are allowed to join, making the auto banning algorithm impractical