Migrated from: https://dev.bukkit.org/projects/anti-x-ray/issues/1

Originally posted by _ForgeUser10000185 (Jun 5, 2013):

Hey,First of all, great plugin. It works very good the way I have it configured now, almost all the limits that are reached means xraying. Although it works good I still have some ideas to improve it even further.It would be very useful to see some sort of high score list of people who have reached the most mining limits in combination with the time they have played on the server. So if player1 played for 2 days and has reached the limit 10 times. And player2 has played for 1 week and also has 10 mining limits there would be a higher risk of player1 xraing.Also a some sort of player lookup would be useful, in which you could see how many times a player mined ores. This could also be linked to a high/mid/low risk status in combination with idea 1.I hope my ideas will help you, keep up the good work.Best regards,Jason

Originally commented by blablubbabc (Aug 3, 2013):

The counter was added in the last version (1.7.3)

Originally closed by blablubbabc (Aug 3, 2013)

Originally commented by blablubbabc (Jun 5, 2013):

Quote:It would be very useful to see some sort of high score list of people who have reached the most mining limits in combination with the time they have played on the server. So if player1 played for 2 days and has reached the limit 10 times. And player2 has played for 1 week and also has 10 mining limits there would be a higher risk of player1 xraing.

Hm, I do not not like the idea with counting how many times a player has reached his limit. I will keep thinking about this.
However, I will not add something that would require to load all playerData. So something like a top list could only be added like this: having a seperate file for the top-list. On each quit -> check if the player has reached his limit more often than one of the guys from the toplist -> update toplist. However, when the toplist is somehow lost, some mistakes happen, all players limit-counter shall get reset: I would have to load the files of ALL players.. So I am hesitating a bit from this.
However, an top list for the player currently being online , or single lookup shouldn't be a problem though, if I decide to add this.
But I do not think that I will add tracking of players online time. I do not actually see why this would even be necessary if the ore values are setup fine: reaching the limit == reaching the limit. No matter how long the player was already playing on the server.

Same probably could apply for the logging of the count of these from above.. If a player reaches his limit, no matter of how long he already had played or how many times he has already reached the limit before -> check him to see if his is hacking, right in this moment.
Quote:Also a some sort of player lookup would be useful, in which you could see how many times a player mined ores. This could also be linked to a high/mid/low risk status in combination with idea 1.

This would require block logging which would make the plugin a lot heavier than it currently is..

But you are right with saying that these can be helpfull, especially to have another source for verifying if a player is actually hacking.

Also, there are already ore-ratio-logging plugins out there whcih are doing exactly this.

So instead of me adding something like this directly into AntiXRay, which mainly aims to stop xrayers from breaking the blocks on the first hand (and stay lighweight), I suggest you to instead use one of these Block-Logging-Ratio-Plugins in addition to AntiXRay if you want to.

Originally commented by blablubbabc (Jul 26, 2013):

Highscores and block loggin related stuff is out of my consideration.
However, I was long thinking about the remembering, how often a player has reached his limit. I came to the conclusion, that this shouldn't be necessarry (like already pointed out below): it shouldn't matter how often a player has already reached his limit. What matters is, THAT he has reached his limit.
However, I will probably add it anyway in the next version.
Edit: one problem I am currently facing is, to decide, when I add 1 to the counter of "how often the player has reached his limit". Because when the player has reached his limit, and keeps trying to break blocks, he will constantly keep reaching his limit. So I think I will limit the reach counting to 1 time per session, just like the inform messages work.