2
Command Functions
In terms of network/command functions I think they can be divided into 3 catagories
Planning/Strategy
These require time to operate or attention to be shifted out of the cockpit. Setting multiple waypoints, typing instructions, performing functions on an overhead map etc. Things you really can't afford to be doing in combat because you can't do them and fight at the same time.
Combat/Tactical
These should be "one click" functions that can be operated fluently in combat. Setting a single waypoint using the reticule, designating a target, issuing single order via macro etc.
Automatic
Functions that need to be always operating and require no player input such as data and target sharing.
It seems important to me that these things be catagorised correctly, if functions are only useful at a time when there is no time to operate them, such as in combat, they will tend not to be used or it will force the commander to sit out of the battle. The company commander can make best use of the Planning functions, the lance commanders are better to have control of the combat functions.
Command Structure
It is nearly impossible for one person to effectively monitor and control (or assist) a company sized unit. There is just too much to do. For any sort of practical cooperation to occur it will have to be at the small unit level, Lances and Stars. That says nothing for the chances of getting a company to all go along with one plan.
A voluntary Lance system based on the Battlefield model would work well here. Players create a Lance with themselves as leader and people join it if they see an advantage in doing so. Several scout mechs running out to find the enemy would be able to usefully share information with each other and cover more ground quickly etc. It is far less of a problem for Mechs of similar capabilities to simply "follow the leader" than it is for mechs of differing abilities to be coordinated at a distace. Assaults could group together, missile support and so on. Lances would tend to be capability based as Mechs with the same weapons/speed/engagment requirements naturally stick together while those with differing requirements tend to split.
I'd suggest up to 4 lances per side, with one of them having the possibility to be "reinforced" to a strength of 6 Mechs, to allow the main body of a company to all operate on the one command net, rather than splitting them into 3+3 or 4+2.
Becoming a lance commander should be a "free" ability, carried by all mechs. It encourages people to take on command at a junior level at no cost, if it requires modules or skills that are not otherwise useful or they penalise a player by payload/crit reduction then it limits the interest.
Company commander I am not so sure about, it could be the commander of the most populated lance (my current favorite) or it could be an independent position selected by vote, rank or some other means.
Map
Finally, the Commanders Map. I like the idea of a large size overhead map for planning and coordination purposes but I don't like the idea of it filling the whole screen. That level of detail is unnecessary and it makes it impossible to concentrate on except when standing still. I've noticed in the gameplay vids that the pilot view can be moved left and right, I'd like to see this ability used for looking at the overhead map. The pilots view would shift so that the reticule/HUD continues to point forward (unlike in combat mode when it moves with the view) so they can see where they are going/what they are shooting at while the map appears at an angle to the side.
Like thus:
That's it for starters. Commence the bickering
