Context
I am running a dedicated NeoForge 1.21.1 server with Sable (1.2.2) and Twilight Forest (4.8.3345).
The server crashes with java.lang.IllegalStateException: Recursive update when processing a chunk containing a Twilight Forest "ForceFieldBlock"
-
"RapierVoxelColliderBakery.getPhysicsDataForBlock" calls "BlockStateBase.getCollisionShape()"
-
"ForceFieldBlock.getShape()" calls "fullFaceOrSimilarForceField()" which uses "LevelAccelerator.getBlockState()" (from Sable)
-
This creates a recursive loop and causes "ConcurrentHashMap.computeIfAbsent" to throw "IllegalStateException"
-
Minecraft: 1.21.1
-
NeoForge: 21.1.228
-
Sable: 1.2.2
-
Twilight Forest: 4.8.3345
-
Other relevant mods: Create Aeronautics, Simulated
Is there a way to add specific blocks (like "twilightforest:force_field") to a blacklist or configuration so that Sable does not try to calculate collision physics for them?
I would like to keep both mods enabled but disable Sable's physics processing for incompatible blocks. If such a config option does not currently exist, would it be possible to add one?
The crash occurs when the chunk is ticking (during "postProcessGeneration" / "prepareTickingChunk")
Crash Report
https://mclo.gs/aOWTEMq
Context
I am running a dedicated NeoForge 1.21.1 server with Sable (1.2.2) and Twilight Forest (4.8.3345).
The server crashes with
java.lang.IllegalStateException: Recursive updatewhen processing a chunk containing a Twilight Forest "ForceFieldBlock""RapierVoxelColliderBakery.getPhysicsDataForBlock" calls "BlockStateBase.getCollisionShape()"
"ForceFieldBlock.getShape()" calls "fullFaceOrSimilarForceField()" which uses "LevelAccelerator.getBlockState()" (from Sable)
This creates a recursive loop and causes "ConcurrentHashMap.computeIfAbsent" to throw "IllegalStateException"
Minecraft: 1.21.1
NeoForge: 21.1.228
Sable: 1.2.2
Twilight Forest: 4.8.3345
Other relevant mods: Create Aeronautics, Simulated
Is there a way to add specific blocks (like "twilightforest:force_field") to a blacklist or configuration so that Sable does not try to calculate collision physics for them?
I would like to keep both mods enabled but disable Sable's physics processing for incompatible blocks. If such a config option does not currently exist, would it be possible to add one?
The crash occurs when the chunk is ticking (during "postProcessGeneration" / "prepareTickingChunk")
Crash Report
https://mclo.gs/aOWTEMq