Slitherine

This is perhaps a misunderstanding on my part, but since the AoB expansion I notice an odd phenomenon when setting-up commands at deployment.

When I assign an unallocated general to a unit previously part of another command, that unit receives the general's standard but remains part of the former command. So effectively I have one command with two generals. Previously it would have become a single unit command to which I could then reassign units.

It's not so important but a bit odd. But perhaps I have missed something, and if my apologies in advance.

+1 I've noticed this also.

Strange. I am unable to reproduce this. It seem to be working normally when I test it, and the code for adding generals has not changed.

What sort of battle was it?

Of course if you move your C-in-C to a unit of another command it does not change the unit's command. Could that be what happened?

Looking at the code, this could happen if there are no empty teams (commands). The engine only allows 8 teams, so if all 8 of these already have units, then the unit's team won't change when the general is added.

However, I am struggling to see how, if you already have 8 teams, you have not already been assigned 4 generals.

I am honestly not sure so with this helpful info will try to work out what is going on. I suspect it is the CinC move that you mention, as I had not realised this. Thanks.

I have seen that C-in-C reassignment behaviour happen before.

jomni wrote:I have seen that C-in-C reassignment behaviour happen before.

That is WAD.

Hi Sir,
I am a DBM player from 1.2 I just turn on the computer version of FOG2.
I got the same problem while I played my first personalised battle for training.
I am a french spoken what is WAD ?
Thank you

Koban55 wrote: I am a french spoken what is WAD ?

Welcome to Field of Glory 2!

WAD is an abbreviation for "working as designed", in other words, there is nothing wrong