So many buttons

I actually don't think it's a huge problem since you only see most of those buttons when you select-all, and in that case you're probably only using the common ones. The important thing is that the unit-specific stuff get stuck at the end (load/unload, command-fire, etc.)

Although slightly-related - am I the only one who finds the disembark/embark behavior a bit confusing? I can't get "disembark" to do anything on a unit. If I pick a unit, select "embark" and then queue some move commands before the transport picks it up, it disembarks automatically when it arrives at the destination (heaven help me if I don't queue the moves until after the transport arrives). If I select a unit that's in a transport, the orders don't get relayed to the transport, so the disembark button does nothing.

I suppose I should create a new thread for that... the embark button is wonderful but seems warty.

To be fair, those are the two units with the most icons. The jumping commander is a builder, a d-gunner, and a jumper, and thus carries the jump/d-gun/builder UI. The transport adds the transport UI... so while it is "just two units", it's probably the single strongest combination of two units you could come up with.

But the point is still well-made.

Strongly disagree with removing move. It makes the move hotkey discoverable and likewise the concept that the move command is distinct from the fight command.

I'd kill morphs out of the game before taking the move button, but I'm a big fan of making gameplay follow UI... If a game feature doesn't fit the UI, kill it. Maybe move morphs to a new tab?

How many times have you used "m" to move units? I'm 100% for removal of the move command. It is redundant since the default right click command for every mobile unit is move.

This is why we didn't add set/remove target buttons initially. I honestly still think they should be automatic with a manual attack order ('stop' to clear). 100% that morphs should be in the 'units' tab, except maybe comm.

A year ago I used M for move very very often for builders. That's the time when I got all the my reclaim awards.

Anyway! What I want to say is that play styles, both strategy and control wise, differ a lot among players and that none should be at a disadvantage when it comes to the most basic things such as the move button.

If you really want to have more space for commands, then move "Wait" to unit states.

I think so, but I'm not sure. Does it really matter if Wait's the only queue-able unit state? Nubs don't know how it works/never use it anyway and pros would know/find out anyway.

@luckywaldo's first post:
You have F for patrol, not P?
There are 5 transport buttons and 5 attack-buttons (with fight)? LOL, never noticed that OVERKILL!

@maakey:
I use m to move a Krow over a big factory or over a buildings when I have a repair-zone over these.

@ALL:
can we not add options to hide wer and asdfg buttons? they are so common.
[color=grey]* A good idea for my Chili_Border_Menu, once the bugs are fixed...[/color]

Can we not use shift for queuing, ignore CRTL for unit-commands and - especially - use ALT to toggle between Move/Fight, Load/Unload, Attack/SetTarget, Embark/Disembark, Repair/Reclaim?
* The indicator would be a half/half-ed button icon

If you have only 1 morph or only 1 thing that would open another tab, just keep it in the first one (AND the second one ofc)
* Pxtl> But that would be an assload of contextual checking.

I prefer to use "ALT" for state-shifts in my key-layout - alt-F for firestate, alt-M for movestate, and so on. Personally, I use "CTRL" for the alternate forms of common actions... we already have that a bit - D and CTRL-D for d-gun and self-destruct, I use CTRL-R for resurrect, and T/CTRL-T for target and clear-target.

Or scale down the buttons when they overstep the page's space.