CMx2's new movement system explained

[Battlefront.com]

NOTE! graphics and naming conventions related to Commands are preliminary. Therefore, this thread should be seen as a discussion of the general UI and behavior of the Commands interface, not an in depth "it will absolutely be in the game this way" type discussion about individual elements.

The concept of issuing instructions to your units is now called "Commands". This is such an important designation we are even capitalizing it In CMx1 Commands ("Orders" in old terms) were simply listed out for the player with some things being context sensitive to game conditions and/or the unit. In CMx2 the Commands are much more streamlined and organized. Instead of having a single popup list of Commands they are now displayed at the bottom of the screen all the time:

Commands are divided up into 4 logical groupings:

Movement Commands - basic Commands to get a unit from A to B.

Combat Commands - basic Commands to instruct a unit how to use its weapon/s and/or weapon/s systems.

Special Commands - Commands for speciality functions specific to that type of unit and/or circumstance.

Administrative Commands - allows the unit to perform certain organizational functions.

Only one group of Commands is shown at any one time, with the little buttons along the bottom toggling which one is shown. The shot above shows, obviously, the Movement Commands being selected.

The new omnipresent Commands interface makes them readily accessible to mouse clicks as well as much more than that. Note that there are 9 possible button positions.... now notice the keypad on your keyboard. What do you think the number keys correspond to? You got it.. the buttons You want that next Waypoint to be a Cohesion Command? Just hit #7 and bingo... you're all set. Want the next one to be Caution? Hit #4 and the next Waypoint, and every successive one unless you make a change, will be a Caution Command. Want a side order of fries with that? Well, we can't do that, but we can allow a Combat Command! Before you click down the next Waypoint simply hit (key TBD) or the little "C" button and the Commands currently at your disposal turn to Combat Commands. Hit the corresponding number key of the Combat Command you want, and bingo... all set. Now when you put down the Waypoint you'll get the new Combat Command as well.

As for Waypoint behavior, it is pretty much the same as CMx1. You have points that are connected by colored lines which represent the Movement Command the unit will follow between the two points. Weapons Commands are similar to CMx1, but now they are assigned to whatever Waypoint they were assigned. It also stays in force until something bumps it. An Arc Fire Command, for example, is followed from Waypoint to Waypoint until another Combat Command is issued, such as a Timed Fire Command. Some Commands, like Timed Fire, require a secondary input from the player, in this case a unit of time for how long the unit should hammer the designated target. Commands like Timed Fire are "One Offs" in that they only apply to that Waypoint and not automatically replicated for following Waypoints. Such Commands are pretty obvious, but there is UI feedback to make sure the player knows the difference between a "Persistent" Command and a "One Off".

OK, so we have all the Commands broken up into nice, neat groups. Big deal, right? Right, it is a big deal

In CMx1 you could generally only issue non-movement instructions at the beginning or end of a line of Waypoints. In CMx2 that has completely changed. Now you can issue up to three Commands per Waypoint; one Movement, one Weapon, and one of either Special or Adminstrative types. Some Commands are "Persistent" in that you select it once and it applies to all further Waypoints, some are "One Offs" in that they apply only to that Waypoint, and others are used for "Start/End" only.

The ramifications of this new system are profound. To illustrate this, I'll describe (in generalized terms) something that was impossible to do in CMx1. In CMx2 if you wish to move a tank moving down a street and moving its turret around to cover potential threats, your Commands might look like this:

Waypoint 1 - Move, orientate turret right

Waypoint 2 - Move, orientate turret left

Waypoint 3 - Move, orientate turret right

Waypoint 4 - Stop, orientate turret center, button up

So for Waypoints 1-3 the player issues two Commands, and for Waypoint 4 issued three. Note that the player doesn't HAVE to issue three Commands per waypoint, just that it is possible to do this if so desired. Much of the time one Command per waypoint will be the norm because the usual Combat Commands are Persistent and Special/Admin Commands are not generally used. Was the lack of this sort of control missed by players? For sure it was to some extent. However, with the way CMx2 works now we expect that people would find the old system a serious liability.

Now, this does not mean the TacAI isn't going to do anything for you as it did in CMx1. Quite the contrary... the TacAI should be quite active in managing the little details. The difference is that the TacAI no longer has to read the player's mind for those situations which fall outside of the norm. For example, you don't have to tell a vehicle to rotate its turret towards a threat in order to engage it, then specify what type of ammo and how many shots to fire at it. 9 times out of 10 the TacAI's default behavior will handle all this stuff exceptionally well, especially because it now has a memory for targets. But when you want to conserve ammo and only whack a bunker ONCE or you have a hunch that a threat is coming from a particular direction, you can now give more guidance to the unit than you could in CMx1.

Any user of CMx1 knows that Battlefront fully understands that the User Interface makes or breaks a game. Especially a tactical wargame. Adding the ability to issue these extra Commands, not surprisingly, requires new interface since CMx1's was not designed to handle the Command concept. Having said that, CMx1's UI was extremely easy to use, intuitive, and quite flexible. Good lesson in game design -> don't chuck out stuff that works!

I guess that's about it. The bottom line is that CMx2's system is very friendly to CMx1 and new players alike, but a lot more powerful than CMx1's system. Early tests with this new system indicate it is possible that the new interface is even easier and faster to use than the old sytem. Flexible and powerful, yet easy to use... that's what we like to deliver in our games!

Steve

[ November 05, 2005, 11:08 AM: Message edited by: Battlefront.com ]

[Frenchy]

Steve:

Thanks for this update. I wonder what other surprises are in store fo us players?!

[Michael Emrys]

Neat! Only...

Originally posted by Battlefront.com:

...we can allow a Weapons Command! Before you click down the next Waypoint simply hit (key TBD) or the little "W" button...

What "little 'W' button"? If it's the one I am looking at in your illustration, it's labeled 'C' (for Combat?). Actually, I think I like 'W' better as it is more intuitive and easier to remember.

Otherwise, I like what I'm seeing here.

Michael

[junk2drive]

I should'a taken a screenshot before Steve edited the pic.

[flamingknives]

Yeah, WTF just happened there?

I'd hazard that Moon rang Steve up, yelling;

"What the *$*£ are you doing! That's classified!"

And there was a 'W' button in place of the 'C'

[Stingray]

Outstanding !!! Can't wait for the demo to try this new UI.

[Scipio]

Originally posted by Battlefront.com:

Flexible and powerful, yet easy to use... that's what we like to deliver in our games!

Steve

And that's what we would like to get from you!

If I understood right, commands are given that way to single units? How about Platoons? Shall we say, I want my infantry platoon sneak to point x, and than assault point y. Will I have to issue orders to each single squad, or can I use group commands?

CM1x allows no waypoints for group commands. Will this be changed?

[Battlefront.com]

Whoops... forgot about the terminology change de jour. We are calling the "Weapons" Commands "Combat Commands" since not all are strictly weapons related. I've edited the description to match up with the screenshot.

The other screenshot, that was displayed for about 2 minutes, will come back around today or tomorrow. I just don't have time to detail those things all at once so I'm hacking them off one or two at a time

Steve

[aka_tom_w]

WOW!

Great

Many thanks

the rest of my family JUST can't understand why I can't let my powwerbook out of my sight now for more a minute for fear of missing more news worthy posts and staying up-to-date with all the latest news!

My head is spinning

(in a good way)

-tom w

[Battlefront.com]

Group Commands may or may not make it in. We'll just have to see. There are a lot of niggly little problems for us to work through to make this feature somewhat useful instead of totally useless.

Steve

[stikkypixie]

What about command delays?

[Mace]

Steve, IIRC you indicated that the CMx2 engine can support pre-scripted 'movies' that helps set the scene for a scenario.

From what I'm seeing here you could use the commands to set up the 'movie script'?

[SgtMuhammed]

I want voice recognition software so I can hook up my old CVC to my computer and relive my glory days!

Seriously thought it sounds interesting, can't wait to try it out.

[Michael Emrys]

Never mind.

Michael

[mazex]

Sweeet! The more the merrier!

Some questions about the commands displayed in the screenshot (wich are all MOVE commands):

Why is there no "normal" (yet)? In may situations you want you soldiers to simply march without getting exausted, but without dragging their feet behind...

Is it maybe possible to do a move with none of the options selected (a "normal" move)? In that case, can you depress two of them for a combination? Mmm that would be really nice! "Move in cover but do it as fast as possible" is fairly different from: "move to point B, but don't get detected - time is irrerevant so take your time and crawl silently!". The possibilites are endless - and the time to implement them too I guess

When you move a squad - will the "cover" command be in the form of moving in bounds if under fire?

I would really like the additional option "Run as hell!" (or a more polically correct name:)) as a higher alternative to "speed" for making sure that the squad really runs as fast as possible over a street when another squad gets the "Suppressive fire - maximum ammunition expenditure!". For me, "Speed" could be something you give as an order to the squad in the rear that are going to march fast with no risk of enemy fire to point C, or the sprint speed across the street above...

Anyway, it seems A LOT better than CMx1 but you know how it is - give the hounds a load of bones and they want more or they'll try to bite your arm off

/Mazex

[ November 05, 2005, 01:53 PM: Message edited by: mazex ]

[M1A1TC]

Originally posted by Battlefront.com:

Waypoint 1 - Move, orientate turret right

Waypoint 2 - Move, orientate turret left

Waypoint 3 - Move, orientate turret right

Waypoint 4 - Stop, orientate turret center, button up

Steve

Why cant you make the tank or any other armored vehicles scan for targets automatically? I dont want to have to tell every single gunner of each vehicle how to do their job

For example, if you set firing limits, the gunner can scan inside that arc automatically. That would be easier for player- less micro-management. That is a downfall of CM games

[flamingknives]

Isn't the scenario quoted by Steve more along the lines of 'Cover right/left' commands? If you picture the example being a tank moving down a street with cross-street, does that make more sense?

[M1A1TC]

The TAC AI should detect the street on the right, and tell the gunner to scan down the street. I dont want to do it myself- as a commander- for each vehicle. Thats gunner's job.

You supposed to be playing a bigger role

[flamingknives]

CM isn't a command game though.

I'd hazard that coding the TacAI to get the turret in the right direction in anything other than a very clear cut situation, like said street, would be a royal PITA.

Even the street situation could be more complex, as you could have already secured the side streets with a threat to the front.

[Bil Hardenberger]

Interesting stuff Steve, and about time

Pity that Platoon orders might not make it in.. but I definitely understand the need to either do it right or not at all.

Bil

[M1A1TC]

Originally posted by flamingknives:

CM isn't a command game though.

How is that?

[flamingknives]

You don't play the role of platoon/company/battalion commander. If you did then it would be an FPS with orders.

You command each unit rather like the unit's commander (squad leader, TC, whatever).

[M1A1TC]

I am sorry but I disagree. This game is exactly a platoon/company/troop/battalion commander simulator, with micro-managing options. Its doesnt have to be FPS

[flamingknives]

How many Company commanders do you know who have to order all their squads how to behave, and can fly around the battlefield?

[M1A1TC]

How many squad leaders do you know that fly around the battlefield giving orders to the whole battalion, besides their own squad?