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.
@FurmigaHumana
You know that by doing that, you're sending an unobfuscated copy of the chunk first, then another obfuscated one, so hackers can just discard the new one right?
great news, I finaly fixed the problem with newly generated chunks, it required a bit of 'dirty code' but aparently it is working fine.
The fix was very simple, I just had to skip newly generated chunks and send it to the player in the next tick.
I'll upload v1.5 late today.
Error on the latest version you posted: http://pastie.org/5566683
@Adrenalineq
on github
@FurmigaHumana
Source included?
Just updated to 1.4.6, but newly generated chunks still not being obfuscated, I'm giving up. I have absolutely no Idea of why this happens.
Bukkit 1.4.5 - Recommended build OUT !-
So, we'll have no solution for the newly chunks not getting obfuscated bug :\
uhuhhu bukkit crash alot of plugins at newest bukkit D: @@
@FurmigaHumana
Pastebin:
http://pastebin.com/tjAyPw1Y
@Adrenalineq
You need to change your engine mode if you don't want that to happen.
@FurmigaHumana
And make it please compatibility with ProtocolLib
@FurmigaHumana
This is normal if FAntiXRay change dirt, stone and other common blocks to diamonds ore ..etd ? o_O
Meu servidor esta com um pouco de lag quando estou com o plugin ativado. Ele fica 20 tps, mas mesmo assim da umas travadas. Estou sem o cache ativado porque quando ativo, tenho aquele erro do Too many files open, e o servidor cai. Tenho um servidor de 100 slots, sempre cheio.
@archlinux
Yep, hope it's fixed soon.
nevermind, all fine now with 1.3 (except for the new chunks bug)
@sception
funny... this plugin makes my server unusable (5tps) orebfuscator: 20tps (but other problems)
...default settings.
FH:
An easy way to test it:
1) Open a test server running only FAntiXRay and a clean 'world'
2) You will see that the chunks loaded on spawn are obfuscated like a charm.
3) Start walking on the map till newly chunks get generated.
Bingo. All new generated chunks won't get obfuscated.
Hope it helps.
@archlinux
really? I thought that was patched, I'll see what I can do.
FH:
Version 1.3 still has the newly generated chunks not getting obfuscated bug :\
Hope you can fix it ASAP.