[.51] Strangness with taking cities.

First bug:

 

Walked up to a city with a stack of 6, attacked and took the city.  2 of my troops were left outside the city, each in a separate stack where I initiated teh attack from

Second:

Attacked with 2 heroes and a troop.  I took the city, but one of the heroes fell.  The one who died ended up in 2 cities(the one I just took, and the second closest city).  The hero who survived was no where at all.  About 10 turns later, he turns up in the city I took.

Finally:

Trying to take Resoln's last city, he had a monstrous stack and I basically got wiped out.  But one of his heroes basically had infinite turns when attacking my missile troops, until they died.  After killing the 3rd missile troop(the last of 'em), he then got stuck in an infinite loop and the game crashed (DX exception).  When killing the missile troops, he'd make an attack, and hit or miss, he'd get another turn added to the turn roster.  Once it was dead, he'd stop.  He had an initiate of 28, and was taking 2 turns in a row.  If he attacked something on the second of his turns, it resolved normally without creating an extra turn.

After he killed the last missile troop, he would do a casting animation, then defend for several turns, then do it again.  Each of those actions, he was gaining multiple extra turns, to the point that his turns waiting completely filled the turn roster that was displaying.

2,741 views 2 replies
Reply #1 Top

I've seen the "few troops decide to stay outside" bug after taking a city, but have yet to figure out what the hell is causing it.

Reply #2 Top

Just speculating here, but #3 might be the infinite turn "Command" bug discussed in this thread.

For #1 and #2 the developers might appreciate a saved game that they could use to recreate the problems, if you've got one.