August 18th, 2008, 11:45 PM
|
Second Lieutenant
|
|
Join Date: Sep 2007
Posts: 525
Thanks: 17
Thanked 17 Times in 10 Posts
|
|
Re: Darwin's Zorro: The Battle For Antilarium-started
Quote:
Originally Posted by CyborgMoses
Quote:
Originally Posted by Dragar
gah, what a mess! In future lets please pause the game as soon as there is an error until we decide what to do
|
This is what has happened; no turns have been processed since the one in question.
konming: since I don't know how much you know about software bugs, I am going to make some suggestions which may seem obvious. Please don't be offended.
There is something which causes this bug to manifest or not manifest. Since we don't know what causes the problem but suspect that your input may have something to do with it, and we know that your current input results in the bug showing up, one way to try to keep it from showing up again is to change your input as much as possible. I would suggest reorganizing all troops in this province, both in the makeup of units and in which commanders those units are assigned to. If you have a unit of seven spearmen assigned to a sage named Steve, maybe one of those elements is one of the things which can make the bug show up; take a guy from another unit and add it to the spearmen, and pass them off to some other commander. If you have a commander moving who you don't actually need, try having him do something else; maybe the particular combination of commanders and orders makes the bug manifest. Even seemingly unrelated things, such as which mages in your other provinces are researching and which ones are casting spells or forging, should be switched up where possible. I hope that this is helpful.
PS: On the bright side, at least this affected your entire army. Several times in single-player, I've had the movement bug cancel my orders for some, but not all, of my commanders, leading half of my army to be slaughtered when their comrades didn't show up to the battle.
|
Great advice. I suspect it has to do with mixed movement types, but we will see.
|