Thermos, a replacement for KCauldron due to KCauldron's inactivity, has launched: https://github.com/TCPR/Thermo…accc06caed2b6c2d0f879c5ee
FastCraft is no longer compatible: https://gist.github.com/ajthemacboy/b1a839454dd62269dc91
Don't know what to say about this really; the devs of KCauldron and Thermos say FastCraft offers no performance improvement, but my own tests say it does.
If you're willing to support Thermos I couldn't be happier, but if not I understand that this is a nightmare!
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..
So that's why Factorization is broken... I love FZ but the packet kicks were just obnoxious so we had to remove it.
Sadly, using vanilla Forge just isn't an option for my server. If SpongeForge and Pore were to backport to 1.7.10, I'd use those in a heartbeat.
But my server really needs blocklogging with the Prism plugin, and my players would be upset without /home and /tpa commands.
KCauldron broke more and more each update, and Thermos is at least a little more stable than KCauldron. I'd be using Cauldron still if it was updated to later versions of Forge.
Got a crash using fastcraft-1.22-ctest22.jar.
Was connecting to a dedicated server running the same version, immediately after updating both from ctest21.
The actual crash begins on line 8179 and appears to be an issue with Thermal Dynamics server when it is accessing a neighboring block that has changed states.
Will try rolling back FastCraft version.
Edit: Changing client back to ctest21 fixes the issue or at least allows me to play without crashing.
Hallo,player I would like to inform you that I am using your MOD Fastcraft for our private mod pack
Hello, player.
I would like to inform you that we are using your mod Fastcraft for our private mod pack
Derpcraft mod Team
Hello, got a crash using 1.22-ctest23.
fml log: https://gist.github.com/Keyarose/2fabc69d32f758f0b05c
The crash happens aprox 75% of the time when using a Mystcraft linking book. I think it might be related to the LookingGlass mod used to show the link in location. It throws a number of ArrayIndexOutOfBoundsException before the crash.
LookingGlass 0.2.0.00
Mystcraft 0.12.3.01
Display MoreHello, got a crash using 1.22-ctest23.
fml log: https://gist.github.com/Keyarose/2fabc69d32f758f0b05c
The crash happens aprox 75% of the time when using a Mystcraft linking book. I think it might be related to the LookingGlass mod used to show the link in location. It throws a number of ArrayIndexOutOfBoundsException before the crash.
LookingGlass 0.2.0.00
Mystcraft 0.12.3.01
Can you post the crash report instead of the log?
I've had a lot of bad experiences with MystCraft, mainly Pahimar refusing to fix major bugs and performance issues. Hopefully this isn't a bug with MystCraft or you may be out of luck 
Received the following "faulty access detected" crash using fastcraft-1.22-ctest23: http://pastebin.com/enkG0YiP
ajthemacboy: Here's the crash skimmed out of the log: https://gist.github.com/Keyarose/51d3367f6ab846099691
Player: Thanks, hopefully it won't be too difficult.
Using this mod in my modpack, Infinitech. Thanks so much for making this! 
Partial Crash Log - https://gist.github.com/DPxKnightxZero/44e7bfcf6ebf946e0ac5
Full Crash Log - https://gist.github.com/DPxKnightxZero/2ed275b267380e68f5ef
Using test 23 - Crash after about a few seconds. 
"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.
Any way you could talk to team Aether II? They are the creators of the mod.
https://github.com/gildedgames/aether-issues/issues/624
You should keep such debugging tools and maybe even improve on info provided.
Issue with mod unsure of cause ; possible issue with micdoodle core
https://gist.github.com/DPxKnightxZero/27fa99a6daee84b4fa45
Server keeps freezing.
Okay no it has nothing to do with that. Using latest fastcraft test 23
Dynamic lights was the issue of crash!
