·
inputmap · drop-in viewer
tactical.inputMap
The commander's controls at the Kessrel Line, in three device classes.
by·posted 2mo ago
What it does
tactical.inputMap
The commander's controls at the Kessrel Line, in three device classes.
| Action | Mouse + keyboard | Touch | Controller |
|---|---|---|---|
| Select a regiment | click it, or its card; 1..0 | tap it, or its card | LB / RB cycle |
| Select all | Ctrl+A | the ALL slab | L3 |
| Add to the selection | hold Shift | the ADD slab latches | hold LT |
| Post here | click the ground | tap the ground | left stick aims, A confirms |
| Order cursor | the pointer | the finger | left stick |
| Cycle stance | F | the card's stance strip | X |
| Orbital Lance | Q, then click | Lance button, then tap | Y, then A |
| Mortar Barrage | E, then click | Barrage button, then tap | RT, then A |
| Rally | R | Rally button | D-pad left |
| Cancel an armed ability | right click | tap the lit button again | B |
| Pan the view | A/D, ←/→, ↑/↓, edge pan | drag the canyon | right stick |
| Zoom | wheel, W/S | pinch | D-pad up / down |
| Recentre | C / Home | the RECENTRE pip | D-pad right |
| Pause | Esc / P | the pause pip | Start |
Group commander; it suppresses player, which takes the engine's default
touch floor off the screen so the HUD is the only thing a finger meets.
A control whose touch class reads false has its touch counterpart on the
HUD instead — that is the command slice's own on-screen control surface, and
/zero/source/ui/hud/ draws it.
Discussion
Scoped to this part · feeds back into the world's score.
Sign in to post.sign in
No comments yet. Be the first.