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


    I updated to 0.2.6 and my log is getting filled with this:

    2011-05-15 00:13:16 [INFO] CORRUPTION WARNING: suspicious face count:7168@820060
    2011-05-15 00:13:16 [INFO] FATAL ERROR: negative face count:-14666@812924
    2011-05-15 00:13:16 [INFO] CORRUPTION WARNING: suspicious face count:15935@805505
    2011-05-15 00:13:16 [INFO] CORRUPTION WARNING: suspicious face count:3855@798410
    2011-05-15 00:13:16 [INFO] CORRUPTION WARNING: suspicious face count:14649@846949
  3. Offline


    Maybe this Preview supports you ..

    I failed with the Intro .. i know

  4. Offline


    And your index.txt still looks nothing extraordinary? If so, then either one is false alarm or the other is not reporting errors.

    Btw for interpreting the .index.txt file:

    chunk entry:1471@1433617 (33,50)@361500[6,12,60,0,5,4,]
    chunk entry:1472@1433629 (34,49)@361827[4,33,18,0,0,5,]
    chunk entry:1473@1433641 (35,48)@362046[0,27,52,0,0,8,]

    362046 - Where the chunk data entry is stored in the file <-- not important
    (35,48) - Chunk coordinates <-- (x,z block coordinates divided by 16) Check that these are reasonable
    1433641 - Where the chunk index entry is stored in the file <-- not important
    [0,27,52,0,0,8,] Number of ores of each type in the order specified in config.txt <-- Check that these are reasonable

    Sorry if I'm being confusing. Since I guess you have a large map and not enough RAM to regenerate it all at once it is best to go with the rectangular method so never mind. There is a link under description to how to recover your ore.

    Impressive :)

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


    i used this for 8 hours now i have a corruption errors and ores dont show up...great.

    uninstall and rollback.....sheeesh. thought this would be a good idea.
  6. Offline


    Updated to newest version .. first login problem still exists.
    Server Side
    v11:39:50 [INFO] RazMage lost connection: disconnect.overflow

    Client Side
    Internal Exception: Software cause connection abort: recv failed

    My server is tiny player wise, map is 166 megs. I did a axr off before updating. Will see how it goes.

    AntiXRay [0.6.2]

    Show Spoiler
    11:45:11 [INFO] CORRUPTION WARNING: suspicious face count:1542@11883
    11:45:11 [SEVERE] null
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
            at java.lang.reflect.Method.invoke(Unknown Source)
            at com.asdaarg.bukkit.NSCommand.NSCommand.Command(
            at com.asdaarg.bukkit.NSCommand.NSCommand$1.onPlayerCommandPreprocess(NS
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
            at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.Packet3Chat.a(
            at net.minecraft.server.NetworkManager.a(
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(
    Caused by: java.lang.NullPointerException
            at com.asdaarg.bukkit.antixray.AntiXRay.axr_test(
            at com.asdaarg.bukkit.antixray.AntiXRay.CMD_axr_test(
            ... 22 more
    11:45:11 [INFO] RazMage issued server command: axr test

    Ingame I did a backup then a test and it responded .

    AXR:MysticForest ore file has errors.
    AXR:MysticForest ore file passed the test.
    AXR:MysticForest memory passed the test.

    All this was first boot/login of the server.

    Two maps. One axr is on, the other is not. Both debug options were off. Just turned on and will see what happens.

    If backup of ore file exists backup fails. (I think thats why)

    Axr chunk now shows 0(Zero) ore (at least in the chunk I logged in at)

    Console Major Errors on restart (Turned debug on) Don't know when they started.

    Show Spoiler
    11:51:19 [INFO] FATAL ERROR: negative face count:-14924@503613
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:15949@457393
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:27757@447591
    11:51:19 [INFO] FATAL ERROR 8
    11:51:19 [INFO] FILE LINDEX ERROR 6
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:14824@579706
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:15616@569048
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:9252@601997
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:13108@590868
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:14848@537870
    11:51:19 [INFO] FATAL ERROR: negative face count:-19275@526632
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:8995@536624
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:11565@588344
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:4112@598856
    11:51:19 [INFO] FATAL ERROR: negative face count:-15066@566676
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:20303@577058
    11:51:19 [INFO] FATAL ERROR: negative face count:-31854@469381
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:31869@479219
    11:51:19 [INFO] CORRUPTION WARNING: suspicious face count:14336@449797

    Debug Attached
    +tons more

    Rolled back to 0.5.21

    Attached Files:

  7. Offline


    Can i protect chests?
  8. Offline


    Raz: You always provide me such good bugreports, thanks for that :) I'll see if I can fix it now.

    Edit: The weird thing is the old test (index.txt) reports normal ore counts, but the new test reports strange ore counts.
    Edit: I'm at loss with this, you've turned on debugging too late apparently so I have no idea when it started. I can't replicate this, it works fine no matter what I do. I fixed the NPE with test though.

    Not yet, but will probably quite soon.

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

    The PC Tech Guy

    No, it's just that I don't have a multi-world configuration. So........ what should I do?
    Update: Plus, I'm getting FATAL ERROR 8 even after deleting my configuration....
  10. Offline


    Can I have a look at your debug.log so I can get to the bottom of this...
  11. Offline

    The PC Tech Guy

    Since it's too dang long...
    Anyways, it happens when I startup the server for the second time with AntiXray. Happens for a few seconds of spamming, then it stops.

    I trimmed it a bit...

    Attached Files:

  12. Offline


    It looks like a false alarm. no ores should not cause fatal error 8. The reason I don't get this error is because I don't have these dead 0 ore chunks, probably a relic from a much earlier version of axr
    Edit: No that doesn't explain it.
  13. Offline

    The PC Tech Guy

    Weird, I'll try again and report back.

    Now I get a suspicious face count. Yay. And the debug log is now 768 KB. And a fatal error: negative face count.

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


    How does your .index.txt look like now?
  15. Offline

    The PC Tech Guy

    Same as how I got fatal error 8, just this suspicious face count instead. Although /axr off works fine, and faster in fact than the older versions.

    Attached Files:

  16. Offline


    The ore counts look ok to me except for the dead chunks. Do an /axr off then /axr on and see if the suspicious face counts disappear as well
  17. Offline

    The PC Tech Guy

    Got a negative face count, then a repack failed, contact the author upon /axr on.
    2011-05-15 15:59:41 [INFO] The_PC_Tech_Guy used command "/axr on"
    2011-05-15 15:59:41 [INFO] FATAL ERROR: negative face count:-25686@3904
    2011-05-15 15:59:41 [INFO] Error: Repack failed - Please contact the author.
  18. Offline


    and index.txt still looks like before?
  19. Offline

    The PC Tech Guy

    I don't know, I'll upload it again. It is also showing those two lines every server start up, so it's unable to do it...

    Oh, it's bigger.... anyways, it's unable to hide ores.

    Attached Files:

  20. Offline


    Ok this time its showing a lot of errors...
  21. Offline


    Ok, tried again with same results. I enabled debug before upgrading/ and before /axr off with old version.

    Steps: Enabled Debug 0.5.2 and started server
    /axr off
    stop server
    update plugin (jar file)

    Start Server
    Login and then did a /axr worlds just because
    then in an attempt to reproduce exactly what I did i did a /axr backup twice (with no world name). Yes I did the wrong command in error, but then did a /axr backup MysticForest

    then did /axr test with same results as before both client output and console errors.. (I did not completely compare but looked the same)

    then just for something extra this time I did a /axr off which had no client output and had an exception in the server log.

    Attached is before/after upgrade debug files, along with server.log

    Attached Files:

  22. Offline

    The PC Tech Guy

    @RazMaTaz looks like we're having similar problems, although I'm starting fresh, and you're not... well, I have no idea what version 6 brought besides backups and bugs... maybe we should go back to 5.21. :p
  23. Offline


    Raz: Thanks for the report again. Although I still can't find out what the problem is, at least I've eliminated a few places to look thanks to your report. I will put in some extra checks that kick in when a chunk is being saved, because I start suspecting that something happens there with the face/ore counts and then it overwrites other entries and then all hell breaks lose, because I looked at some of the errors:
    and they have been correctly written at the correct place before, and its not possible for a negative face count to get there without it being overwritten (when it gets it from memory its from the length of an array which is always positive)
    Edit: mind if I have a look at your config.txt btw?
  24. Offline

    The PC Tech Guy

    @asdaarg I hope you get this fixed soon. I don't know what you did, but it's causing a lot of confusion. Keep up the good work, though ;)
  25. Offline


    I don't know what I did either, it worked so nicely when I tested it before release, in fact its still working nicely. I wish I knew what you guys are doing to get those errors :p Anyways, updated now, with a lot of checks.
  26. Offline

    The PC Tech Guy

    Nothing, in fact I started over with a new ore file after successfully restoring my ore. It has something to do with the new .ore thing.......... if you changed how it's formatted....
  27. Offline


    getting 404 on the plugin file
  28. Offline


    config.txt [0.5.2]
    no change for upgrade, drop jar and go.

    Show Spoiler

    I am curious why so many duplicate lines with the CMD_

    Don't have time to test 0.6.3
  29. Offline


    all your download links seem to be broken for me anyone else having this problem?
  30. Offline


    I managed to get it from the rapidshare link

    starting up my server I got this:
    2011-05-16 00:09:23 [INFO] AXR: Loading/Scanning Chunks
    2011-05-16 00:09:24 [INFO] repack
    2011-05-16 00:09:24 [INFO] FATAL ERROR 8
    2011-05-16 00:09:24 [SEVERE] null loading AntiXRay v0.6.3 (Is it up to date?)
        at com.asdaarg.bukkit.antixray.BChunk.size1(
        at com.asdaarg.bukkit.antixray.BChunk.byteSize(
        at com.asdaarg.bukkit.antixray.BChunk.Load(
        at com.asdaarg.bukkit.antixray.AWorld.Repack(
        at com.asdaarg.bukkit.antixray.AWorld.<init>(
        at com.asdaarg.bukkit.antixray.AXR.makeWorld(
        at com.asdaarg.bukkit.antixray.AntiXRay.axr_on(
        at com.asdaarg.bukkit.antixray.AntiXRay.CMD_axr_on(
        at com.asdaarg.bukkit.antixray.AntiXRay.onEnable(
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(
        at net.minecraft.server.MinecraftServer.e(
        at net.minecraft.server.MinecraftServer.a(
        at net.minecraft.server.MinecraftServer.init(
    what does this error mean? has AXR actually loaded?

    i've had to go back to 0.5.21 because the v6 ones just aren't working for me, either the plugin fails to load at all or I get spammed with errors or both :( I even tried reloading all the ore and starting from scratch but v6 keep giving me that error ^ also because of corruption *somehow* I had to load a 3day old ore file so I think I lost a bunch of chunks :|
  31. Offline


    It happened because I did some of the error checks in the wrong order. Fixed now. 0.6.x will not allow files with these errors to be loaded by default.
    Edit: You could do /axr off in 0.5.21 to start with a clean ore file in 0.6.x.
    You can use the .bak file, it should always create before a repack (if you have autobackup on, which it is by default)

Share This Page