Author Topic: [Fixed] "Move Skill set, but pos == nextPos"  (Read 760 times)

tomreyn

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
[Fixed] "Move Skill set, but pos == nextPos"
« 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...



... 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.
« Last Edit: 16 April 2011, 12:02:29 by silnarm »
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

silnarm

  • Local Moderator
  • Behemoth
  • ********
  • Posts: 1,373
    • View Profile
Re: "Move Skill set, but pos == nextPos"
« Reply #1 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.
Glest Advanced Engine - Code Monkey

Timeline | Downloads