Posts by Player
-
-
-
-
-
-
-
-
-
-
-
-
"com.gildedgames.util.threadedlighting.world.ThreadedWorld" is the problem, remove the mod. Moving the lighting calculations to a thread isn't safely doable as it involves global state modifications and running arbitrary code on some mod blocks. Doing it regardless will cause sporadic crashes and corruption. FC detects one case of those invalid global state modifications since ctest22 for debugging purposes, the final versions won't have this by default.
-
-
The issue was on my side, new build at http://files.player.to/tmp/fastcraft-1.22-ctest23.jar
-
That's actually not a FC-specific incompatibility, the missing/mistyped field is public in Forge as well. I've added a workaround for the next build.
Overall I'm not impressed with Thermos and later KCauldron changes, there's way too many unsafe additions that barely work in vanilla, let alone modded mc. Deliberately breaking mods as in https://github.com/TCPR/Thermo…95596aa79dde996457a05177e and questionable performance "improvements" all over the place. Changes like introducing ConcurrentHashMap avoid concurrent modification exceptions, but don't help with getting an actually consistent world state and perform significantly worse for non-threaded access..
-
Yes, unintentional
911.443776815..
-
64 ITNT and 64 Pu yield an explosion power of 911, which is equivalent to a radius of 1822 air blocks.
-
I've uploaded another test build at http://files.player.to/tmp/fastcraft-1.22-ctest22.jar
It adds extra logging for SvEgiiVEteR's issue and tracking for P3rf3ct_Zer0's, both most likely caused by misbehaving mods. Please evaluate them
-
Note that the explosion power is capped for performance reasons, you'll have to edit the config to see more effect
-