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

    asdaarg

    AntiXRay
    Version:v0.6.10

    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



    Description:

    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.



    Downloads:
    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
    AntiXRay
    Source and old versions

    Features:
    - 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.

    Commands:

    /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)

    permissions:

    antixray.axr.on
    antixray.axr.off
    antixray.axr.worlds
    antixray.axr.chunk
    antixray.axr.chunk.regen
    antixray.axr.chunk.regen.ore
    antixray.axr.map
    antixray.axr.show
    antixray.axr.hide
    antixray.axr.dump
    antixray.axr.diff
    antixray.axr.gen
    antixray.axr.gen.copy
    antixray.axr.test
    antixray.axr.pack
    antixray.axr.backup
    antixray.axr.mirrorworld
    config.txt:

    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.


    changelog:
    v0.6.10
    • Fixed Array index out of bounds in listindex accessing materials that has not been loaded yet.
    v0.6.9
    • Added /axr mirrorworld <world> <mirrorworld> command
    v0.6.8
    • Fixed NPE when trying to expose ores in world hole.
    v0.6.7
    • checking whether wrong file exist during repack.
    v0.6.5
    v0.6.6
    • fixed NPEs in some commands that can occur if you use it and the world is off.
    v0.6.5
    • fixed open file pointers during repack.
    v0.6.4
    • fixed NPE during repack when load fails.
    v0.6.3
    • fixed NPE when running test on all worlds and not all worlds are on
    • added various memory checks and chunk data entry overwrite checks
    v0.6.2
    • fixed NPE when trying to flush the debug file when debug file is turned off.
    v0.6.1
    • 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
    v0.6
    • /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
    v0.5.21
    • 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
    v0.5.20
    • Additional file corruption checks that will make noise as soon as something goes wrong
    v0.5.19
    • Fixed another potential index derangement bug.
    v0.5.18
    • Fixed array out of bounds exception during previous fix
    v0.5.17
    • 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.
    v0.5.16
    • fixed half of ore not being hidden when a chunk is generated on load.
    • removed various unnecessary details to be logged in debug.log
    v0.5.15
    • 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
    v0.5.14
    • Switched to non physics updating block material setting hack
    • Updated to #733
    v0.5.13
    • Added detailed debug logging of background processes.
    • removed logging of filepointer
    v0.5.12
    • 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.
    v0.5.11
    • fixed /axr gen not unloading chunks that were originally not loaded
    v0.5.10
    • /axr gen and /axr gen copy now actually usable
    v0.5.9
    • ore in stone filter now also applies to /axr off and /axr show (not just when it is found by light detection)
    v0.5.8
    • 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
    v0.5.7
    • 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)
    v0.5.6
    • fixed ore regen not working when axr is off in that world
    • removed physics lock spam
    v0.5.5
    • fixed more concurrency errors during background processes (hopefully for the last time)
    v0.5.3
    • fixed more concurrency errors during background processes
    v0.5.2
    • fixed concurrency errors during background processes
    v0.5.1
    • fixed debug off in config file causing unable to start (again! although different place now)
    v0.5
    • 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
    v0.4.1
    • 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
    v0.4
    • 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
    v0.3.3
    • 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.
    v0.3.2
    • 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
    v0.3.1
    • Fixed silly nullpointer exceptions
    v0.3
    • 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)
    v0.2.5
    • 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
    v0.2.4
    • Fixed bug locating exposed-face-to-ore index elements having no array bounds check.
    v0.2.3
    • Fixed bug exposed-face-to-ore index elements not being removed
    v0.2.2
    • 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
    v0.2.1
    • 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
    v0.2
    • 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
    v0.1.5
    • Fixed bug in ore restoring function causing large veins of ore to be generated out of nothing
    • More detailed debug log
    v0.1.4
    • 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.
    v0.1.3
    • 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
    v0.1.2
    • Fixed bug due to player location being null for some weird reason
    • Added debug logging of time spent on the main time consuming procedures.
    v0.1.1
    • Fixed config file not loading properly
    • Removed wtfexception spam
    v0.1
    • Initial Release
    Donate (Not necessary but appreciated)
     
  2. Offline

    Graloth

    Understandable, but could you at least upload them elsewhere then? the links don't work atm :( that is, unless you're already working on that
     
  3. Offline

    asdaarg

  4. Offline

    Graloth

    awesome, thanks! could you also make an alternate download for NSCommand? (just in it's own thread) since it's required for AntiXRay
     
  5. Offline

    asdaarg

    I'm having partial success mitigating the problem after reverse engineering mc code. Walking south and west ore is hidden all of the time, while walking east or north is is hidden some of the time.
    Edit: Total success now, all ore can be hidden now except a ring around spawn which can easily be removed with /axr off /axr on for now :)
     
  6. Offline

    RazMaTaz

    Wow, such a conundrum shrouded in mystery! LOL .. or CF for short!
    I kept meaning to ask about the IsDecorated flag but kept forgetting.

    And whats the deal with dropbox I'm curious you have a link I could read about the problem?
     
  7. Offline

    asdaarg

    Well you could read the TOS: https://www.dropbox.com/dmca#terms and then think about if you really want to sign on to all that stuff.

    It turned out there is a "done" flag, but it but its not completely done until the N, NE, and E chunks have been generating their ore since it spills over into that chunk and thus leaving ore visible, so I simply had to check that its done on all 4 of them, and if it isn't, try again a second later.

    Anyone have ideas of what players should do to hide their chests? Type a command? Hide it under a rock? To integrate it with the existing algorithm, it would be best if the chest is put in pitch black and that it is changed into smooth stone.

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

    Zalastri

    I was under the impression that since 1.5 ore is occluded. I was testing on my server using an xray texture pack to try to get a feel for what xray looks like and whatnot, and I noticed that ore no longer appears until it's exposed to air. (Valuable ore that is, like diamond and gold)
     
  9. Offline

    asdaarg

    That's always been the case with texturepacks. The xray mod will bypass this though and let you see ore that's not exposed to air. What 1.5 allows you to do is to have it not render faces that are behind other faces, these being among the ones that are exposed to air, and this can be turned off from graphics options.
     
  10. Offline

    Zalastri

    Hm. That's upsetting. Was hoping they'd fixed the problem from their end. So is this plugin stable enough for a public server at the moment? I'm already having CPU load issues though.. :\
     
  11. Offline

    asdaarg

    Its very hard to say. As long as I'm developing and adding new features, there is a chance of it breaking, as can mc updates. Just recently there were a bunch of problems, and I'm not sure if they all got solved yet; there's not been enough testing, but there has not been any bug reports yet after the couple of bugfixes I made. Just keep backups of both worlds and ore files. There is a way to restore ore despite not having any backups also, and there is a way to check that your ore is intact, using the /axr dump and /axr diff commands. It used to be quite CPU intensive, until 0.4.x. but you can still experience lag spikes when people explore new areas.
     
  12. Offline

    Rick

    thanks and good luck
     
  13. Offline

    zlavik

    got this error verison: v0.5.16 bukkit 735

    2011-04-27 22:11:10 [WARNING] Task of 'AntiXRay' generated an exception
    java.lang.NullPointerException
    at com.asdaarg.bukkit.antixray.AWorld.show(AWorld.java:103)
    at com.asdaarg.bukkit.antixray.AWorld.show(AWorld.java:127)
    at com.asdaarg.bukkit.antixray.AXRUtil$2.run(AXRUtil.java:389)
    at com.asdaarg.bukkit.antixray.AXRUtil$runner.run(AXRUtil.java:321)
    at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:128)
    at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:358)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:285)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
     
  14. Offline

    grizzlymann

    Hi sorry to ask a potentially obvious questions but what is the command to replace all ores on an existing map after initial install?

    Thanks for your time.
     
  15. Offline

    asdaarg

    What command were you typing when you got this?

    After initial install, it does this automatically. But it is gradual, and ore is hidden as chunks are loaded. To hide all at once would require knowing what all chunks have been generated, which bukkit does not provide me info about, I'd have to dig into the region files.

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

    grizzlymann

    Thanks for the quick response! That method sounds like it will work well with my server.
     
  17. Offline

    asdaarg

    Thanks, the bug was fixed in 0.5.16.

    Fixed now in 0.5.17 (hopefully)

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

    UfaRock

    What's wrong? How do I fix it?

     
  19. Offline

    SynMonger

    Using craftbukkit 733, I get the following issues:

    During server startup
    Code:
    2011-04-28 13:10:06 [SEVERE] Java heap space loading AntiXRay v0.5.17 (Is it up to date?)
    java.lang.OutOfMemoryError: Java heap space
    	at com.asdaarg.bukkit.antixray.AWorld.LoadChunkA(AWorld.java:364)
    	at com.asdaarg.bukkit.antixray.AWorld.LoadChunkB(AWorld.java:421)
    	at com.asdaarg.bukkit.antixray.AWorld.loadChunk(AWorld.java:485)
    	at com.asdaarg.bukkit.antixray.AWorld.getBChunk(AWorld.java:507)
    	at com.asdaarg.bukkit.antixray.AWorld.Load(AWorld.java:169)
    	at com.asdaarg.bukkit.antixray.AntiXRay.axr_on(AntiXRay.java:291)
    	at com.asdaarg.bukkit.antixray.AntiXRay.CMD_axr_on(AntiXRay.java:309)
    	at com.asdaarg.bukkit.antixray.AntiXRay.onEnable(AntiXRay.java:87)
    	at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:127)
    	at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:632)
    	at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:218)
    	at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:116)
    	at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:94)
    	at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:217)
    	at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:204)
    	at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:144)
    	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:259)
    	at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
    
    And the entire memory heap is taken up. As a test I ran without anti xray and with two players on the server only uses 185MB of RAM.

    During normal use
    Code:
    2011-04-28 13:08:56 [SEVERE] Could not pass event BLOCK_PHYSICS to AntiXRay
    java.lang.ArrayIndexOutOfBoundsException: 0
    	at com.asdaarg.bukkit.antixray.BChunk.Expose(BChunk.java:487)
    	at com.asdaarg.bukkit.antixray.AWorld.Expose(AWorld.java:429)
    	at com.asdaarg.bukkit.antixray.AntiXRay$2.onBlockPhysics(AntiXRay.java:141)
    	at org.bukkit.plugin.java.JavaPluginLoader$23.execute(JavaPluginLoader.java:340)
    	at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
    	at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:257)
    	at net.minecraft.server.World.k(World.java:378)
    	at net.minecraft.server.World.applyPhysics(World.java:364)
    	at net.minecraft.server.World.update(World.java:334)
    	at net.minecraft.server.World.setTypeId(World.java:306)
    	at net.minecraft.server.ItemInWorldManager.c(ItemInWorldManager.java:139)
    	at net.minecraft.server.ItemInWorldManager.d(ItemInWorldManager.java:166)
    	at net.minecraft.server.ItemInWorldManager.b(ItemInWorldManager.java:118)
    	at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:434)
    	at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
    	at net.minecraft.server.NetworkManager.a(NetworkManager.java:195)
    	at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:74)
    	at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
    	at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:370)
    	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:285)
    	at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
    
     
  20. Offline

    TehJammers

    Same as above, with the second one under normal use.
     
  21. Offline

    asdaarg

    Fixed ArrayIndexOutOfBoundsException.

    SynMonger, can I have a look at your .index.txt file(s)?
     
  22. Offline

    SynMonger

    I've only got one world, pasted below:
    Show Spoiler
    room for:10396 chunks found...10396 chunks:
    chunk entry:0@3620028 (11,11)@1788774[13,87,196,0,7,19,0,]
    chunk entry:1@3620040 (-34,-34)@2763709[0,0,0,0,0,0,0,]
    chunk entry:2@3620052 (-9,-9)@592967[0,0,0,0,0,0,0,]
    chunk entry:3@3620064 (-24,-24)@965172[0,0,0,0,0,0,0,]
    chunk entry:4@3620076 (-17,-17)@911984[0,0,0,0,0,0,0,]
    chunk entry:5@3620088 (-51,-51)@2942148[2,64,144,0,4,17,0,]
    chunk entry:6@3620100 (14,14)@1838586[2,56,114,0,2,14,0,]
    chunk entry:7@3620112 (-3,-3)@660057[0,0,0,0,0,0,0,]
    chunk entry:8@3620124 (-18,-18)@912581[0,0,0,0,0,0,0,]
    chunk entry:9@3620136 (9,9)@58848[0,0,0,0,0,0,0,]
    chunk entry:10@3620148 (-42,-42)@1455173[0,69,105,0,8,19,0,]
    chunk entry:11@3620160 (-26,-26)@1252561[0,0,0,0,0,0,0,]
    chunk entry:12@3620172 (20,20)@3315915[2,32,97,0,0,4,0,]
    chunk entry:13@3620184 (19,19)@3304455[8,37,53,0,0,24,0,]
    chunk entry:14@3620196 (18,18)@3296750[0,26,58,0,0,18,0,]
    chunk entry:15@3620208 (17,17)@3291713[6,53,61,0,0,13,0,]
    chunk entry:16@3620220 (16,16)@3288739[6,34,41,0,0,23,0,]
    chunk entry:17@3620232 (15,15)@3285595[4,38,96,0,0,4,0,]
    chunk entry:18@3620244 (12,12)@3273631[3,36,68,0,0,17,0,]
    chunk entry:19@3620256 (-48,-48)@2408634[7,72,181,0,3,15,0,]
    chunk entry:20@3620268 (-35,-35)@925491[11,33,97,0,2,18,0,]
    chunk entry:21@3620280 (-37,-37)@935034[5,82,197,2,8,22,0,]
    chunk entry:22@3620292 (-25,-25)@965544[0,0,0,0,0,0,0,]
    chunk entry:23@3620304 (5,5)@28341[0,0,0,0,0,0,0,]
    chunk entry:24@3620316 (-32,-32)@998046[0,0,0,0,0,0,0,]
    chunk entry:25@3620328 (-12,-12)@555921[0,0,0,0,0,0,0,]
    chunk entry:26@3620340 (-11,-11)@568097[0,0,0,0,0,0,0,]
    chunk entry:27@3620352 (10,10)@66437[0,0,0,0,0,0,0,]
    chunk entry:28@3620364 (7,7)@40033[0,0,0,0,0,0,0,]
    chunk entry:29@3620376 (-27,-27)@910341[0,0,0,0,0,0,0,]
    chunk entry:30@3620388 (-14,-14)@678984[0,0,0,0,0,0,0,]
    chunk entry:31@3620400 (-46,-46)@1507351[7,70,106,4,4,18,0,]
    chunk entry:32@3620412 (-19,-19)@913015[0,0,0,0,0,0,0,]
    chunk entry:33@3620424 (-8,-8)@605119[0,0,0,0,0,0,0,]
    chunk entry:34@3620436 (-2,-2)@671190[0,0,0,0,0,0,0,]
    chunk entry:35@3620448 (-41,-41)@955348[11,70,97,0,0,17,0,]
    chunk entry:36@3620460 (-36,-36)@2763647[0,0,0,0,0,0,0,]
    chunk entry:37@3620472 (0,0)@0[<----suspicious face count
     
  23. Offline

    asdaarg

    Well, I have to say I wasn't very clever there, I put a suspicious face count warning, without having it print out the count. But I still know what the count is, because the file pointer points to 0, where it should find 22610 and should lead to an allocation of 135661 bytes. But the bigger stupidity of mine is to have it break at something like that. It should continue listing the entries. Since what version have you been using axr without doing /axr off in between?
     
  24. Offline

    jullleee

    i got the error,
    556/(677)
    hiden blblbabal
    10000 cunks

    but after that ^the server freeze. my map is very big. thats the problem?
     
  25. Offline

    SynMonger

    I have no idea what version(s) I've used, or that /axr off should be used when changing versions. At least I didn't see anything about that in the plugin description.
     
  26. Offline

    matjam

    Code:
    01:01:59 [INFO] Lindex error: lx[0]=16 x=10 ly[0]=7 y=6 lz[0]=7 z=15
    01:01:59 [INFO] Lindex error: lx[1]=16 x=11 ly[1]=7 y=6 lz[1]=8 z=13
    01:01:59 [INFO] Lindex error: lx[2]=16 x=12 ly[2]=8 y=6 lz[2]=6 z=14
    01:01:59 [INFO] Lindex error: lx[3]=16 x=12 ly[3]=8 y=6 lz[3]=7 z=15
    01:01:59 [INFO] Lindex error: lx[4]=16 x=11 ly[4]=9 y=7 lz[4]=4 z=14
    01:01:59 [INFO] Lindex error: lx[5]=16 x=11 ly[5]=9 y=7 lz[5]=5 z=15
    01:01:59 [INFO] Lindex error: lx[6]=16 x=14 ly[6]=9 y=7 lz[6]=6 z=7
    01:01:59 [INFO] Lindex error: lx[7]=16 x=15 ly[7]=9 y=7 lz[7]=7 z=7
    01:01:59 [INFO] Lindex error: lx[8]=16 x=14 ly[8]=10 y=8 lz[8]=4 z=5
    01:01:59 [INFO] Lindex error: lx[9]=16 x=4 ly[9]=10 y=5 lz[9]=9 z=9
    01:01:59 [INFO] Lindex error: lx[10]=16 x=7 ly[10]=11 y=6 lz[10]=9 z=10
    01:01:59 [INFO] Lindex error: lx[11]=16 x=14 ly[11]=37 y=9 lz[11]=5 z=15
    01:01:59 [INFO] Lindex error: lx[12]=16 x=5 ly[12]=38 y=37 lz[12]=5 z=4
    01:01:59 [INFO] Lindex error: lx[13]=16 x=6 ly[13]=38 y=37 lz[13]=6 z=3
    01:01:59 [INFO] Lindex error: lx[14]=16 x=6 ly[14]=38 y=37 lz[14]=7 z=4
    01:01:59 [INFO] Lindex error: lx[15]=16 x=7 ly[15]=38 y=34 lz[15]=8 z=7
    01:01:59 [INFO] Lindex error: lx[16]=16 x=6 ly[16]=39 y=37 lz[16]=6 z=5
    01:01:59 [INFO] Lindex error: lx[17]=16 x=7 ly[17]=39 y=37 lz[17]=7 z=4
    01:01:59 [INFO] Lindex error: lx[18]=16 x=7 ly[18]=39 y=37 lz[18]=8 z=5
    01:01:59 [INFO] Lindex error: lx[19]=16 x=9 ly[19]=51 y=41 lz[19]=4 z=8
    01:01:59 [INFO] Lindex error: lx[20]=16 x=9 ly[20]=51 y=41 lz[20]=5 z=9
    01:01:59 [INFO] Lindex error: lx[21]=16 x=10 ly[21]=52 y=41 lz[21]=4 z=9
    01:01:59 [INFO] Lindex error: lx[22]=16 x=7 ly[22]=52 y=42 lz[22]=5 z=6
    01:01:59 [INFO] Lindex error: lx[23]=16 x=9 ly[23]=54 y=42 lz[23]=15 z=7
    01:01:59 [INFO] Lindex error: lx[24]=16 x=9 ly[24]=54 y=42 lz[24]=14 z=8
    01:01:59 [INFO] Lindex error: lx[25]=16 x=6 ly[25]=55 y=46 lz[25]=15 z=15
    01:01:59 [INFO] Lindex error: lx[26]=16 x=14 ly[26]=55 y=51 lz[26]=14 z=5
    01:01:59 [INFO] Lindex error: lx[27]=15 x=15 ly[27]=59 y=51 lz[27]=13 z=4
    01:01:59 [INFO] Lindex error: lx[28]=15 x=15 ly[28]=59 y=51 lz[28]=14 z=5
    01:01:59 [INFO] Lindex error: lx[29]=15 x=15 ly[29]=59 y=52 lz[29]=14 z=4
    01:01:59 [INFO] Lindex error: lx[30]=16 x=15 ly[30]=59 y=52 lz[30]=15 z=4
    01:01:59 [INFO] Lindex error: lx[31]=15 x=15 ly[31]=60 y=52 lz[31]=13 z=5
    01:01:59 [INFO] Lindex error: lx[32]=15 x=13 ly[32]=60 y=54 lz[32]=14 z=14
    01:01:59 [INFO] Lindex error: lx[33]=15 x=14 ly[33]=60 y=54 lz[33]=14 z=14
    01:01:59 [INFO] Lindex error: lx[34]=16 x=14 ly[34]=60 y=54 lz[34]=15 z=14
    
    Is this from AntiXRay?
     
  27. Offline

    asdaarg

    Not sure how you can get that. Is that from server log or where? Did you copy&paste or go from memory?

    Yes, did you do /axr off and /axr on at startup? If not, you will likely get this if you are upgrading from 0.5.17 or prior. Doing it will refresh the indices of the faces of ore blocks exposed to air and flush out all these errors, and hopefully there will be no more of them. If there are then I have more bugs to fix.

    Well its not like it should be used. If you have a big map and don't want to rescan it each time then you wouldn't want to do that. If you do it however, potential errors from previous versions will not stay around that have been fixed in later versions. It also makes it easier for me to debug potential errors.

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

    matjam

    Fair enough. I'm running the /axr off, its taking a long time :) A lot more chunks on one of the worlds that I didn't know about. :)
     
  29. Offline

    jullleee

    from my memory
     
  30. Offline

    asdaarg

    Well it looks like something you get when you've run a /axr on or hide command, and its not an error. Do you get any errors in server log? Also what version of axr and cb are you using?
     
  31. Offline

    Black_Jack

    I tried few times /axr on, /axr off to test it. And now some ores are appears with x-ray. Is it normal? Or how to fix it?
     

    Attached Files:

Share This Page