This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What is the problem?Every time we try a major rollback involving p:environment it gets stuck on attempting to rollback and another rollback can not proceed.I also get an error on console
What steps will reproduce the problem?1. Try to /hawk rollback or /hawk preview with p:environment and something like r:52. e.g. /hawk rollback r:5 p:environment3.
What version of HawkEye are you using (shown in console during start-up)?1.0.5
Show me any console errors and/or your start-up console message for HawkEyeThere is no startup error other than auto update not working which i have disabled2011-10-01 17:43:13 [WARNING] Task of 'HawkEye' generated an exceptionjava.lang.NumberFormatException: For input string: "2-11" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at uk.co.oliwali.HawkEye.util.BlockUtil.getDataFromString(BlockUtil.java:98) at uk.co.oliwali.HawkEye.entry.BlockEntry.rollbackPlayer(BlockEntry.java:40) at uk.co.oliwali.HawkEye.Rollback.run(Rollback.java:95) at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:137) at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:439) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:374) at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)
Show me your config.yml and/or your config.php (REMOVE YOUR PASSWORD)
block-filter:- 97- 98log: lava-bucket: true painting-place: true other: true pvp-death: true block-fade: true chat: true quit: true sign-place: true painting-break: true lava-flow: true flint-steel: true button: true command: true block-form: true teleport: true lever: true item-drop: true water-bucket: true block-burn: true sign-break: true block-break: true leaf-decay: true water-flow: true join: true door-interact: true block-place: true open-container: true item-pickup: true explosion: true container-transaction: true mob-death: true other-death: true enderman-pickup: true enderman-place: truegeneral: check-for-updates: false max-lines: 0 tool-block: '17' log-item-drops-on-death: false cleanse-age: '0' default-tool-command: '' delete-data-on-rollback: false cleanse-period: 20m log-ip-addresses: true debug: false max-radius: 0 default-here-radius: 5mysql: hawkeye-table: hawkeye port: 3306 player-table: hawk_players username: ******************* world-table: hawk_worlds hostname: localhost max-connections: 10 password: **************************************** database: minecraftversion: 1.0.5command-filter:- /login- /restartsrv- /register
Have you checked the FAQ page?yes
I have the same problem, but after any rollback, regardless of size or player.
Same problem here, pretty much keeping us from rollbacking after a griefer came by.
EDIT: I have had to stop using HawkEye due to this..
Did this just get ignored, i will soon stop using hawkeye because of this if it continues
I don't know why it only happens to a few people. I can't even replicate the bug :\
I tried reproducing this on our server, but was also unable to get that message with any command containing p:Environment. A few things you can check on:
Have you attempted renaming your HawkEye tables and allowing the plugin to generate new ones, then causing a few Environment changes in-game and testing it with a fresh database? There may be database corruption causing issues for some.
I see you do have enderman-place enabled, which does cause console errors, and does get logged as p:Environment. Just a complete shot in the dark here, but could that be causing issues when enderman-place is set to true and you use p:Environment as an argument?
Also, it doesn't state which version of CraftBukkit you're running anywhere in the post; are you sure you're using the correct version of HawkEye corresponding to the version of CraftBukkit you're running? Remember, there are two versions of 1.0.5, re-download and replace your HawkEye.jar if you're unsure!
To post a comment, please login or register a new account.