search

eisental / RedstoneChips

A Bukkit plugin for digital redstone integrated circuits
eisental.github.com/RedstoneChips
GNU General Public License v3.0
22 stars 15 forks source link

Exception in RCBukkitEventHandler #61

Open jaysan1292 opened 12 years ago

jaysan1292 commented 12 years ago

I was editing the .mem file for a sram chip and did /rcload, which then gave me this:

2012-05-25 04:00:06 [SEVERE] Could not pass event BlockPhysicsEvent to RedstoneChips org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:303) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.TimedRegisteredListener.callEvent(TimedRegisteredListener.java:30) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:459) at net.minecraft.server.World.k(World.java:510) at net.minecraft.server.World.applyPhysics(World.java:496) at net.minecraft.server.BlockRedstoneTorch.onPlace(BlockRedstoneTorch.java:55) at net.minecraft.server.Chunk.a(Chunk.java:417) at net.minecraft.server.World.setRawTypeIdAndData(World.java:344) at org.bukkit.craftbukkit.block.CraftBlock.setTypeIdAndData(CraftBlock.java:107) at org.tal.redstonechips.RCBukkitEventHandler.onBlockPhysics(RCBukkitEventHandler.java:117) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601)

It loops forever until I kill the server.

EDIT: It seems it was a mistake on my part; I had a syntax error in the .mem file. There really should be some sort of exception handling for this though.

EDIT 2: No, that wasn't it. /rcload still seems to throw that same exception.

eisental commented 12 years ago

Isn't there any more information in the looping error? It looks like an infinite redstone loop caused by some redstone torch but I would need more info to see what's going on.

jaysan1292 commented 12 years ago

I'm not really sure what else I can do to help, but I've attached a link to the server log: http://dl.dropbox.com/u/3225986/truncated-server.log

(on a side note, it boggles my mind as to how it generated nearly 10MB of output in the five seconds it took for me to kill the server)