Thunderbrd
C2C War Dog
I suppose the AI research determinations aren't taking the Limited Religion/Divine Prophet combination in mind.Playing latest version of C2C (perfect world, immense, eons, limited religions on, divine prophets on) i notice AGAIN bug/flaw in AI behavior that is in game for a few months at least: Wilhelmina is another top civ on my continent and she tries to research EVERY religion tech, falling bad behind me. And she did not start any religion yet ... She researches Jainism now, i research Drama.
Otherwise new C2C is very sweet. Keep up good work guys, i cant wait to see new engine without vewport limits to play my favourite big maps.
On one hand (the research determination side) she thinks she is desperate to get a religion. On the other hand, (the Divine Prophets/Limited Religions) side, she knows she can only get one religion and is holding out for her favorite since nobody has taken it yet.
Provided the Prophet awards from DP on those techs aren't captured yet, its not bad for her to be trying to get them, but if they have been, and she's just behind the curve, she should be taught to avoid those techs until her favorite religion has been taken from her and she needs one she bypassed earlier that hasn't been taken yet.
This flaw in her behavior would be delaying her ability to reach her favorite religion in time to take it from others so it is something that should eventually be addressed, but will not be easily fixed (nor soon) as its a fairly complex added evaluation consideration for her research path decisions.
I don't know all that much about how leaders are evaluating religious techs under the Limited Religion option in the first place... I'd think it would make a very big difference to what they should do there and I don't know how much of it has been taken into consideration for them there in general.
Good to have pointed it out though!
It just means there's a memory corruption that has trampled on the memory for that vector. Most likely something is indexing out-of-bounds in some array, but there's no real way to know what from this - it whatever happened to be allocated next to the vector at the time which could be anything essentially. Any changes to use of a (heap allocated) array recently would be the likely culprit.
hmm... so it really could be a wide variety of possibilities there. It was happening after a particular revision so as soon as we have it established EXACTLY what revision that is it'll be pretty easily found I think. Thanks for the feedback Koshling!