Orebfuscator
Orebfuscator - Anti X-RAY:
For all releases of 1.9/1.9.1/1.9.2/1.9.4/1.10/1.11/1.12.x/1.13.x: Version 4.4.3
Now with support for CraftBukkit 1.9/1.9.1/1.9.2/1.9.4/1.10/1.11/1.12.x/1.13.x!
This plugin is used to counter X-RAY Client mods.
It modifies data that are sent to clients to hide blocks of your choice, such as Ore, chests, dungeons, etc.
It does not manipulate blocks in the world file, thus is safe to use.
ProximityHider is a feature that hides chests that are far from players.
As of 4.3.3, Proximity Hider has been enhanced to use line-of-sight checks, not just proximity! Upgrade today.
Configuration Guide
https://github.com/lishid/Orebfuscator/wiki/How-to-properly-configure-Orebfuscator
https://github.com/lishid/Orebfuscator/wiki/Configuration-File
FAQ
https://github.com/lishid/Orebfuscator/wiki/FAQ
DOWNLOAD
Please read compatibility information before downloading as not all releases work with all versions of CraftBukkit.
Latest version should be on BukkitDev, or as a release on the Github page: https://github.com/lishid/Orebfuscator/releases
Please also download ProtocolLib and install it in the plugins folder.
- Is compatible only with version 4.0.0 or newer.
- For 1.9.4 support, you must use build 277 or newer of Protocollib 4.0
- For 1.10 support, you must use build 293 or newer of Protocollib 4.0
- For 1.11 support, please use latest stable builds of ProtocolLib for 1.11.
- For 1.12 support, please use ProtocolLib 4.3.0 or newer.
- For 1.13 support, please use ProtocolLib 4.4.0 or newer.
- Download link: https://www.spigotmc.org/resources/protocollib.1997/
- Legacy Link: http://dev.bukkit.org/server-mods/protocollib/
Features
- Advanced algorithm that hides ore, chest and and anything you specify in the configuration
- Spout compatible, but optional
- No modifications to CraftBukkit.jar is needed
- Customize the blocks you want to hide
- HIDES DUNGEONS and other blocks that are in the dark
- Different hiding mode, or scrambling.
- Extensive configuration. Change updating methods depending on your bandwidth and processing speed.
- Hide hidden chests and furnaces until a player is close to it.
- Hide hidden chests and furnaces until a player can see it.
Usage
Install:
- Copy "orebfuscator-4.4.3.jar" to your plugins folder
- If you're upgrading from Orebfuscator.jar, move the contents of the "Orebfuscator3" folder to the "Orebfuscator4" folder
- Restart your server.
Configuration
See this: https://github.com/lishid/Orebfuscator/wiki
Commands
See this: https://github.com/lishid/Orebfuscator/wiki
Permissions
See this: https://github.com/lishid/Orebfuscator/wiki
Source Code
Here you go! (Hosted on Github) - please post issues and requests for help there
Metrics
- This plugin utilizes Hidendra's plugin metrics system, which means that anonymous information of your OS and setup will be collected and sent to mcstats.org
- Opting out of this service can be done by editing plugins/Plugin Metrics/config.yml and changing opt-out to true.
Thanks!
- Aleksey_Terzi, single-handedly updating to CraftBukkit 1.9, 1.11, and 1.12!
- DevotedMC for taking over management of the project
- AFFORESS, major help on code optimization and spout support!
- Lishid, for years(!) of maintaining this plugin, and MarioG1 for recent patch support
- raphfrk, helped with packet processing
- Many donators!
Bugs
- See the issues page for any outstanding problems.
TODO
- A command that generates the world cache for the existing chunks.
Changelog
Version 4.4.3
- Support for Minecraft 1.13.2 latest builds (CraftBukkit/Spigot/etc)
Version 4.4.2
- Fixes for reported issues during use -- please update
Version 4.4.1
- Support for Minecraft 1.13 and 1.13x (CraftBukkit/Spigot/etc)
- Some enhancements under the covers, including better support for tile entity hiding and state management
Version 4.3.3
- Includes fixes for portions of #164
- NEW FEATURE: Gaze based proximity hiding. If you can't see it due to blocks in the way, it stays proximity hid, regardless of your physical closeness! For full details, read here: PR#16
- New example configs! Find them here: https://github.com/lishid/Orebfuscator/tree/master/Plugin/src/main/resources/resources
Version 4.3.0
- Support for Minecraft 1.12 (CraftBukkit/Spigot/etc)
Version 4.2.1
- #135 : Resolved issue that plugin doesn't work unless you delete the config and force reload and clear cache after startup
Version 4.2.0
- Support for Minecraft 1.11 (CraftBukkit/Spigot/etc)
- Remove ChunkReloader due to performance issues at scale.
- Addressed #66. Limit Cache retention configuration options added.
- Proximity Hider blocks are by default orebfuscated, if both are active.
- Implemented #62. Per World Configuration -- have unique configurations per world.
- Addressed DevotedMC#8. Allow for unique proximity Y height per material hidden.
- Fixed #113. Item frames sometime disappeared.
- Fixed #124. Glitches when used FastAsyncWorldEdit.
- Fixed #125. Prevent obfuscation for NPC, for ex. NPC from plugin Citizens.
- Fixed #128. EntityChangeBlockEvent was not causing block updates.
Version 4.1.4
- Fixing ChunkLoader error: https://github.com/lishid/Orebfuscator/issues/110
- Improving performance of ChunkReloader
Version 4.1.2
- It is now possible to use Worlds list either as blacklist (i.e. all worlds are subject for obfuscation excluding listed) or as whitelist (i.e. only listed worlds are subject for obfuscation)
- Fixed bug with using ProximityHider and Signs. It is now possible to add WALL_SIGN and SIGN_POST to ProximityHider obfuscation.
- Updated wiki so commands and configuration pages are matching to the current Orebfuscator.
Version 4.1.1
- Various Small fixes
- Fix which might resolves problem described in https://github.com/lishid/Orebfuscator/issues/100
- Config file now supports block names additionally to IDs
Version 4.1.0
- Support for CB 1.10 - thanks Asgarioth!
Version 4.0.14
- Single jar supports all releases of 1.9.x now!
- Some chunk reload issues are corrected (on teleport, etc.)
Version 4.0.12.1
- Add support for 1.9.4 - this release does not support prior versions.
Version 4.0.12
- Fixed entity list reload issue
Version 4.0.11
- Fixed failure to deobfuscate along chunk boundaries under specific conditions.
Version 4.0.10
- Fixed crash for PaperSpigot servers
Version 4.0.9
- Fixed crash when chunk section (16 x 16 x 16) has more than 127 different block types
- Implemented different "transparent block" lists for Engine Mode 1 and Engine Mode 2. For now only difference is with lava block, for mode 1 it is non-transparent, for mode 2 it is transparent.
- Implemented possibility to specify which blocks are transparent and not in the config file, sections: TransparentBlocks and NonTransparentBlocks.
- Fix which may have solved java.util.ConcurrentModificationException
- Fix for phantom blocks (visible after chunk reloaded) when player is digging straight line on the chunk border.
Version 4.0.7-beta
- Corrected transparent block list. For example, lava blocks marked as transparent and therefore adjacent blocks are not obfuscating anymore
- Improved performance of ProximityHider function
Version 4.0.5-alpha
- Fixes teleport / join in the End causing client-side crashes.
- Fixes failure to deobfuscate immediately on join.
Version 4.0.3-alpha
- Updated to MC1.9.
Full release notes: In Github Release
Version 3.0.5
- Updated to MC1.8.3.
Full history: https:github.com/lishd/Orebfuscator/wiki/Version-History
A quick donation is always appreciated :D
Devoted Patreon or General Inquiry
@7007King0770
This plugin doesnt use much more memory (probably just a dozen of megabytes more than usual). if you can't handle this small amount of increase... you have a problem... Try launching with more RAM.
Btw, it's possible that you have a plugin that in combination with this one makes much more memory usage. I get no problems with 1GB for 40 players.
Read the FAQ in the forum post in forum.bukkit.org under section java.lang.OutOfMemoryError @7007King0770
This plugin doesnt use much more memory (probably just a dozen of megabytes more than usual). if you can't handle this small amount of increase... you have a problem... Try launching with more RAM.
Btw, it's possible that you have a plugin that in combination with this one makes much more memory usage. I get no problems with 1GB for 40 players.
Read the FAQ in the forum post under section java.lang.OutOfMemoryError
http://forums.bukkit.org/threads/sec-orebfuscator-1-2-6-anti-x-ray-1-0-1-r1-1597.38385
Is there any significant ways to reduce memory usage? My server has been crashing due to lack of memory caused by the extensive amount of memory used by this plugin.
@supayoshi
You can disable darkness obfuscate if you don't need it (hides stuff in the dark).
@FatFreeSMP
Not sure where your lag messages come from if your CPU is not fully used, maybe something in the java configuration is restricting the use of your cpu. If you're using spout and have problems, it's likely that spout is causing it. Cache just makes a bunch of files, but should speed up and use less CPU.
Well I tried using Engine mode 3 with an initial radius of 1 like you suggested, it seemed to work fine for a while, but again started getting more and more 'waves' of 'can't keep up' messages, All the while my CPU is reporting only 30% usage.
One thing i wasnt too sure about is the 'processing threads' option, I have a quad core processor so should I have it set to four? When I set it to higher than 1 in console, then check it using 'ofc status' it reports maximum threads is 1 no matter what I set it to, what does this mean? Thanks!
P.S. Also, I saw another user suggest running without caching to improve performance, are there any bugs with caching? or should it improve performance?
@lishid
Do you mean, DarknessHideBlocks: true
I will set this to false then?
@spydercanopus
I recommend the dev version over the the normal release version, but if you don't need spout for other things, don't use it! Spout is buggy and have some optimizations that kinda disrupts other plugins, and I use plenty of hacks to overcome such incompatibilities. If you absolutely needs spout, use the latest dev version.
@lishid
Is the spout devbuild version required or just recommended over the spout release version?
@miketoast
Read the red WARNING part in the main post up there.
@darkcloud784
I just thought people are not that lazy. Maybe I'm wrong. Here's a link to Spout's page: http://dev.bukkit.org/server-mods/spout/ Use the second link in Server Admin part, it says "Download the latest server plugin development build*"
@Zombiemold
Use Engine mode 3, should save some resources. Enable cache if you haven't done so.
@supayoshi
This is not supposed to happen. Anything on the surface is not replaced with fake ore. Try disable darkness obfuscation if you added the ores to it.
@FatFreeSMP
Try using engine mode 3 with initialRadius of 1.
Still having 'can't keep up' messages, I have tried multiple different configurations including the default and this still happens.
Two things to note: 1. It doesn't start immediately, just over time as 10-20 players are active, leading to crippling lag over time. (my server has handled 60+ players in the past with No Orebfusicator) 2. The 'can't keep up' messages seem to come in waves, like a couple minutes of no messages, then a minute or so of them spamming.
Server Specs: i5 3.2ghz quad core, 8 gigs ddr3 ram, 64GB SSD for storage. Plugins: Essentials, Logblock, Worldguard, WorldEdit, CombatTag, Spout and Nocheat.
Again, I thank you for this great plugin and hope eventually it will work for me! Keep up the great work.
Hi we experience nolag, it is a wonderful antixray plugin, though our system has an i5, and 16 gb of ram, and a shitload of other plugins. (No anti lag plugins however)
Anyway, what my error is, is that sometimes user see block lag ;) Thats how they named it its just cute. It means that sometimes when users walk over a few stones, they are ores, and when they walk or stand longer, place a torch / block they dissapear, also when they dig them ofcourse.. However maybe It's an idea to remove this by adding an light, or player distance thingy, that will automaticly remove the antixray plugin in the [?] blocks the player is standing. Like 10 blocks, this way xray won't work still only on really short distance. But that way people will never see fake ores, and get dissapointed!
is this an idea?
I am having the exact same issue squidicuz, and many others are reporting. Why does this lag so terribly? 20+ is unplayable with it, EngineMode 2.
@lishid
lol use dev version with no link to any dev version on the plugin info or the post.
I enabled this plugin and tried to xray on engine mode 2, I can still see through all the blocks
@squidicuz
Are you using spout? Try updating that to the latest dev version.
@Pr4w
I am having similar issues. The CPU on the server is a Hexacore i7 and the tick rate is horrible with this installed. Major chat lag and rubber-banding occurs with only 20 players online. Becomes unplayable with more players than that.. It is set to use engine mode two and utilize multiple threads. I am going to try engine mode three to see if there is an improvement.. How do you run this on a decent server without it lagging? (would a ticket be more helpful?)
EDIT: NoLagg seems to have improved performance significantly, server side that is...
@Viper150
This has been addressed multiple times. It's not possible. The calculations it takes to know which cave to hide and which to show to the player is enormous, and not a practical solution.
@Pr4w
I'll PM you.
This plugin works great, but caves still show up. Is there a way to completely hide those as well? Thanks.
@lishid
Do you have Skype ? That way we can coordinate it, I can't leave the plugin on for prolonged times, causes too much lag for the users... And it isn't really noticeable on any test bench with 1-2 players, so I'd have to install it on the live and run tests for a short while
@bazookapooka
Engine mode 3 uses a different random generation algorithm (loops through the blocks instead of using a random number) It uses slightly less CPU than engine mode 2, with somewhat the same results.
@Pr4w
I don't get it either, it could be a spout problem... Try updating spout to latest dev version. If that doesnt work, I'll join the server sometimes to check it out.
@re4397
Button added at the end on the forum post and bukkit-dev page.
@SuperRaWR
Thanks, I'll have a look.
@violation84
The updates occur whenever a player tries to mine an area (ex: hit a block, break a block) The frequency of updating is sort of fixed. Update radius only changes that when you hit a block, a larger radius behind that block is revealed, so that the users won't be mining fake blocks.
If your server's CPU can support it, you can up the initial Radius. Beware though that this can cause significant lag when players login and/or explore new areas of the map (depends on your server capacity).