..Thoughts on the game, bugs and patches

[tai4ji2x]

I don't disagree that CA is responsible for the bugs. I do disagree that the siege bug was introduced with the patch. Testing suggests it has been present since 1.1, and perhaps even with 1.0, but I haven't read conclusive evidence for the status of 1.0.

I understand that leaving the machine running might not be feasible for some people, but it is simple and effective. Also, the AI does get back on track after a reload, so it's not like it's broken for good when you do need to load it.

No, I'm not saying customers should be responsible for fixing anything. What I'm saying is that we can help ourselves if we choose, rather than just waiting for these jokers to do something. I don't know about you, but I'd rather fix what can be fixed now, because I like the game and don't want to wait for October to get better gameplay. It isn't good, but it is preferable to the alternatives of not playing at all or living with the pain.

A fix for the horse archer problem was posted on this forum about a month ago. It involves changing ONE word in the unit description file for each of the affected units, and those units are listed with the fix. If you cannot find the fix in this forum, I can dig up a copy of it and post it back here, but that might take some time.

- although the siege lifting on its own may have been there all along, there is speculation that 1.2 introduced other AI-forgetfulness upon reloads.

- leaving a machine on is wasteful of electricity only half-joking, but that aside, if you're one of those who can only play 2-3 turns a night (esp. each turn gets longer on average to complete as your campaign progresses), the AI "getting back on track" is nearly impossible.

- if you can even get connected online anymore, the horse archer fix won't work there.