NuclearCraft

NuclearCraft

34M Downloads

Crash when inserting Depleted Cell

GrazzMan opened this issue ยท 6 comments

commented

Accidentally added Depleted LEU-235 to Fission Reactor. Crashed Server completely. Had to edit and remove block in MCEdit to get server to start again. Using Ver 1.9c in MC 1.7.10
crash-2016-10-05_18.34.40-server.txt

Time: 10/5/16 6:34 PM
Description: Ticking block entity

java.lang.ArrayIndexOutOfBoundsException: -1
at nc.tile.generator.TileFissionReactor.doesFuelMatchDepleted(TileFissionReactor.java:668)
at nc.tile.generator.TileFissionReactor.fuel(TileFissionReactor.java:679)
at nc.tile.generator.TileFissionReactor.func_145845_h(TileFissionReactor.java:115)
at net.minecraft.world.World.func_72939_s(World.java:1939)
at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:489)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:636)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:334)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:396)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)

A detailed walkthrough of the error, its code path and all known details is as follows:

-- Head --
Stacktrace:
at nc.tile.generator.TileFissionReactor.doesFuelMatchDepleted(TileFissionReactor.java:668)
at nc.tile.generator.TileFissionReactor.fuel(TileFissionReactor.java:679)
at nc.tile.generator.TileFissionReactor.func_145845_h(TileFissionReactor.java:115)
at net.minecraft.world.World.func_72939_s(World.java:1939)

commented

It was a ME export bus with depleted as the filter. Not at my system for a few days, but was ME driven.

commented

Well, that seems strange, considering that I can't even export depleted cells (or any non-valid item, in fact) to the controller. Perhaps the issue is fixed in 1.9d?

commented

I'm finally on the case :)

commented

Actually, I can't recreate this... can you either recreate this or remember how this happened?

commented

Ok, I understand the issue now - I will get it fixed in the final 1.7.10 version