COMMUNITY CALL TO POWER v4.05 Play-testing Release

Hey, sorry to hear that you`re encountering CTD`s. I played the latest released version time ago and didn`t encountered any hard crash (only using CCTP and IGE, and with Oder disabled). Anyway i can look at the logs and maybe i can figure out what is causing the issue.

About Enchantuer, critism is fine, its a good way to keep things going, but sometimes you spend that much time to create something, and then somebody is comming and is telling you his opinion, and this can be very frustrating. I spent so much time to create the techtree, to balance it etc (you would be surprised how tricky and complex the techtree is), that any mayor change would mean i need to waste countless hours. And to be honest, iam not going to redo such features, iam willing to overwork and balance several aspects of the mod. But to start over and creating some basic features again, would be a mess and i don`t have the time for it.

Anyway one reason why its so quit here, is the fact that my PC crashed my latest master version, and i was to ****ed up, to redo the work.

 

I wouldn't be surprised if its one of the other mods I have, even if they're minor, since this is such a large overhaul. I actually started learning to code just this past year (relatively fluent in java at this point, and know some LWJGL for it. Am also planning on looking into C++), so I can't even imagine how much dedication you have to have stuck with this for so long. Anyway, which logs would you like me to send your way?

 

Hm after looking quickly at the Lua log it seems the issue occurred in TopPanel.lua on line 272 attempt to call global 'GetCityOrder' (a nil value) I'm assuming this is similar to a NullPointerException in Java. What fascinates me the most about this error is I have Order disabled.

 

Wait, it seems that this error has been occurring throughout the entire playthrough. Does it print the error to the console/log even if it's been caught with a try/catch? I'm guessing that for some reason at some point the error couldn't be handled properly for some reason.