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

    Xepher

    I really need the 5.21 version of axr and the link given by the OP appears to be broken. May someone have a working link ?
     
  3. Offline

    RazMaTaz

    Hmm.. I can't seem to get axr to turn on for a skyworld in game. Will try it with config.

    With it added to config, console states SkyWorld don't exist.

    Actually won't turn on for my nether(just a test).

    Both worlds were done using Multivers. Currently using CB build 820
    Maybe I should try the RB, but switch to 820 due to it fixes a Multiverse problem.
     

    Attached Files:

  4. Offline

    Xepher

    Please may someone have it ? because I'm currently running a world without any ore in....
     
  5. Offline

    RazMaTaz

    here is 0.5.21 Just remote the .zip extension. Its from all my backups and the plugin.yml stats is 0.5.21 :)

    You can also do everything on a separate machine, ignore the multiworld stuff, and delete all but the level.dat in your world folder. The server will recreate it when the server starts (well, the spawn area) and then you would need to follow the directions to generate the rest of your map.

    Then copy your ore file to the real server with same version axr and go for it. :) Or copy your current world to your test machine with the new ore file for test purposes before you make it go live.
     

    Attached Files:

    Last edited by a moderator: May 14, 2016
  6. Offline

    Ratchet

    hey asdaarg any news on an update to fix all these bugs and such?
     
  7. Offline

    Simon Andersen

    Hey,
    One of my friends, was starting to use xray mod on my server, so I researched for a way to solve this, and I found the plugin called AntiXray. I Installed it, and I typed in the command "axr on" and "axr hide". - Then my friend stopped use it, and I wan't it of again, cause its a bit annoying for the one who is mining. But when I typed in "axr off" and "axr show", it said that something like 70000 ores was restored, but no ores was really restored. Of course I was so stupid to not do a back up of my world, so I would like to hear - what could I do?

    I tried the "Foolproof solution" but, it turned out, that I am an idiot...
    Here is the "solution":

    Instructions for restoring ore without backups:


    1. Copy the world you want to restore ore in, lets call it w1 , to a new folder w2
    2. Delete the region folder in w2
    3. Start the server
    4. Import w2 using whatever multi-world plugin you have that can do it
    5. If your the index in your ore file is still intact you run/axr gen copy w1 w2. Otherwise you need to use a map utility that shows all chunks in w1 so you can figure out what rectangular area(s) to generate and then type/axr gen w2 x1 z1 x2 z2for the area(s) where x1,z1 and x2,z2 are two diametric corners in a rectangular area.
    6. Type/axr on w2 and repeat step 5
    7. Shut down the server
    8. replace the ore file w1 with w2 (you might want to make a backup of w1 just in case) They are located in AntiXRay folder in your plugins folder.
    9. Delete w2 (after removing/unregister it with the multi-world plugin so it doesn't get created again, if your multi-world plugin does that at startup)
    10. do:/axr off w1to filter out ore thats already been digged out. Then you can turn it back on with/axr on w1
    Even tho, that I tried this, as good as I can, I could not make the damn ores get back in.

    So if anyone had this problem and solved it, or if anyone knows a solution, please tell me in a "Very VERY foolproof" way.. :) Thank you!

    Please don't say stuff like: ALWAYS BACKUP! - I don't wan't to hear that. I know that now, and I learned by my mistake.
     
  8. Offline

    RazMaTaz

    I followed thost same instructions and had very good luck with my map. Where do you run into trouble at?

    If you don't care about original positions use NBT2 previously mentioned which is used offline.
     
  9. Offline

    DJ411

    i need help so i can stop ppl from viewing any Ore!!

    Code:
    debuglog=debug.log
    debug=true
    timerms=200
    maxdep=3000
    maxfaces=1000
    maxheight=128
    ChunkFileBuffer=20000
    autostart=true
    nounload=false
    fileindexdebug=true
    mapcol=x7a6d02899cce7888228d8ddeddxxxxxxxxdxaaadddddddd1dd41ddd8dddddddddddddddddddddfbfe89dd856edddddd
    mapwidth=50
    mapheight=20
    materials=14,15,16,21,56,73
    maxys=37,68,127,36,21,21
    worlds=
    schedulerload=30
    autobackup=true
    autorepack=true
    losvt=false
    lenient=false
    schedulerstatustimer=3000
    filterorenotinstone=true
    CMD_axr_worlds=
    CMD_axr_on=
    CMD_axr_on=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_map=
    CMD_axr_chunk_regen_ore=
    CMD_axr_chunk_regen_ore=
    CMD_axr_chunk_regen_ore=
    CMD_axr_chunk_regen=
    CMD_axr_chunk_regen=
    CMD_axr_chunk_regen=
    CMD_axr_chunk=
    CMD_axr_chunk=
    CMD_axr_off=
    CMD_axr_off=
    CMD_axr_show=
    CMD_axr_show=
    CMD_axr_hide=
    CMD_axr_hide=
    CMD_axr_dump=
    CMD_axr_diff=
    CMD_axr_gen_copy=
    CMD_axr_gen=
    CMD_axr_backup=
    CMD_axr_pack=
    CMD_axr_test=
    CMD_axr_test=
    
    Can someone help!
     
  10. Offline

    Simon Andersen

    Hey
    I actully ran into problems, when the MultiWorld thingy started. I have no experience with that, and I don't know how to "Import w2".
    And another place where I ran into problems was, where should I put in the w2 folder? And I can't just rename the "World" folder to "W2", then I guess the serveren wouldn't start?
     
  11. Offline

    Xepher

    Thanks a lot, It was really helpfull !

    I solved my problems but not without big troubles. I had to rollback my world for two days, with using my antiXray save....

    Anyway, I'm not gonna reemplement this plugin until it is more safe. Some ideas to bring it safer :
    - Make auto saves
    - Make less fat logfiles
    - Create a way to restore ores unless running the game or something else...

    Even if I won't use it anymore, I understand that this plugin is not so easy to create and I recognise the wealth of it. It did what I wanted him to do when I was using it. (But he didn't pass the 1.6.6 upgrade test :p)
     
  12. Offline

    Mhalkyer

    Does this work well with CB #818?
     
  13. Offline

    RazMaTaz

    All world folders go into the main cb folder. Create a folder called W2 if you wish and copy the level.dat from your world folder.

    if you use multiverse check the documentation, but its like /mvimport W2

    I have just a very small personal server for me and a few friends, and best I can tell its working.. When I upgraded I did an /axr off first. and then installed the new jar file and deleted the old plugin/AntiXRay folder

    I'm using 0.6.7 and CB820 currently, with MC 1.6.6

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

    godgodgodgo

    Does this work with the latest recommended build?
     
  15. Offline

    Asphodan

    Does not work well with 818.

    I had to revert the server to 1.5, turn AXR off, uninstall it, and go back to 1.6.

    Easy peasy.
     
  16. Offline

    godgodgodgo

    Hmmm needs updating then
     
  17. Offline

    bruceweed

    Someone should update this >.< for craftbukkit builds 818+ (its at stable build 839 now)
     
  18. the plugin is great, but there is one problem:
    when there are 4 diamonds closed near each other, and you hit all the stones around, only one of the four will appear again. the rest is still away.
    Is there something with the configuration false?
    Or why does the other diamonds do not appear again?
    (I am using antiXRay v. 0.5.21!)

    And my secound question:
    Is it possible to run that plugin on a VServer?
    Or does the plugin needs too much computerpower?

    greetings
    Chriss
     
  19. Offline

    Neils

    Is this working fine with 818 ?
    An if not, will it be updated ?
     
  20. Offline

    RazMaTaz

    asdaarg- Any status updates?

    Error:
    Show Spoiler
    Code:
    16:44:41 [WARNING] Task of 'AntiXRay' generated an exception
    java.lang.NullPointerException
            at com.asdaarg.bukkit.antixray.AWorld.BandExpose(AWorld.java:463)
            at com.asdaarg.bukkit.antixray.AXR.Expose9Chunks(AXR.java:56)
            at com.asdaarg.bukkit.antixray.AntiXRay$2.run(AntiXRay.java:105)
            at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(C
    raftScheduler.java:138)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:388)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:311)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)


    Debug.log Excert.

    Show Spoiler
    Code:
    2011.06.09 04:44:41 Periodic light check[171µs]
    2011.06.09 04:44:41 Periodic light checkwtfexception: couldn't find-60,62
    2011.06.09 04:44:41 onChunkUnLoad -74,58:[5µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,58:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -72,58:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -71,58:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -70,58:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -69,58:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -68,58:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -67,58:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -74,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -72,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -71,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -70,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -69,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -68,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -67,59:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -74,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,60:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -72,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -71,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -70,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -69,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -68,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -67,60:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -74,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -72,61:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -71,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -70,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -69,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -68,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -67,61:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -74,62:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,62:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -72,62:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -71,62:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -70,62:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -69,62:[8µs]
    2011.06.09 04:44:41 onChunkUnLoad -68,62:[5µs]
    2011.06.09 04:44:41 onChunkUnLoad -67,62:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -74,63:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,63:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -72,63:[4µs]
    2011.06.09 04:44:41 onChunkUnLoad -71,63:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -70,63:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -69,63:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -68,63:[4µs]
    2011.06.09 04:44:41 onChunkUnLoad -67,63:[3µs]
    2011.06.09 04:44:41 onChunkUnLoad -74,64:[2µs]
    2011.06.09 04:44:41 onChunkUnLoad -73,64:[2µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-59,62)scanned:305 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497451(-59,62)->1463552
    2011.06.09 04:44:41 [1463552- 1464189]
    [2222µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-59,63)scanned:395 ores with 1 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497463(-59,63)->1464189
    2011.06.09 04:44:41 [1464189- 1465012]
    [2197µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-60,63)scanned:337 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497475(-60,63)->1465012
    2011.06.09 04:44:41 [1465012- 1465713]
    [3058µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-61,63)scanned:251 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497487(-61,63)->1465713
    2011.06.09 04:44:41 [1465713- 1466242]
    [2492µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-61,62)scanned:298 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497499(-61,62)->1466242
    2011.06.09 04:44:41 [1466242- 1466865]
    [2846µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-61,61)scanned:317 ores with 1 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497511(-61,61)->1466865
    2011.06.09 04:44:41 [1466865- 1467532]
    [1076µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-60,61)scanned:224 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497523(-60,61)->1467532
    2011.06.09 04:44:41 [1467532- 1468007]
    [808µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-59,61)scanned:313 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497535(-59,61)->1468007
    2011.06.09 04:44:41 [1468007- 1468660]
    [1029µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-58,61)scanned:268 ores with 0 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497547(-58,61)->1468660
    2011.06.09 04:44:41 [1468660- 1469223]
    [846µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-58,62)scanned:338 ores with 10 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1497559(-58,62)->1469223
    2011.06.09 04:44:41 [1469223- 1469986]
    [954µs]
    2011.06.09 04:44:41 onChunkLoad: Load:(-58,63)scanned:236 ores with 6 exposed faces
    2011.06.09 04:44:41 Index Entry Write@1491279(2,2)->24925
    2011.06.09 04:44:41 Index Entry Write@1491291(12,12)->24052


    I had teleported to a location I had not been to since installing AXR,
    I did a series of commands , /axr chunk, /axr worlds, and /axr test MysticForest at somepoint.. the first chunk command shown 0 ores.. in file.. went to another location, and back and chunk shown the ores in memory and looked ok. Not sure witch command created the error on the console, or if TP'ing did it.





     
  21. Offline

    Donald Scott

    I am confused as to what /axr gen w2 x1 z1 x2 z2 actually does... My server crashed once and now all of the ore is gone (the backups were lost) and the gen command is not actually adding the ore back. I read the steps posted to restore the ore, but could someone explain what the aforementioned command should be doing?
     
  22. Offline

    asdaarg

    @RazMaTaz
    Ok, well this explains it. I don't know if this was the problem last time, but it is likely so. If you can find this exception in the log back then, then this is it. The reason I was confused last time was because I thought the lindex was missing, but this clearly isn't the case now, but the chunk entry itself is missing. It probably occured because the teleportation is buggy in mc/CB not loading all chunks (typically the chunk you teleported to) so when trying to expose ore in that chunk, it wont find an entry, but will try to do something with it anyway and thus result in this. I'll make a workaround for this in short.

    Edit: I just checked and yes, it was the same problem last time. Fixed in .8
     
  23. Offline

    Ancetras

    How do I set these:

    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)

    I don't understand "maxys" o_o
    Does it work with chest?
    >.<
     
  24. Offline

    Mhalkyer

    Hi Asdaarg, is there an easy way to regenerate the ores in a given chunk/radius? My players are reporting that all my ores are gone. I might have uninstalled it wrong, so I'm going to try and fix it before regenerating more ores.
     
  25. Offline

    Toni

    Just a question, this plugin is working with CB 818+ ? I'd like to try it out, but I'm a little worried.
     
  26. Offline

    The PC Tech Guy

    I think it's working for me. At least /axr off did.
     
  27. Offline

    Mhalkyer

    Looks like "/axr off" is working for me, it's slowly restoring the chunks. Can I log off and it'll continue?

    EDIT: I can't complete a restore on 47,000 "chunks" (not sure if this is mc chunks, when axr first loads it says axr only hid 600 chunks.). There's a massive amount of java null pointer exceptions and my server eventually freezes.

     
  28. Offline

    asdaarg

    You can restart the server and do /axr off again and it will gradually restore all chunks. To be on the safe side restart it before you run out of heap space.
     
  29. Offline

    Mhalkyer

    I've tried this multiple times last night and it did not work. When I would restart the "restore: 0 out of 47000" would completely restart. Needless to say I have a few comments/questions:
    1. Could you add a console command and messages for the restore process?
    2. Do you make sure a player can't do "/axr off" if the process has already been started?
    3. Do I need to change anything in the axr config file?
    4. Doesn't axr just rehide the ores when I restart the server after doing /axr off??
    5. Could you add a "resuming restoration process" message if it detects a previous restore?
    6. Once "/axr off" is finished, do you prevent someone from using "/axr off" again?
    Thanks for your help on this, I've been pulling my hair out all night.
     
  30. I don't think this plugin hides ores on different worlds. Even though it says its on. It is not on....
     
  31. Offline

    asdaarg

    The number of chunks to restore should shrink each time. The file should shrink in size after repack.
    1. No, its not as simple to add console commands and its not worth it.
    2. No; it will likely crash if you type it twice with some concurrency error.
    3. No.
    4. It will only hide loaded chunks which are usually 625 chunks around spawn and around where you are logged in.
     

Share This Page