Board Thread:Modded Server Technical Support/@comment-26276264-20170714171906/@comment-25101089-20170716203817

Alright, so from looking at that Thermos source code it seems that Cauldron patches some of the classes targeted by the LOTR coremod. Coremodding is already a horrible messy process, and trying to work around something else also changing the code at the same time will be nigh impossible to fix. I'd like to remind everyone that what I do is not waving a magic wand and fixing problems effortlessly, as it may appear, but trying to track down the very specific causes of what goes wrong, which may be completely non-obvious. One single mismatch between what code the mod expects and what it gets is enough to cause a crash, and there may be many of those.

The only 'fix' for this may well be to have the mod detect a Cauldron server, and disable all the parts of the coremod which are found to cause problems, one by one. In this instance, that means no armour protection modifiers. As more incompatibilities are found, it may mean other LOTR mod features disabled. But I have to ask, at what point does it become worth trying to run the mod on the intended, supported, fully compatible Forge server, using mods like Forge Essentials to replicate almost all the plugin features you could ever want, instead of risking unfixable crashes every time the mod adds a new feature?