XRay Informer
Thank you for 70,000 downloads! CoreProtect support is here!!!
Do you have a minecraft server and have trouble with users x-raying?
XrayInformer may be your solution to get rid of them.
XrayInformer hooks into your server logging plugin and calculates data to tell you if a player is cheating with an Xray mod.
Permissions and Commands
Screen Captures
Technical Info
Works with:
CoreProtect
- and -
LogBlock
Have an issue or a bug? Use the Issue Tracker:
What will be added in later versions?
Faster more efficient search algorithm.Add support for CoreProtect.- Support for Prism
Have calculations only account for natural mined ores, not placed oresUpdate and fix the cleared player manager
As a learning and aspiring developer, I am still looking for some means of support in future school endeavors. If you would like to donate and help support me, it would be greatly appreciated. My plugins are free, and this is optional. If you can't support me through monetary means, please feel free to comment and check out my other plugins as well. Anything helps, thanks!
Be sure to check out my other Bukkit plugins!
HeadshotEffects
SelectivePvP
This plugin has a lot of potential. I has quickly become a powerful tool for us. If I could make a suggestion a bit of explanation in the config would be helpful. With a bit of tweaking this plugin could be ideal for stopping x-rayers. Thx for your effort and kindness wesley272!
I agree, I can't believe I've never posted an explanation of the configuration or added comments to the actual one on your server. Will do.
Perhaps you were busy making the plugin work. :P
My staff is seeing this but I am not. I have all perms "*". Is there a way to perm out of it or to disable it? I do want to keep the log in msgs which I do see also.
Configuration information is now available via the "pages" page or:
https://dev.bukkit.org/projects/xray-informer/pages/config
With the new config documentation, you'll see that you can disable that in the config :)
Hey everyone, I apologize for the lack of attention I've given this plugin over the last two months, I've been busy and to be honest didn't give any of my minecraft projects much time. With the release of 1.11 I'll be updating XrayInformer and working on some fixes and new features.
@Futschel Are you using CoreProtect or LogBlock? If you're using CoreProtect, you need to change your config to reflect this, as the plugin attempts to use LogBlock by default.
Hello wesley272,
I have a problem with your PlugIn. I am runnung an 1.9.4 spigot server, with LogBlock v 1.10 and XrayInformer v.3.3.5
I don't get data for the Informer. there is the folloeing error:
[22:21:21 WARN]: org.apache.commons.lang.UnhandledException: Plugin XrayInformer v3.3.5 generated an exception while executing task 139673
at org.bukkit.craftbukkit.v1_9_R2.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at de.diddiz.LogBlock.config.Config.getWorldConfig(Config.java:267) at de.diddiz.LogBlock.QueryParams.getTable(QueryParams.java:182) at de.diddiz.LogBlock.QueryParams.getQuery(QueryParams.java:157) at de.diddiz.LogBlock.LogBlock.getCount(LogBlock.java:324) at com.wesley27.xrayinformer.lookups.LogBlockLookup.stoneLookup(LogBlockLookup.java:56) at com.wesley27.xrayinformer.XrayInformer$4.run(XrayInformer.java:526) at org.bukkit.craftbukkit.v1_9_R2.scheduler.CraftTask.run(CraftTask.java:71) at org.bukkit.craftbukkit.v1_9_R2.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
can u tell me what the Problem is ? Thx !
Please add prism support! Great plugin!
How far away are you from making the support for Prism?
Thank you for your hard work on your plugin, have been using it for months.
Have a few suggestions:
1) Notify staff in game when a player goes over the break percentage, such as https://dev.bukkit.org/bukkit-plugins/x-ray-block-percentage-xbp/ did.
2) Have an option in the config to check all worlds, or multiple specified worlds, when performing the /xcheck <playername> command.
@wesley272
Yea, i know. Sorry for my english. I told only that if name world is other than default, in plugin it isn't set, is the same error. Correct name of the world must be entered to plugin. But nevermind, This is not a bug. I think :)
@Jalulek
You're welcome :)
Something is getting lost in translation, I'm not understanding what you mean about the correct world in the config? The config world option is a default option that is meant to be changed by the plugin user.
@wesley272
Yea,
Good Job Wesley!
All problems reselved. But in config must be write correct world. If name is other, also display than error
THX for your work!
@wesley272
Update - I've found a bug in my code that only started being a "bug" lately, but was always an issue in my mechanics. Never thought about it before because I never produced the error you guys got. My apologies for this persistent issue. There's an update coming for you LogBlock users ASAP :)
EDIT: LogBlock fixes in the latest version v3.3.8 :)
@Jalulek
I'm looking into it, at this time I'm unsure what could be causing this error but I'll figure it out and upload a fix if it's a problem in this plugin :)
Wesley I found it your message.
Check your post here from Oct 11, 2015 at 17:08
I don't know if this the some problem, but also is when i joining to server.
All errors i write you below. Error when joining and error when use commands: /xcheck player
@Jalulek
I don't remember, that wouldn't make sense, XrayInformer doesn't need UUIDs to function properly. Is that the only error you're getting?
I'm testing logblock, check commands. Any errors in console. Error is only when i added plugin xrayInformer.
But this problem from error when i joining to server report you a any time ego on version early 1.8. If i good remember you told me that xrayinf. not is aware UUID? Probably... But not have possible fix it?
@Jalulek
@Retrojnr
Both of you are having the same error. You're using MC 1.10 right? Are you sure your LogBlock is working correctly? I've heard reports of LogBlock not working with 1.10. That error is not due to XrayInformer, it's because LogBlock isn't properly initialized and therefore XrayInformer cannot connect to it. There's no guarantees of XrayInformer working with Lockette until Lockette is updated to work with 1.10.