Hexical Interop crashes game

[Mansarde]

When using the latest official release of Hexical (v1.5.0) with Hex Debug v0.6.0 or v0.7.0, then as soon as you try to close the GUI of the splicing table the game crashes.

This seems due to the Hexical Interop that was introduced in Hex Debug v0.6.0.
Hex Debub is trying to access the OPEN_HEXBOOK field of Hexical, which unfortunately is a private field in v1.5.0

Exception

java.lang.IllegalAccessError: class gay.object.hexdebug.fabric.interop.FabricHexDebugHexicalInterop tried to access private field miyucomics.hexical.inits.HexicalKeybinds.OPEN_HEXBOOK (gay.object.hexdebug.fabric.interop.FabricHexDebugHexicalInterop and miyucomics.hexical.inits.HexicalKeybinds are in unnamed module of loader 'knot' @685cb137)
	at knot//gay.object.hexdebug.fabric.interop.FabricHexDebugHexicalInterop.sendKeyEvent(FabricHexDebugHexicalInterop.kt:21)
	at knot//gay.object.hexdebug.fabric.HexDebugClientAbstractionsImpl.sendHexicalKeyEvent(HexDebugClientAbstractionsImpl.kt:11)
	at knot//gay.object.hexdebug.HexDebugClientAbstractions.sendHexicalKeyEvent(HexDebugClientAbstractions.java)
	at knot//gay.object.hexdebug.gui.splicing.SplicingTableScreen.method_25404(SplicingTableScreen.java:550)
	at knot//net.minecraft.class_309.method_1454(class_309.java:395)
	at knot//net.minecraft.class_437.method_25412(class_437.java:409)
	at knot//net.minecraft.class_309.method_1466(class_309.java:391)
	at knot//net.minecraft.class_309.method_22678(class_309.java:477)
	at knot//net.minecraft.class_1255.execute(class_1255.java:102)
	at knot//net.minecraft.class_309.method_22676(class_309.java:477)
	at knot//org.lwjgl.glfw.GLFWKeyCallbackI.callback(GLFWKeyCallbackI.java:44)
	at knot//org.lwjgl.system.JNI.invokeV(Native Method)
	at knot//org.lwjgl.glfw.GLFW.glfwWaitEventsTimeout(GLFW.java:3474)
	at knot//com.mojang.blaze3d.systems.RenderSystem.limitDisplayFPS(RenderSystem.java:237)
	at knot//net.minecraft.class_310.method_1523(class_310.java:1244)
	at knot//net.minecraft.class_310.method_1514(class_310.java:802)
	at knot//net.minecraft.client.main.Main.main(Main.java:250)
	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:506)
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:72)
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
	at org.prismlauncher.launcher.impl.StandardLauncher.launch(StandardLauncher.java:105)
	at org.prismlauncher.EntryPoint.listen(EntryPoint.java:129)
	at org.prismlauncher.EntryPoint.main(EntryPoint.java:70)

[object-Object]

Hmm. The Hexical interop is meant to work with Hexical 2.0.0. I'll see if I can make it prevent earlier versions from being used.

[Mansarde]

Hmm. The Hexical interop is meant to work with Hexical 2.0.0. I'll see if I can make it prevent earlier versions from being used.

Thanks, much appreciated! 🙂🍻

[object-Object]

The next release of HexDebug will log this message on startup if Hexical<2.0.0 is detected:

And this message (instead of crashing) the first time you try to use the Hexical interop in a splicing table:

Thanks for the report ^^

[object-Object]

Also, as a workaround until the fix is released, you should be able to avoid the crash by disabling the splicingTableKeybinds.sendHexicalTelepathy option in HexDebug's client config.

[Mansarde]

Also, as a workaround until the fix is released, you should be able to avoid the crash by disabling the splicingTableKeybinds.sendHexicalTelepathy option in HexDebug's client config.

Ah ok , I downgraded to 0.5.0, but I'll definitely do this then so I can use the new version.
Thx for taking the time! ✌️