Problem selecting the units

[Pizza90]

Hi all i have a problem selecting the units. This is the problem: i want to select some units but some units close get selected too. This is very annoying especially when i select units to attack a target but a worker gets selected too and then i can't attack. I put here some pictures to explain better:

Romans:
Here i wanted to select the archers but as you can see when i select them two workers gets selected too:
http://img228.imageshack.us/img228/2817/romansn.png

Japanese:
Same thing even in this case a worker gets selected too:
http://img262.imageshack.us/img262/6176/japanesev.png

Is this a bug? Or should the selecting thing get improved Or is it me selecting wrong the units?? I posted here and not in the mods place because happens with various mods and not only one. I tried with the default factions of mg and seems there is no problem.

Im on windows xp.

Greetings

[Omega]

That is a bug in all versions of Glest, MG and GAE included. It has nothing to do with which mod used, as I've seen it on magitech.

[Pizza90]

Oh okay Thanks for the info. To me happens sometimes with various factions and i play many mods so i thought it was related to them. If it's a known bug, well good it's a first step to fix it   Hope it will get fixed soon (yes im sure everyone says the same for every bug   ) because is an important thing since selecting unit it's a main thing of the game.

ps: i modified the title of the post since this problem is not related only to the mod.

[John.d.h]

The only work-around I know of is unselecting the extra units, which is easier in GAE because you can do it by shift-clicking on the units' icons (is this also in MG?).

[Pizza90]

I will copy here the same idea i wrote on the "bugs/works that needs to be fixed/done before release" thread (but as i said im not a developer so dont know if it would work or not):

Forcing the units to attack: When selecting the units example: 4 archers and 1 worker and then you click for attack the units would be forced to attack so at that point only the units with an attack option would attack while the rest would not move. Vice versa when you would select for example 4 workers to harvest the wood and an archer would get selected for error, you could click "harvest" and force the units to harvest, so the workers could go to harvest and the archer would not since he can't harvest.

[Conzar]

In other games, this situation is handled by moving the unit that cannot perform the command along with the units that can perform the command. 

An example in SC2: 2 zealots (melee attacks) and 1 high templar (no melee nor ranged attacks, spell class only).  With 2 zealots and 1 high templar selected, if the player attacks say 1 marine, then the zealots and high templar will move to the marine's position.  The high templar will just move along with the zealots until it too reaches the marine.

Why would you want this behavior?  Because the high templar has spells that might be useful for the attack.  You wouldn't want to box select and move/attack your units only to find out that your high power spell casters are still at home b/c they couldn't actually attack anything. 

Likewise, with the example of the worker, maybe you want an escort for your workers to the gold/wood/stone patches.  If the archer doesn't go along with the workers, you will have to issue yet another command to insure that, slowing down your micro.

I've got some other things to work on ... but I think this is an important gameplay feature, so when I have time, I'll look into the code for this one.

[John.d.h]

In other games, this situation is handled by moving the unit that cannot perform the command along with the units that can perform the command.

Currently, a right click with a mixed selection like that will result in your workers walking up to the enemy and just getting in the way or getting killed.  I would think the ideal solution would be for them to stay just behind the fighters.  Maybe a formation system is in order?  I doubt that's an easy thing to implement, though.

[titi]

I think this problem is fixed now ( on my local copy   )
Will be checked in shortly before next release .... ( still a little secret  )