Re: Bugs found in Tekkit 2.0
Got a doozy--seen it peripherally referenced on this thread but in an incomplete manner.
Managed to kill my server by right-clicking on an Equivalent Exchange energy condensor while holding a buildcraft wrench.
Throws the server for a loop--stops everything. Throws an error like so:
11:22:27 [sEVERE] java.lang.NullPointerException
11:22:27 [sEVERE] at net.minecraft.server.ItemStack.doMaterialsMatch(ItemStack.java:243)
11:22:27 [sEVERE] at ee.TileCondenser.extractItem(TileCondenser.java:539)
11:22:27 [sEVERE] at buildcraft.transport.pipes.PipeItemsWood.checkExtract(PipeItemsWood.java:111)
11:22:27 [sEVERE] at buildcraft.transport.pipes.PipeItemsWood.doWork(PipeItemsWood.java:90)
11:22:27 [sEVERE] at buildcraft.transport.TileGenericPipe.doWork(TileGenericPipe.java:159)
11:22:27 [sEVERE] at buildcraft.api.PowerProvider.update(PowerProvider.java:52)
11:22:27 [sEVERE] at buildcraft.transport.TileGenericPipe.l_(TileGenericPipe.java:108)
11:22:27 [sEVERE] at net.minecraft.server.World.tickEntities(World.java:1182)
11:22:27 [sEVERE] at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:534)
11:22:27 [sEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:441)
11:22:27 [sEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
11:22:27 [sEVERE] Unexpected exception
java.lang.NullPointerException
at net.minecraft.server.ItemStack.doMaterialsMatch(ItemStack.java:243)
at ee.TileCondenser.extractItem(TileCondenser.java:539)
at buildcraft.transport.pipes.PipeItemsWood.checkExtract(PipeItemsWood.java:111)
at buildcraft.transport.pipes.PipeItemsWood.doWork(PipeItemsWood.java:90)
at buildcraft.transport.TileGenericPipe.doWork(TileGenericPipe.java:159)
at buildcraft.api.PowerProvider.update(PowerProvider.java:52)
at buildcraft.transport.TileGenericPipe.l_(TileGenericPipe.java:108)
at net.minecraft.server.World.tickEntities(World.java:1182)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:534)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:441)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)
Repeats this error every time the chunk loads--and completely stalls/stops the server.
Afterwards, server is still "running"--it will accept commands like 'help/stop/save-all' but it supplies no chunk data to users who attempt to connect.
Client throws this error:
[17:42:27] [sEVERE] Exception in thread "main"
[17:42:27] [sEVERE] java.util.NoSuchElementException
[17:42:27] [sEVERE] at java.util.Scanner.throwFor(Scanner.java:838)
[17:42:27] [sEVERE] at java.util.Scanner.next(Scanner.java:1347)
[17:42:27] [sEVERE] at org.spoutcraft.launcher.MD5Utils.parseChecksumFile(MD5Utils.java:80)
[17:42:27] [sEVERE] at org.spoutcraft.launcher.MD5Utils.updateMD5Cache(MD5Utils.java:63)
[17:42:27] [sEVERE] at org.spoutcraft.launcher.gui.LoginForm.loadLauncherData(LoginForm.java:347)
[17:42:27] [sEVERE] at org.spoutcraft.launcher.gui.LoginForm.<init>(LoginForm.java:130)
[17:42:27] [sEVERE] at org.spoutcraft.launcher.Main.main(Main.java:177)
Server can be restarted and runs fine--until somebody gets close enough that the (now flawed(?)) chunk is loaded, and then el crasho!
Tried running Chunkster (bad, I know) to resolve it, but to no avail.
Server is running on a headless Ubuntu Server Linux box, client is running a Lubuntu Linux computer.
Both server and client are running the latest (as of today) jar (et al) downloaded from technicpack.net, running in default configuration.