AGEOD Forums

I have found that it's possible to have a unit stack appear in the wrong region after you have manipulated it in the unit info box at the bottom. The exact methodology is unclear, but this is what I think I did:

1) Select a region where there are more than one force.
2) Select one of the forces.
3) Move the map a bit by scrolling.
4) Drag the force's tab to another tab. Here's where it's weird: it seems that it's possible to either "miss" the other tab and the unit ends up on the map where you dropped it, which could be another region. It might also be when the two stacks can't be combined.

The result is the unit appears on the map in the wrong location, but is still actually located in the proper spot. In the above example, if the unit I was selecting was in Montgomery, PA, and through my fiddling with it appeared to be in Alexandria, VA, if I deselected the unit than clicked on it's counter in Alexandria, it would still say "Montgomery, PA" as its' location. It would not say "en route to Alexandria".

HOpe this is clear. I'll try to repeat it more consistently. It's happened to me a few times, so I suspect others have seen it.

Hi Crimguy!

[...]The result is the unit appears on the map in the wrong location, but is still actually located in the proper spot.[...]

The error occurs if you take a unit and drop it on it's own tab of the unit panel. I think this error was brought to Pocus' attention, so I am sure a fix is imminent.

The units appearing in different regions happens to me a lot also. Sometimes if you just click on a stack it will move a region or two visually but still physically (by way of tool tips) be correctly positioned. I have gotten use to just placing them back to the correct region...

Happens to me as well.

I've seen this also. It does not look like the kind of bug that is easy to fix. It involves reprograming an integral UI component rather than an illogical rule.

I'm just trying to lower your expectations, so when Pocus does fix it we can all worship him even more.

I will have to disappoint you here, because even if I think I have a fix for this 'drop on my tab' bug, I'm unable to reproduce the problem some people have (being able to displace visually a stack to another region). But perhaps both were linked.

Anyway, for the next update watch out for possible side effects on the first fix.