MegaGlest Forum

Archives (read only) => Glest Advanced Engine => Bug reports => Topic started by: tomreyn on 16 April 2011, 04:07:08

Title: [Fixed] "Move Skill set, but pos == nextPos"
Post by: tomreyn on 16 April 2011, 04:07:08

I just had GAE (commit a35cf04270f36c56d4f3df6fd622e3f6745bdb9f) bail out with an error on Shibboleth:

Quote

Move Skill set, but pos == nextPos

This error is displayed on screen...

(http://freeit.org/glest/screens/gae_move-skill-set-but-pos-equals-nextpos.png)

... but it is _not_ written to any logs.

It can be reproduced by adding some opponents' units to your attack queue. In my case, I was attacking with a bunch of archers (who were not visible to the attacked units), and put two workers of the CPU player I was attacking on the archers' attack queue. As soon as they killed the first worker, this error message displayed and the game ended, bailing out to the main menu.

Title: Re: "Move Skill set, but pos == nextPos"
Post by: silnarm on 16 April 2011, 12:02:05

Thanks, there was a problem with the attack command when a specific target they had died, it was finishing the command but not setting stop skill, leaving whatever was set from the last command update. Not a problem if the command finish is followed by the usual auto generated stop command, but if there were orders on queue... problem.  All fixed up.