Inactive [SEC] AntiXRay v0.6.10 - protecting ore from XRay mod and transparent texturepacks [1000]

Discussion in 'Inactive/Unsupported Plugins' started by asdaarg, Apr 11, 2011.

  1. Offline



    Reporting Errors the follow things have to be mentioned:
    • CB Version and AXR version
    • Whether you started the AXR version with a fresh ore file or not (doing /axr off before upgrade)
    • If not, since what version you've been using the same ore file.
    • If you get any errors in console, check the debug.log for "Error"s and "Warning"s. and post those.

    Upcoming features for 0.7:
    - AXR Chest chest hiding feature developed by MrSelfDestrukt
    - New advanced visibility test (almost done, only need to test it now and decide whether its going to replace or be an alternative to the original light based test) Details here and here


    AntiXRay hides ores from players by turning them into stone until they have been exposed, thus making it impossible for any client side hacks to detect them, as their location is not sent to the client.

    Backup your world(s) I cannot guarantee that ore doesn't disappear from them due to this plugin. Even if you did not backup, there is a foolproof solution here. If you decide to uninstall, type /axr off, and not delete the ore data file before your ore is restored unless your intention is to strip your worlds from ore.

    If you upgrade from 0.5.21 it is recommended that you do /axr off first flush out errors from the ore file. If you do not have enough RAM, you can do this in steps using 0.6.9 but you need to set lenient=true in the config file to allow the file to be loaded
    NSCommand <-- Required
    Source and old versions

    - Specify what ores to hide(works with non ore blocks too as long as they don't use data values or extra data such as chests and signs (use some chest locking plugin for keeping your chests from xrayers)
    - Multi world support
    - Permissions support
    - Stores ore data in binary files (one per world) and only keeps data about loaded chunks in physical memory. It is on average 400 bytes per chunk in and guesstimatedly around 450 in physical memory, so it is reasonably small, but some people might play on huge worlds and want to conserve memory.
    - Saves data about chunks immediately on any changes (they are assumed to be by far sufficciently rare that any performance is won by buffering is neglible. As such it also prevents potential ore duplication on server crashes)
    - chunk and world statistics
    - ingame map of loaded chunks
    - background processes that does not freeze the server
    - dump ore statistics into file and compare them to see the changes in ore content.
    - lots of configuration options

    Ores will become visible under any of these circumstances:
    - A surrounding block is lit by torch and player is within the chunk or adjacent chunk and within 16 blocks to player on Y axis.
    - A surrounding block is lit by a third block broken falling or removed by explosion and player is within the chunk or adjacent chunk and within 16 blocks to player on Y axis (occurs once every 2 seconds, but configurable).
    - A surrounding block is broken or falls or removed by explosion
    - A surrounding block is changed by another plugin (can be cpu intensive if you worldedit a big area for instance - might do a workaround for this)

    Current Limitations:
    - Ores at light level above pitch black on chunk generation will not be hidden e.g. near lava or surface cave entrances.
    - Ores will not be found exploring caves in pitch black (who does that anyway?) These two limitations was to allow a light based visibility test that relies on a test already built into the server, thus avoiding extra performance overhead as well as headache of coding it myself. Despite these limitations, AntiXRay should make it far beyond pointless to search for ores using XRay or transparent textures.
    - Gravel and sand dropping on chunk generation may expose ore. This is assumed to be rare enough to have neglible effect.
    - The data file will not repack itself. The ratio between generated ore and mined ore is assumed to be very high, and the file size is considerably small but nonetheless, should you want to "repack" it, just turn axr off and on and the new file will be smaller excluding the gaps between chunk entries. But again, do some basic math and count the amount of ore blocks mined in total, multiply that by 2 bytes. After a month of mining 10000 ore blocks, you shaved 20k off that 3M file.
    - If you place a torch there is a tiny delay as seen in the video due to client side prediction and lag between the time the info of the ore to get back to the client from the server. This can seem unnatural so I might make a better vision test later that doesn't rely on light. However it would be more expensive in terms of cpu cycles.
    - If you have a slow server or a lot of players, you might want to remove coal from the config list. It speeds it up at least 200%. There are some optimizations I can do that I might add later that will speed up things further.


    /axr on - hides all unlit ore
    /axr off - reveals all hidden ore (and deletes the data file!)
    /axr on <world> - hides all unlit ore in specified world
    /axr off <world> - restores ore in specified world
    /axr worlds - world statistics
    /axr chunk - chunk statistics at chunk player is on
    /axr chunk <x> <z> - chunk statistics at specified chunk
    /axr map -shows map of loaded chunks in current world
    /axr map <world> -shows map of loaded chunks in specific world
    /axr map <zoom>
    /axr map <world> <zoom>
    /axr map <x> <z>
    /axr map <world> <x> <z>
    /axr map <zoom> <x> <z>
    /axr map <world> <zoom> <x> <z>
    /axr show
    /axr show <world>
    /axr hide
    /axr hide <world>
    /axr dump <world> <file>
    /axr diff <filein1> <filein2> <fileout>
    /axr gen <world> <x1> <z1> <x2> <z2> command for generating a rectangular area of chunks
    /axr gen copy <world1> <world2> command for generating all the chunks in world2 that are registered in world1
    /axr pack <world> - removes dead space in ore file (not that there is much from just mining but the axr chest will create significant amount of dead space.
    Auto-backup, that will backup your ore file on startup
    /axr backup <world> - backs up the ore file of the world if and only if the file passes the corruption test
    /axr test <world> - test the ore file and memory for errors for a specific world
    /axr test - test the ore file and memory for errors for all worlds
    /axr mirrorworld <world1> <world2> - creates a world world2 with the same seed as world1.
    These functions are not recommended for use unless you know what you're doing: (they can be destructive of tile entites)
    /axr chunk regen - regenerate chunk (to as it was when world was initially generated)
    /axr chunk regen <x> <z> - same but for specified chunk
    /axr chunk regen <x1> <z1> <x2> <z2> - same but for axis aligned rectangular area
    /axr chunk regen ore - only regenerate ores in chunk at player position
    /axr chunk regen ore <x> <z> - same but for specified chunk
    /axr chunk regen ore <x1> <z1> <x2> <z2> - same but for axis aligned rectangular area

    Note about regeneration: ores, trees, flowers and mushrooms are random each time and not tied to world seed (bukkit/mc issue)



    timerms - the time between light check by broken third block in milliseconds.
    maxdep - buffer size for number of ores that can occur in a chunk - don't change unless you have another plugin that adds tons of ore.
    maxheight - is the number of Y-levels in your map.
    ChunkFileBuffer - sets how much is buffered for new chunks to be stored until the index is rewritten (at the end of the file.)
    Materials - what ores you want to hide. (has to have same number of elements as maxys)
    maxys - the first Y level from bottom they cannot occur at. (has to have same number of elements as Materials)
    worlds - what worlds are loaded at startup (comma separated)
    autostart=all (normal) worlds are loaded at startup (unless CFGworlds is set)
    nounload = keeps all ore data in physical memory
    debug - turning on writes to a debug file keeping track of important info that may be needed to solve bugs or figure out why lag occurs
    fileindexdebug - turning on debug file needed as a quick check of the consistency of your ore file
    mapcol - the chatcode colour of each type of block in ascending order, shown in /axr map
    mapwidth - the width of the map shown in /axr map
    mapheight - the height of the map shown in /axr map
    schedulerload - 0-100 percentage of time going to execute any background process.
    schedulerstatustimer - time in millisecs between each status report of a background process
    filterorenotinstone - filters ore upon exposition that is not in stone (can be used to restore ore from a backupped ore file or ore file generated from a fresh world with same seed)
    autorepack - pack ore files automatically at startup - on by default
    autobackup - backup ore files automatically at startup(requires autorepack) - on by default
    maxfaces - specify max amount of exposed faces per chunk before error occurs
    lenient - ignore lindex errors when loading file (useful if you have them from before and want to filter them out)
    All CMD_... options are for redefining the commands so you can type something else.

    • Fixed Array index out of bounds in listindex accessing materials that has not been loaded yet.
    • Added /axr mirrorworld <world> <mirrorworld> command
    • Fixed NPE when trying to expose ores in world hole.
    • checking whether wrong file exist during repack.
    • fixed NPEs in some commands that can occur if you use it and the world is off.
    • fixed open file pointers during repack.
    • fixed NPE during repack when load fails.
    • fixed NPE when running test on all worlds and not all worlds are on
    • added various memory checks and chunk data entry overwrite checks
    • fixed NPE when trying to flush the debug file when debug file is turned off.
    • added lenient config option to ignore lindex errors when loading file (useful if you have them from before and want to filter them out)
    • added more information on error when loading from file
    • added config option maxfaces to specify max amount of exposed faces per chunk before error occurs
    • /axr off now gradually unregisters chunks - as a workaround to what appears to be a problem with chunks not getting fully removed from memory despite trying both unloadchunk calls through bukkit. This allows one to shut down the server and continue restoration after a restart if one does not have enough RAM
    • /axr pack <world> - removes dead space in ore file (not that there is much from just mining but the axr chest will create significant amount of dead space.
    • /axr backup <world> - backs up the ore file of the world if and only if the file passes the corruption test, also packs the new file.
    • /axr test <world> - test the ore file and memory for errors for a specific world
    • /axr test - test the ore file and memory for errors for all worlds
    • autorepack config option - pack ore files automatically at startup (if and only if the file passes the corruption test) - on by default
    • autobackup config option - backup ore files automatically at startup(if and only if the file passes the corruption test, and also requires autorepack) - on by default
    • new .ore extension for ore files (rename your old files)
    • removed glowing redstone ore from default ore list (never occurs naturally anyway)
    • fixed faulty scanning issue
    • fixed hopefully last exposed ore face index error
    • fixed false positive in memory check
    • debug.log flushed when error occurs (it is otherwise flushed once in a period of time)
    • more details in debug log when error occurs
    • removed lindex spam in debug log until lindex error occurs
    • Fixed /axr gen not triggering scan anymore
    • Fixed /axr gen not unloading chunks
    • Fixed (workaround) huge memory leak during /axr off /axr show /axr hide and /axr gen caused by bukkit's unloadchunk function
    • Additional file corruption checks that will make noise as soon as something goes wrong
    • Fixed another potential index derangement bug.
    • Fixed array out of bounds exception during previous fix
    • Fixed a couple of bugs offsetting exposed ore face indicies when mining adjacent block potentially causing array out of bounds exceptions at a later stage and the revealing of wrong ores when exposed to light.
    • Added debug logging of exposed ore face indices when found, as well as fault intolerant check that will warn you about any corruption of the indices after the event.
    • fixed half of ore not being hidden when a chunk is generated on load.
    • removed various unnecessary details to be logged in debug.log
    • fixed bug restoring ore, hiding and showing in wrong world
    • revert hack to set block material of a chunk to physical updates due to lacking javadocs to figure out what function to call
    • Switched to non physics updating block material setting hack
    • Updated to #733
    • Added detailed debug logging of background processes.
    • removed logging of filepointer
    • fixed failed scan after /axr gen unloading chunks that were originally not loaded, consequently also /axr gen causing server to freeze and timeouts on clients.
    • fixed /axr gen not unloading chunks that were originally not loaded
    • /axr gen and /axr gen copy now actually usable
    • ore in stone filter now also applies to /axr off and /axr show (not just when it is found by light detection)
    • added /axr gen command for generating a rectangular area of chunks
    • added /axr gen copy command for generating all chunks that are registered in another world
    • Configuration option CFGfilterorenotinstone implemented, that allows filtering of ores not in stone (can be useful in recovering lost ore from a world with the same seed)
    • fixed ore regen not working when axr is off in that world
    • removed physics lock spam
    • fixed more concurrency errors during background processes (hopefully for the last time)
    • fixed more concurrency errors during background processes
    • fixed concurrency errors during background processes
    • fixed debug off in config file causing unable to start (again! although different place now)
    • ore stats dump - listing all chunks ore counts into a text file
    • ore stats diff - showing difference between two ore stats dump files (these two tools are useful if you are worried that your ores might disappear)
    • show command - reveals the ore but does not unregister them or delete the file
    • hide command - hides again ore that was revealed with show.
    • show, hide and ore stat dump are background processes that does not freeze the server.
    • axr off is now a background process
    • load percentage of background processes can be configured
    • specify map zoom and center
    • Fixed file index debug listing not showing
    • file index debug listing can be turned off in config.txt (fileindexdebug)
    • area regeneration functions now tolerate any two coorner in rectangle in any order.
    • fixed debug off in config file causing unable to start
    • added axr map command for showing map of loaded chunks
    • fixed light expose unmapped material (probably why you got grass/smooth stones)
    • fixed light expose restored block being block at exposed face
    • fixed light expose no chunk location offset (why you got it at spawn)
    • fixed exposed face location wrong axis (probably floating blocks)
    • removed unnecessary cacheing of chunks at startup by not using chunks as keys for file index(probably solve memory problems for large worlds)
    • bypassing unnecessary cacheing of blocks using minecraft hackery.
    • revised scan algorithm, bypassing bukkit wrapcode resulting in at 5-10 times faster scanning.
    • fixed queries on unloaded sidechunks during scan resulting in loading and even generation of chunks that on top of it due to eventlock get ignored by onChunkLoad, thus leaving chunks of unhidden ore.
    • fixed light expose filling 0s after removed index
    • probably more bug fixes, can't remember them all
    • world statistics: type axr world - shows also what worlds are on/off
    • chunk statistics when axr is off no longer causes world to be registered without any chunks being loaded
    • axr on doesn't show NaN when there is nothing to hide
    • proper colouring
    • empty chunks are no longer ignored.
    • Fixed potential ore type shift bug
    • Moved listindex before file is loaded so debug info can be displayed even if it crashes while loading.
    • added rectangular area regen functions
    • Fixed silly nullpointer exceptions
    • Specify what worlds to turn on and off
    • Specify what worlds to load at startup
    • option to keep all ore data in memory
    • chunk statistics (useful for checking that your ore doesn't disappear or duplicate)
    • chunk regenertaion (restore a chunk to state at world generation)
    • chunk ore regenertaion (restore only ore)
    • Fixed some other bugs related to exposed-face-to-ore index
    • Index debug file working again (it was still expecting 0.1.5 files)
    • Added potential ore file corruption warnings to debug file output
    • Fixed bug locating exposed-face-to-ore index elements having no array bounds check.
    • Fixed bug exposed-face-to-ore index elements not being removed
    • Fixed bug exposed-face-to-ore index not being updated when ores are recovered and removed from hidden ore list (new bug in 0.2)
    • Fixed bug at y levels above 128-16 looking for ores above the map
    • Uses NSCommand now (it did right from the start but its now a separate plugin)
    • auto-creation of config files
    • defaults to ops only when permissions is not present
    • Light detection optimization based on a separate list of faces exposed to nonsolid materials (this might not work with all materials yet such as stairs and singlesteps, but its not like the world generator puts them in the caves anyway) resulting in at least 10 times faster execution of light checks. This should reduce all lag that's not due to scanning new chunks for ore.
    • Once again more detailed debug log
    • Fixed bug in ore restoring function causing large veins of ore to be generated out of nothing
    • More detailed debug log
    • Removed file corruption check that's hogging up some cpu cycles during file load and write events (the latter occured during scan event) - so this should speed up scan events.
    • pseudo error "load error 1" moved to debug log.
    • Added 1 tick delay of scan in onload event since it appears bukkit fires it before the chunk is populated with ore. This fixed the bug of ore appearing if you teleport or walk far away from initially scanned chunks.
    • removed physics event logging since it appears to always be neglible.
    • Added message at startup informing you about the waiting time of scanning all loaded chunks may take a while.
    • Fixed bug starting server without plugin data folder causing it unable to write debug file
    • Added more debug file details (when its scanning, loading from file, or just loading from memory when neither is shown)
    • Those who who don't hide coal, should experience faster chunk scanning now
    • Fixed bug due to player location being null for some weird reason
    • Added debug logging of time spent on the main time consuming procedures.
    • Fixed config file not loading properly
    • Removed wtfexception spam
    • Initial Release
    Donate (Not necessary but appreciated)
  2. Offline


    What exactly did it do?
  3. Offline


    Something is wrong with the code that restores ores etc. When I installed the plugin I mined straight down into a deposit of Coal, all well and good. But the coal deposit was seemingly endless, and continued on and on and on and on, the plugin was replacing stone with coal as I was mining it and in the end I ended up with 130 coal from a single depoist. Obviously there is no way that the deposit was that big in the firstplace and the plugin has replaced stone with coal when it shouldnt have

    I experianced no lag or plugin incompatabilities and I run 38 plugins including essentials, iconomy, worldedit, worldguard, craftbook and towny just to name a few. So people complaining about that need to look at thier setup.

    Thankfully I backed up my world beforehand. Hope you find a fix, I am really interested in this plugin

    Debug logged attached. Bukkit Build 170

    Attached Files:

  4. Offline


    first of all there is 20-30 sec lagg , essentials ichat isent working anymore, cant find the antixray config file . and how long do the pluggin take to run normal. its been 1 houer now and still lagg
  5. Offline


    Well 130 coal is certainly not something you find normally so yeah, I have to see if I can replicate this. Did you rollback or do you still have it? Also do you have world.index.txt (with world being the name of the world you are on) It lists the number of ores of each type in each chunk in the data file.
  6. Offline


    I run essentials and it worked fine with this mod, no lag. Console logs might help the developer understand what is happening.

    Unfortunetly not, my interest was rolling back my server as quickly as I could, sorry. However, when I try this plugin once you release a new version, I will be sure to keep those two in the case of issues.

    The logic is genious but the implementation is somewhat wonky at this stage :p

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 13, 2016
  7. Offline


    The config file is not created by default. It takes anything from 2 sec to 5 minutes to start depending on how many chunks you have loaded at startup. It can be laggy with many players on or if you are exploring chunks that have not been scanned yet. No idea why essentials ichat would not work with this.
  8. Offline


    well everything is going bananas for me ,,
    ill try and wait some more and see if lagg stops,,
    my txt is alreadt at 2130 chunks look like it stoped now but still lagg

    do i need to make a config file manualy then ?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 13, 2016
  9. Offline


    If you want to change the default configuration yes.
  10. Offline


    If I reload the plugins while I just throw in this plugin, it "works". If I /axr off and then /axr on it locks up. If I start up the server, it locks up.

    I get this if i try the /axr on command.
    2011-04-12 16:09:15 [SEVERE] java.lang.ArrayIndexOutOfBoundsException: 7
    2011-04-12 16:09:15 [SEVERE]     at com.asdaarg.bukkit.antixray.BChunk.BandExpose(
    2011-04-12 16:09:15 [SEVERE]     at com.asdaarg.bukkit.antixray.AWorld.BandExpose(
    2011-04-12 16:09:15 [SEVERE]     at com.asdaarg.bukkit.antixray.AntiXRay.Expose9Chunks(
    2011-04-12 16:09:15 [SEVERE]     at com.asdaarg.bukkit.antixray.AntiXRay$1$
    2011-04-12 16:09:15 [SEVERE]     at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(
    2011-04-12 16:09:15 [SEVERE]     at net.minecraft.server.MinecraftServer.h(
    2011-04-12 16:09:15 [SEVERE]     at
    2011-04-12 16:09:15 [SEVERE]     at
    2011-04-12 16:09:15 [SEVERE] Unexpected exception
    java.lang.ArrayIndexOutOfBoundsException: 7
        at com.asdaarg.bukkit.antixray.BChunk.BandExpose(
        at com.asdaarg.bukkit.antixray.AWorld.BandExpose(
        at com.asdaarg.bukkit.antixray.AntiXRay.Expose9Chunks(
        at com.asdaarg.bukkit.antixray.AntiXRay$1$
        at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(
        at net.minecraft.server.MinecraftServer.h(
    2011-04-12 16:10:32 [INFO] Read timed out
    This is what I get if I start the server.
    2011-04-12 16:13:23 [SEVERE] java.lang.NullPointerException
    2011-04-12 16:13:23 [SEVERE]     at com.asdaarg.bukkit.antixray.log.log(
    2011-04-12 16:13:23 [SEVERE]     at
    2011-04-12 16:13:23 [SEVERE]     at
    2011-04-12 16:13:23 [SEVERE]     at
    2011-04-12 16:13:25 [SEVERE] java.lang.NullPointerException
    2011-04-12 16:13:25 [SEVERE]     at com.asdaarg.bukkit.antixray.log.log(
    2011-04-12 16:13:25 [SEVERE]     at
    2011-04-12 16:13:25 [SEVERE]     at
    2011-04-12 16:13:25 [SEVERE]     at
    2011-04-12 16:13:25 [SEVERE] java.lang.NullPointerException
    2011-04-12 16:13:25 [SEVERE]     at com.asdaarg.bukkit.antixray.log$
    2011-04-12 16:13:25 [SEVERE]     at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(
    2011-04-12 16:13:25 [SEVERE]     at net.minecraft.server.MinecraftServer.h(
    2011-04-12 16:13:25 [SEVERE]     at
    2011-04-12 16:13:25 [SEVERE]     at
    2011-04-12 16:13:25 [SEVERE] Unexpected exception
        at com.asdaarg.bukkit.antixray.log$
        at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(
        at net.minecraft.server.MinecraftServer.h(
    The config.txt is this:
    I've uploaded the debug.log(debug.txt because the forums don't like .log) if you wanted to look at it.
    Using build 670 and your plugin version 0.1.4.

    Plugins we are using:
    FalseBookExtra BetterShop Permissions EssentialsSpawn MyHome iConomyChestShop Honeypot Stargate iConomy Vanish HeroicRebuke HeroChat dynmap iChat NoCheat GroupManager mcMMO FakeMessage OddItem BorderGuard FalseBookCart WorldEdit LWC WorldGuard Essentials mcbans StealthLogin LogBlock FalseBookBlock Jail

    Hope this is helpful.

    Attached Files:

  11. Offline


    Ok confirmed the ore restoring isn't working as it should. There's far above normal levels of ore appearing while digging.
    Edit: Also think I know why now...
    Edit: Fixed
  12. Offline


    Basically I tested this, with it installed everything is fine until someone uses Xray. Lag was minimal after initial scan. Could use some tweaking. The issue is that when someone turns on Xray it seems to rescan and when it does this mineral deposits form all over the map either in the old spots or replicating. Deposits of Iron and Coal floating above ground where mountains was removed to build cities. Its like in the process of trying to scan and block the ore it rebuilds ore that has already been mined.
  13. Offline


    maxys should have the same number of elements as materials. I could put in a check that disables the plugin if that is not true. axr on can take a while, especially if you have a lot of chunks loaded.

    Sounds very weird. The Xray mod supposedly only analyses data it got from the server. It does not query the server about chunks. Otherwise it would be very easy to detect whether someone uses it or not. There's most probably something else going on here. It almost sounds like the data file has gotten corrupted. Can you post your worldname.index.txt?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 13, 2016
  14. Offline


    remove you download link until you fixed the problem dont post so unstable pluggins . tnx for fucking up my server
  15. Offline


    Well, it would help if you explain what the problem is. Just saying "fucking up my server" doesn't explain much. I posted a warning in red letters from the start to back up your worlds, and that's something you should do anyway.
  16. Offline


    You could at least say that your plugin might completly screw up a map, and that you should backup first :/

    EDIT : Ho, it's written, then use a huge font size ;D
  17. Offline


    Wow dont rant about things people do for free. If you were smart enough you would have made a backup so no damage would be done. Besides, the issues were raised a while ago about some possible bugs, perhaps read and do a risk assessment. Dont Q.Q because of your ignorance, he is making a plugin to HELP people and solve a big issue, which nobody else has yet to do as successfully as this.

    I plan to use this plugin later, when hopefully some issues have be fixed. The concept is great, and should really crack down on idiots x-raying.
  18. Offline


    I guess I'm slightly confused with maxys. Does it work as, the first number in material is to match the first number of maxys? Or is it simply meaning the number in maxys needs to match the level of everything down/up of that level to be hidden?
  19. Offline


    How about you read the description and gain an understanding of how a plugin works (and the inherrint risks) before using it dipshits. The description clearly says to backup your map and that the plugin is still being tested, if you cant be arsed reading plugin descriptions than you are a piss poor server owner who probably runs some crappy, unnotable community.
  20. Offline


    I'm working on an optimization that should speed up all light checks many times over. That should fix all lag issues except for lag due to scanning new chunks for the first time.

    the x:th number in material matches the x:th number in maxys. I used the numbers given here:
    It is the "none above"+1

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 13, 2016
  21. Offline


    Good idea ! But when someone brake iron bloc, an other iron bloc spawn near.

    How can i fix it ?

  22. Offline


    This may be because of high latency making a hidden ore appear to pop up, or because you are mining the dark.
  23. Offline


    Ah. So if I didn't want anyone to see a diamond block, 57, I would set it as, 1 to hide it at all levels?
  24. Offline


    128 for all levels
  25. Offline


    Alright. Thanks for the help. I'll see if it works after playing with the config file.
  26. Offline


    As requested although probably a little late here's my whole antixray folder including logs

    Attached Files:

  27. Offline


    already told you it lagg the server 30 sec + and even when deleting the plugging is still ghosting the server,,.
    you are saying backup but what if what if ppl dont want this anymoreafter using it for awile, cant go back to an old bacup in this case
    you are addeting the core of the game and making it imposible to remove it later on,,
    mabe it just hapening to my server
  28. Offline


    To be honest, it explains exactly what the plugin does, it replaces all the ores with stone.
    It doesn't take a genius to realise that if the plugin malfunctions then it wont be changing them back.
    It clearly explains to back your map up as well as stating its experimental and not yet working correctly.

    he's made an epic plugin but it does need a bit of work. Lay off him because without developers making anti-hack plugins your server is fucked anyway if you want to keep it fair.

    Obviously you're mad because you didn't back it up but if you would have read it in detail before you downloaded and installed it then you wouldn't be in this situation.
    Its hardly his fault.
  29. Offline


    How do you mean ghosting the server? Are you sure it is related to my plugin?
  30. Offline


    im not mad im helping,and there is backup, telling him there is a big bug . so hold you thoung abit budy dr.herbalisem. . mabe the problem is a comunication failur betwen mcmyadmin and your pluggin,
    you can join my server and see tha lagg yourself and the pluggin is deleted, everything looks normal . only the lagg that still is ghosting, looks like it still trying to upload chunks , even when the plugin isent there. .
    server is fin until another players join, it cant handle two players. ..
    do you know if your plugin have any conflikt to any other pluggin, i have alot of pluggins installed, so it whod be to great help trying to delet the ones you know about first if ther is any knownd conflickt,

    and herbalisem the plugin isent that epic yet wen ,it cant be removed agien, but the ide and work he do that is epic.
    i respect him for making this, and telling my point of view that its still an no go when it fucks up one server, if it isent stable it isent , and a warning message that is telling that this pluggin change the core of the game and will follow the server til it end even after removal , the pluggin can still conflikt and lagg the server shod be posted, becas it dosent say anyting about that this pliggin is unremovable after install
  31. Offline


    this is most definitely a plugin worth having once the bugs are worked out. we had our first xray player today.

Share This Page