This requires a bit of funkiness to ensure the main ComputerCraft class doesn't reference any Minecraft/Fabric specific code in its static initialiser. IMO it's worth doing this anyway - allows people to use the jar outside of MC (e.g. in emulators).
See #5. No gametests yet, those are more work.
This requires a bit of funkiness to ensure the main
ComputerCraft
class doesn't reference any Minecraft/Fabric specific code in its static initialiser. IMO it's worth doing this anyway - allows people to use the jar outside of MC (e.g. in emulators).