bcbwilla / fouriermc Goto Github PK

PlayerInteractEvent is also called for right clicks and for interacting with pressureplates, which is not accounted for when incrementing the click counter for the player.

http://gyazo.com/75497502fb2987daa3943cfdd04a3b50
http://gyazo.com/bc7ca9775084b3a00f70d0db70fd7b8f

Add data logging option. Probably just log the clicking signals as arrays in a json file so that it can easily be played with later.

[{player: uuid, signal: [0,1,0,0,0,1,1...]}, ...]

Add option to only log certain percentage for if larger servers want to collect a portion of data over time.

Note that I'm going to ease of later analysis over efficient storage here.

Need a good way to record / log user violations (i.e. when they fail a clicking signal test). Possibly something that keeps track of violations over time and notifies server staff after a certain number of violations. This should be general and play well with other standard server plugins.

Add get/set commands for each of the config parameters so that clicking signal tests can be modified in game. This would be primarily for debugging and testing purposes.

Similar to /ncp info <playername> in NoCheatPlus, it would allow you to see a player's recent violations.

Mentioned in issue 2, and started with #3. To fully do this, we need to have separate click loggers for left and right clicks.

Basic permissions are needed for commands and violation notifications

For Java 7 and up, there is the Diamond operator which is convention for initiating collections.

instead of: public Map<UUID, Violation> violationLogger = new HashMap<UUID, Violation>();

set your programming language to 7 (diamonds & multi-catch) and do:
public Map<UUID, Violation> violationLogger = new HashMap<>();

You shouldn't notice a performance difference, just a little thing I caught while reading your code! :)