Orc Incremental Controls

Quick facts

Reference scope

Partial and build-labeled

Demo v0.09

Right-click mute reference

Demo v0.05

Right-click Warpath toggle reference

Version 1.0 plan

Right-click Chieftain ability activation

Complete keymap

Not published

This is not a complete keymap

The server-owned facts show three source-bounded examples. They do not establish every mouse, keyboard, controller, touch, or rebinding action. The axe preview is historical Warpath art and does not prove a global control.

Use Warpath for the old mode-specific context and Chieftains for the announced release system boundary.

Add controls from visible prompts

Every row should name where an input appears and which build shows it.

Field	Required capture
Build	Exact version or date
Screen	Menu, tooltip, battle, or system
Prompt	Complete visible wording
Input	Exact key, button, click, or gesture
Context	State required for the prompt
Result	First visible response
Rebinding	Only if the interface exposes it
Accessibility	Visible alternative or setting

A working action in one context does not establish the same input elsewhere.

Test without destructive consequences

Prefer menus, paused states, or reversible actions when identifying a control. Record the state before the input and the first response. Avoid testing an unknown action on a confirmation screen that could spend resources or overwrite progress.

If a prompt is missing, verify the build and system state. “Not shown in this context” is more accurate than “unsupported.”

Keep devices separate

Keyboard and mouse evidence does not establish controller or touch behavior. Record device type and visible glyphs. Do not translate one platform’s prompt into another platform’s assumed mapping.

Rebinding support, defaults, and conflicts also require current interface evidence. A standard genre convention is not a game fact.

Troubleshoot an unresponsive input

Capture the current prompt, focus state, overlay state, device, and whether another screen accepts input. Try one reversible focus or reconnect check and record the result. Do not disable security software or change unrelated system settings based on a single symptom.

The page grows only from exact prompts and reproducible responses, preserving its partial label even as more rows are verified.

Record accessible alternatives exactly

If the current interface offers hold/toggle behavior, volume cues, captions, focus indicators, or alternative input prompts, capture the exact setting and scope. Do not describe an accessibility option from an operating-system convention or another game.

Test the alternative in the same context as the default and record the visible response. A setting existing in one menu does not prove it applies to every action. Keeping accessibility rows build-labeled makes missing options visible without overstating platform support.

Official source

Verification boundary

Build boundary

partial Demo v0.05/v0.09 and version 1.0 announcement references

Evidence check

2026-08-28

Still unknown

complete keymap, rebinding, controller support, touch controls, current version 1.0 behavior

Frequently asked questions

What is verified about Controls?

Official sources provide only a partial build-labeled control record: Demo v0.09 right-click mute, Demo v0.05 right-click Warpath toggle, and planned version 1.0 right-click Chieftain abilities. Boundary: partial Demo v0.05/v0.09 and version 1.0 announcement references. Checked 2026-08-28. These examples are not a complete current keymap and do not establish rebinding, controller support, touch controls, or present version 1.0 behavior.

How should a current control be added to this reference?

Capture the build, screen, exact visible prompt, input, context, and result. A working input in one system does not establish the same action globally or make the reference complete.