Ghost Ranger
Prince
- Joined
- Jul 27, 2007
- Messages
- 357
AI/ automated workers don't seem to take the 'commando' promotion into account when choosing where to move. (patch d)
This issue has been reported a several thousand times ago.
Patch 0.41e (unreleased, will break save games)
Patch 0.41d
1. Fixed a crash when starting as a civ with a unique race (fix provided by Xienwolf before the issue was reported, now thats skill!).
Happen to me as well, but then I checked the log which says that the Sheaim had cast worldbreak. I think Worldbreak is supposed to destroy wonders as well; hey, after all it's hell breaking loose here.Two bugs, one relatively major, one pretty minor.
Bug 1
When the AC hit 50(?) and Buboes came into the game, I also got the message that several of my units had been damaged by fire damage. (Don't know if that was from the AC or maybe somebody's world spell (Worldbreak, maybe?).)
Anyway, the bug is that my Tower of Divination got destroyed and I had to rebuild it. I don't think that there's either any AC level or any world spell that destroys national wonders, is there?
2. I waged War against Alexis. When she suddenly became Vassal to Perpentarch, Perpentarch suddenly was at war with me too - without any declaration, dialog option or something. If i had not the score-list on top when i play, i would not even have known.
Does becoming a Vassal not usually end wars first?
No, thats the normal BtS vanilla action, the war ends only if you and Perpentach are at war Alexis, like that they were in peace and she sought protection from him, therefor the war declaration after she became his vassal
1. I frequently had the case in Single Player games: When a civ i am at war with becomes a vassal, the war ends. You can continue the war, but that triggers a warning dialogue option. (besides, i haven't palyed BtS-Vanilla for years )
2. Even if you were right, the problem is: There was no declaration of war, that game just switched from peace with perpentarch to war with perpentarch.
[to_xp]Gekko;8247689 said:it is highly possible that the good ol' bug that makes blight hit human players TWICE has reared its ugly head yet again.