I know it's easy to blame my mod for the compatibility test but ...

I have been testing this new version compatible with 1.1.0 for weeks on the nexus without any issue (in fact there was one but fixed more than a week ago) and secondly other modders on the official discord reports the same nightmare with their mod with no real reason.

So, i'll do my best to solve the issue but it looks like another sabotage from the devs as nothing works as intended.
While i'm investigating on this issue i noticed if i took my 1.0.2 save and loaded 1.1.0 even with all mod disabled i ended with a crash. I returned to 1.0.3 to do some new saves and testing, using my simple mod that simply add a new unit leads to a crash upon migrating to 1.1.0 while i could successfully make a new game with Useful Companions and had no issues pushing it to 1.1.0.


This is not easy and i'm really trying to figure what is wrong, but it looks like an issue really random, and very hard to reproduce crippling most of the mods since their sneaky update.
Because yes once again, i, like many other moders were working on a compatible version on the beta to avoid this specific issue, but Taleworld decided to throw untested content on the last day without telling anybody and without letting us test it and make changes to our mods.

I know this look like complains, but me and some other modders are really trying to make quality product (I'm not talking about those dropping a lazy mod and never updates it), and this is just a hell of a pain to work with Taleworlds. Officially they say all over the place they are helping modders, the reality is a lot different and this is an example, the worst they did so far. To my opinion they are truly looking to destroy all mods except their own future DLCs and constantly sabotage our work.

This had to be told.