Mod crashes for no apparent reason

I'm currently developing another mod and I was playtesting it, but it crashes in 30 AD while "Waiting for other civilizations". I can't seem to solve it but I know it's not this
-Not a missing graphic issue
-Not a DLL issue
-Not a Python issue
So what could it be? I rather not upload the whole mod as it will spoil what it is and it is quite large. I'm in quite a predicament, as I can't find any reason why this happens.

 

could it be a unit's nif file that doesn't work right? one of my units, the modern christian preacher, used to cause the game to crash because the nif file had a problem with the cross that i added and when i fixed that, everything was working fine.

 

I don't think so, I think it might be the absence of a Great General unit in the XML file, because two civs are waging a war in my playtest game.

 

from my experience, when a normal unit is missing, the game appears in it's place a red hemisphere but i'm not sure what happens when a a great person unit is missing because it has never happened to me before.
maybe, if it's not a "broken" nif, there is an xml entry that is pointing somewhere that it shouldn't?

 

Try to turn on python expections.
Also, i thing not having a gg unit might be bad for the game, not sure.

 

Some general advice when crashes happens without any indication to what went wrong:

1. enable python exceptions
2. use a DLL with asserts enabled
3. use a debugger to identify the line where it went wrong

The first one should be doable for everybody. #2 requires a compiler while #3 requires a compiler and human skills to understand what turns up on the screen. Sadly the higher the number, the better it is for pinpointing the problem.

It may come as a surprise that I'm targeting the DLL even though you didn't touch it, but it is possible to set xml in a way, which will make the DLL crash. It actually has warnings when something goes wrong (most of the time), but it uses the assert system to check and display those warnings, meaning using the regular release DLL will disable those warnings.

What I think would be best would be for you to place your mod in git. The benefits it would provide would be to provide a copy to everybody, meaning if you upload your savegame, other people can test it. Also the compile server can provide DLL files for you, fixing the problem that you do not have the assert DLL. There are other benefits to using git as well, like easy merging of modcomps.

The only problem with the git approach is that I haven't written the get started guide yet

 

Sometimes I wonder why people rather ask and wait rather than test it themselves.
If you suspect GG is the problem, all it takes is to start a new game, go to WB and put 2 stacks of opposing units side by side.
Keep whacking till GG is supposed to be born and you get your answer in less than 3 mins.

 

I already solved it, just didn't post it here.