1.5.0: Ender Quarry Fatal Error Client Crash


New Member
Jul 29, 2019

What is the bug:
When an ender quarry is placed and the chunk it is working on is visible, the client is disconnected from the server with a fatal error. This happens until the player is moved, or the ender quarry can be quickly destroyed right after joining. Usually a quick console command to teleport player to spawn has been the easiest solution.

This does not occur in single player worlds, only on servers.

Mod & Version:
ExtraUtilites 1.2.9

Paste.feed-the-beast.com log:

Can it be repeated:

Known Fix:
I updated my server and my client to the latest version (1.2.10) of the ExtraUtilities mod and it no longer happens. I can also right click the ender quarry to see what is going on with it again. This function was not working in previous version.


New Member
Jul 29, 2019
Sure thing. I have included my entire client and server logs, the error occurred at 8:56:26 in the client log. This time it happened when I right clicked the quarry because it was done, looks like same error though.
Client Log: http://pastebin.com/Nc6RfUH8

The time is off on the server, the relevant entry is at, 09:11:55 or line 13063. My host has told me they will fix the time in the next maintenance window... whenever that is lol.
Server Log: http://pastebin.com/D2W5Armm
Last edited:


New Member
Jul 29, 2019
at first:
[08:18:06] [Client thread/WARN] [MachineMuse]: Loading shaders failed!
at net.machinemuse.powersuits.common.ClientProxy.registerRenderers(CommonProxy.scala:74)
at net.machinemuse.powersuits.common.ModularPowersuits$.load(ModularPowersuits.scala:59)
at second:
java.lang.IndexOutOfBoundsException: readerIndex(6) + length(17997) exceeds writerIndex(10): SlicedByteBuf(ridx: 6, widx: 10, cap: 10/10, unwrapped: UnpooledHeapByteBuf(ridx: 1, widx: 11, cap: 11/11))
at io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1160)
at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:668)

and main on client side:
[09:04:12] [Client thread/INFO]: [CHAT] * JiFMike is now AFK.
[09:07:35] [Client thread/INFO]: [CHAT] [CONSOLE: Enabled level saving..]
[09:07:35] [Client thread/INFO]: [CHAT] [CONSOLE: Forcing save..]
[09:07:36] [Client thread/INFO]: [CHAT] [CONSOLE: Save complete.]
[09:10:21] [Client thread/INFO]: [CHAT] [CONSOLE: Forcing save..]
[09:10:22] [Client thread/INFO]: [CHAT] [CONSOLE: Save complete.]
[09:10:22] [Client thread/INFO]: [CHAT] [CONSOLE: Stopping the server..]
And I dont see error at "8:56:26"
[08:56:24] [Client thread/INFO] [journeymap]: Mapping started in C:\Users\mlard\Documents\FTB\direwolf20_17\minecraft\journeymap\data\mp\Websound_38f0e767~9471~4a90~8714~903074f8ae45\DIM0. Memory: 4394MB total, 1636MB free
[08:56:27] [Client thread/INFO] [INpureCullingEngine]: Starting NEI Filter scripting. This might take a moment to load all the modules...

[09:11:02] [Server thread/INFO]: [org.bukkit.craftbukkit.v1_7_R4.command.CraftConsoleCommandSender]: CONSOLE: Enabled level saving..
[09:11:02] [Server thread/INFO]: [org.bukkit.craftbukkit.v1_7_R4.command.CraftConsoleCommandSender]: CONSOLE: Forcing save..
[09:11:03] [Server thread/WARN]: net.minecraft.world.MinecraftException: The save folder for world ./world/DIM-7 is being accessed from another location, aborting
I see this several times

and I think U have some problems with div-7
[09:23:50] [Server thread/INFO]: [org.bukkit.craftbukkit.v1_7_R4.command.CraftConsoleCommandSender]: CONSOLE: Forcing save..
[09:23:50] [Server thread/WARN]: net.minecraft.world.MinecraftException: The save folder for world ./world/DIM-7 is being accessed from another location, aborting
[09:23:50] [Server thread/WARN]: at net.minecraft.world.storage.SaveHandler.func_75762_c(SaveHandler.java:99)
[09:23:50] [Server thread/WARN]: at net.minecraft.world.World.func_72906_B(World.java:4241)
[09:23:50] [Server thread/WARN]: at net.minecraft.world.WorldServer.func_73042_a(WorldServer.java:1078)
[09:23:50] [Server thread/WARN]: at net.minecraft.world.WorldServer.func_73044_a(WorldServer.java:1044)
[09:23:50] [Server thread/WARN]: at org.bukkit.craftbukkit.v1_7_R4.CraftWorld.save(CraftWorld.java:796)
[09:23:50] [Server thread/WARN]: at org.bukkit.command.defaults.SaveCommand.execute(SaveCommand.java:30)
[09:23:50] [Server thread/WARN]: at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:181)
[09:23:50] [Server thread/WARN]: at org.bukkit.craftbukkit.v1_7_R4.CraftServer.dispatchCommand(CraftServer.java:717)
[09:23:50] [Server thread/WARN]: at org.bukkit.craftbukkit.v1_7_R4.CraftServer.dispatchServerCommand(CraftServer.java:697)
[09:23:50] [Server thread/WARN]: at net.minecraft.server.dedicated.DedicatedServer.func_71333_ah(DedicatedServer.java:473)
[09:23:50] [Server thread/WARN]: at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:432)
[09:23:50] [Server thread/WARN]: at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:809)
[09:23:50] [Server thread/WARN]: at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:669)
[09:23:50] [Server thread/WARN]: at java.lang.Thread.run(Thread.java:744)
[09:23:50] [Server thread/INFO]: [org.bukkit.craftbukkit.v1_7_R4.command.CraftConsoleCommandSender]: CONSOLE: Save complete.
[09:23:50] [Server thread/INFO]: [org.bukkit.craftbukkit.v1_7_R4.command.CraftConsoleCommandSender]: CONSOLE: Stopping the server..


New Member
Jul 29, 2019
I'm sorry, the error was at 8:58:26, I must have misread the time.

1) The shaders aren't loading because I have the shader mod loaded, but no shader selected. I only use shaders for screen shots. My laptop can run them, but only at like 12 fps lol, so I leave them off for actual play.

The rest I'm not sure what all that is, looks like fairly normal log entries to me.

I have seen the error about DIM7, which is the twilight forest. Since we haven't really ventured there yet I have no reports of problems.

I feel I should point out this error happens to everyone if they go into sn area where an enderquarry is working. Not just me. Plus, if I update the ExtraUtils mod on the server and on my pc, this problem goes away. It was reported by others, and is fixed in the latest version. I'm not looking for a fix to this problem, one has already been found. My intent was to simply report the bug, so the fix will hopefully be included in the next modpack release.