Skip to content

Self Contained Crashes

Jump to bottom
Danny edited this page Apr 2, 2021 · 6 revisions

If an exception is thrown while interacting with a Redstone Panel, when it's responding to a neighbor change or during its tick process, instead of crashing the game, the Redstone Panel will disabled itself. While I hope no one ever has to experience this, it is much better than a game crash.

When disabled, a Redstone Panel will turn red, and its components will become dark and translucent.

You can remove components from a disabled panel. With any other interaction, it will present a dialog stating that it has crashed.

Clicking "Enable" will "reboot" the panel. If the issue that caused the crash hasn't been fixed, it's possible that it will crash again.

Details about the crash will be written to the Minecraft log file. It would be very much appreciated if you could copy these details and include them in an issue. It may look something like this:

[01Apr2021 22:29:08.092] [Server thread/ERROR] [com.dannyandson.tinyredstone.TinyRedstone/]: Redstone Panel Crashed at 93,64,-23
java.lang.Exception: Test Exception
	at com.dannyandson.tinyredstone.blocks.PanelBlock.onBlockActivated(PanelBlock.java:341) ~[?:?]
	at net.minecraft.block.AbstractBlock$AbstractBlockState.onBlockActivated(AbstractBlock.java:730) ~[forge:?]
	at net.minecraft.server.management.PlayerInteractionManager.func_219441_a(PlayerInteractionManager.java:347) ~[forge:?]
....
Clone this wiki locally