FAntiXRay
FAntiXRay
ATTENTION: This plugin has to be completely rewritten to work on newer versions of craftbukkit. I dont have time to do this right now, dont expect an update any time soon. I'll update, but not right now.
FAntiXRay is a powerfull and lightweight tool designed to provide protection against x-ray mod. This plugin will rewrite the chunk before it is send to the client providing full protection against almost all x-rays mods out there. This doesn't modifies the world in any kind of way.
Pages: Tips and Configuration | Engine Modes | Benchmarks | Source | Jenkins
Features
- Highly Configurable
- 5 different engine modes
- Hide Chests from chestfinders
- Generate fake caves
- Hide blocks based on light level
- Nether obfuscation
- Efficient cache system
- Threaded block update
- more...
Permissions
- FAntiXRay.Deobfuscate - Disable the obfuscation to a player/group
- FAntiXRay.Quiet.Deobfuscate - Disable the obfuscation to a player/group
- FAntiXRay.Updates - Receives in-game update notifications
- FAntiXRay.ClearCache - Permission to clear the cache
- FAntiXRay.SeeCache - Permission to see the cache status
- FAntiXRay.Reload - Permission to reload the configuration
Commands
- /axr reload - Reload the configuration
- /axr cache - Show cache information
- /axr cache clear - Clear the cache
Attention
This plugin hooks directly into CraftBukkit, as result, it may not work with plugins that do the same (e.g NoLagg, ProtocolLib, Spout, I'll try to make it compatible with most of them), also it will break between minecraft patches, which means a 1.4.7 release will not work with 1.5 or 1.4.6.
Know Bugs
- Let me know if you find any!
NEVER post full error in the comments, use paste, pastebin or pastie. Found a way to bypass the plugin? Send me a private message!
A few config options you set will be collected with metrics by Tyler Blair! To disable it, set opt-out to true at PluginMetrics/config.yml, currently tracked settings:
- Engine Mode Number, Update Radius, Fake Caves Settings, Fake Caves Intensity, Cache Settings, Cache Compression Level, Darkness Obfuscation Settings, Explosion/Piston Update Settings, Proximity Settings and Proximity Radius.
No reload command :( - latest spigot, 1.5 - Engine mode: 0 probably don't work checked at nodus
V1.5 is here, I'm still testing it for side effects, use it for test only.
@Adrenalineq
I'm aware of this, is fixed already with 1.5.
@FurmigaHumana
Probably because of your plugin my players has been kicked with reason "disconnect.spam" o_O wtf with it
@Adrenalineq
Here I don't see any errors, would not compile if it had.
@Adrenalineq
I'll do.
@benneht
Yes, you must disable the chunks thing with nolagg to work
@archlinux
The latest uploaded file was just for the record, v1.5 still under testing.
Alpha version still has the new chunks not getting obfuscated issue :\
Incompatible with NoLagg?
Can you add option to reload config ;D
@FurmigaHumana
Because you have alot of errors at source which you don't fix o_O netbeans don't show you this errors?? (FNetServerHandler, FNetServerProxy) :#
@Adrenalineq
Who? I use netbeans, why?
@FurmigaHumana
Say me something.. do you use Eclipse?
@Ta6akus5
http://dev.bukkit.org/server-mods/antixray/pages/engine-modes/
@lishid
that is so weird, indeed, packet51 is used to send new chunks, but packet56 also do the same job, looks like new chunks are sent twice by two different packets, I'll skip the chunks with data from packet51 and see how it goes on my server, but I'm pretty sure that is something wrong here.
@FurmigaHumana
I'm pretty sure Packet51 is sent on new chunks. At least when I obfuscated those, new chunks don't get un-obfuscated.
@lishid
now I nor even know what I'm doing.
@FurmigaHumana
Then you wouldn't have any trouble with new chunks being un-obfuscated in the first place?
@lishid
I'm not even sent then, just saw it now.
@FurmigaHumana
Packet51 is used for large area updates such as redstone, pistons, etc. It's also used for chunk unloading.
@FurmigaHumana
There is a Packet51MapChunk sent too.
@lishid
nop, the chunk isn't sent. I put the packet in a queue and wait until the next tick to obfuscate and send it to the player, he don't receive the original one in any moment.