#1 and #2 Key Selected for Any Unit Switches the AI for the Entire Corps

[J Canuck]

If this is not a bug which I discovered during the Corps Tutorial, perhaps this command model could be reconsidered as it doesn’t seem to be intuitive. If it is a bug, I don't believe a sample battle is required as this condition exists immediately upon the start of the Corps Tutorial.

The keys numbered 1 and 2 that toggle the Take Command function, affect every unit across the entire Corps with one click – the toggle is not restricted to just those units in the particular chain of command where the toggle is being used.

For instance, if I select any Brigade Commander within any Division and hit either the #1 or #2 key, every Division Commander, Brigade Commander, Regiment, Supply Wagon and Artillery Battery in the entire Corps also switches its AI to coincide with the toggled #. A sample consequence is: if I select any Infantry Brigade or just an Ammo Wagon and hit the #2 key, all of my carefully placed and “Take Commanded” Artillery switches their AI function to #2 and starts wandering off.) Toggling #1 or #2 changes the entire Corps’ AI regardless of the unit selected.

The problem this creates is frustrating during those times when I want to force one entire Division to change direction and advance without changing the current AI selection throughout the balance of my Corps. Activating the Take Command flag button of a commander does not solve this problem, because that button only changes the AI of the individual Commander. Reporting units will continue to follow the orders of the AI including any influence by its Stance Order button, especially if the enemy is close by.

I’m sure someone will tell me if I am missing something.

[norb]

I believe that it is for every unit under your command.

[J Canuck]

It is not and that is my point Norb. I thought the #1/#2 buttons should affect just the units under my direct command; but they do not. The #1 key automatically gives me command for every friendly unit in the game and #2 reverts all of them back to the AI.

For example: when I select Division Commander A and click on the #1 key, the Take Command flag lights up and I am given command for the brigades and regiments in Division A. At the same time however, all the Take Command flags of all the friendly units in the game light up and I am given command for every single unit in Divison B , Division C and the Arty Reserve Division D – the entire Corps in the Tutorial!

Is that the way the #1/#2 toggle is supposed to work or am I the only one with the problem?

ps
I just ran out, bought and replaced the batteries in my wireless keyboard = problem still exists.
I changed my wireless for a hardwired keyboard = problem still exists.

Can anyone here replicate my problem? Just start the Corps Tutorial and try out the #1/#2 keys on various units. I’m stumped.

[ADukes]

Yes that's the way 1 & 2 are supposed to work.

You could replace tcallon/tcalloff with Atcommon/Atcommoff in the keyboard.csv.

[J Canuck]

Thank you for swooping in ADukes (as always) to clarify and add your suggestion. I will definitely give that a try. In the vanilla game this does mean that effectively using the #1 key will have to be a two-step process.

Step One
Select a Commander and click his Take Command flag. Next, issue movement and formation orders.

Step Two
Once they start moving, click the #1 key once which will activate the Take Command flags of all subordinate units to force them to blindly follow your orders.

If the #1 key is clicked prior to issuing location and formation orders, the subordinate units will not follow your orders. Unfortunately, the two-step process is a bit cumbersome with enemy is nearby, because one has to click the #1 key quickly before the AI activates and issues a different order to the subordinate units.

Using the #2 key (giving command back to the AI) is cumbersome in a different way as I had laid out in my original post. Because the #2 key gives command back to the AI for all friendly units in the game, it includes those units which one may want to retain command over. The most common one I can think of keeping command over is artillery in order to keep them from wandering off. Once you hit the #2 key, you need to rush back to your artillery and reinstate command by clicking their Take Command flags before the AI takes over.

You getting all this Chamberlain? (Chantilly doesn’t seem to be around.)

All in all these are minor issues to work around for a micromanager who is a take control freak, but enjoys having the #1/#2 option. Norb, I fully appreciate you have much bigger fish to fry to fine tune such a superb game. Thanks again for your help ADukes.

[norb]

I have been told in our bug database that what you describe is how most people expect it to work. So I believe that we will change our defaults. But modding the keyboard file will do exactly what you want.

[J Canuck]

WOW!!!

That’s perfect – works like a charm!

Talk about service – just 29 hours from my first post!!

You guys must have too much time on your hands.

[norb]

No, we just need everyone here to spread the word, so we want to keep you all happy

Also, we worked for a long time on this, it's our baby and we want it to shine!

[J Canuck]

norb wrote:

I have been told in our bug database that what you describe is how most people expect it to work. So I believe that we will change our defaults.

I noticed the default has not been changed by the patches. I changed my keyboard.csv to Atcommon/Atcommoff and it works fine of course. However, I do appreciate the decision may have been made not to change the default - I'm just bringing this up in case it was overlooked.

[norb]

We do not overwrite the ini nor keyboard file in our patches. You can check the default keyboard csv file to see if it was changed there.