RTS pointer

rts-pointer · an adoption of Control options, version 1

Tests included

Use in your game

Opens the authoring tool with these answers and settings already filled in. You still add your game's own rules and tuning.

Open in the authoring tool Download ZIP

What is in the ZIP

The ZIP holds the adoption and its acceptance tests. In the authoring tool, choose Add contract and pick this ZIP. If you keep your design as files, put them in contracts/.

Download adoption JSON · Download tests

The contract behind it

Covers which physical inputs produce each action on every platform. It also covers complete input methods, named control presets, remapping, press styles, simpler alternatives, and device-motion inputs. Action prompts, input timing help, shared-action choice, and event order stay elsewhere.

Read the full Control options contract →

Questions

The supplied answer is marked on each question. Pick other answers to see what changes. Nothing is saved here: the ZIP and the authoring tool use the supplied answers.

Show exact wording for builders

How can players normally change the controls?

Asked when: the platform control sets list has at least one row.
If not asked: With no platform control set, this adoption makes no game-wide remapping promise.

Fixed bindings	The controls cannot be changed in the game. A puzzle game always keeps rotate on the space bar. No player-facing setting changes an action's physical input or press style.
Swap only	Existing controls can only exchange actions. A platformer can swap jump and dash, but an unused button cannot receive either action. A supported binding can exchange its current action with another supported binding; no action can move independently to an otherwise unused input.
Presets only	Players can choose only from named control sets. An action game offers Default and Alternate layouts without individual button changes. The player may select a complete declared preset but cannot change one binding independently inside that preset. The platform offers at least two presets whose availability is starting-and-selectable or player-selectable.
Any action any inputSupplied answer	Any action can move to any supported input. A strategy game can move end turn from Enter to an unused mouse button. Every covered action can be assigned independently to any supported remappable input, including an otherwise unassigned input; conflicts are resolved visibly before use.
Action and press style	Both the input and the press style can change. An adventure game can move interact to another button and change a hold into one press. Every covered action can change to a supported input and to any press style that its cited platform rule offers for that action.

Why this is asked

A platform may offer fixed controls, named layouts, or free changes. This answer supplies the ordinary choice before a platform states another one.

What normally happens when an action needs a difficult press?

Asked when: the platform control sets list has at least one row.
If not asked: With no platform control set, this adoption makes no game-wide demanding-input promise.

No demanding pressesSupplied answer	No action needs a demanding press. A card game plays a selected card with one ordinary activation. No covered binding requires timed, held, rapid, repeated, double, simultaneous, directional-sequence, or device-motion input as its only route to the action.
Simpler alternative	Every demanding press has a distinct simpler route with no setting change. A repair game offers a separate tap button beside its hold-to-repair control. Every covered demanding binding has a declared alternative that performs the same action without configuration.
Player can change it	A setting can make the press easier. A racing game can change a held pit command into one ordinary press. A player-facing setting replaces each covered demanding press with a declared easier press style before play uses the binding.
Required as written	The demanding press remains required. A rhythm special still needs two buttons together and has no simpler route from this contract. The covered demanding binding has no simpler alternative or press-style setting promised by this adoption.

Why this is asked

Holds, rapid presses, double presses, and button combinations can block an otherwise known action. This answer supplies the ordinary choice.

Numbersno numbers

This contract has no numbers to set.

Rules1 rule

A rule is a check between the numbers. Validation reports a rule that fails.

Controls that let players change a press style cannot also require every demanding press exactly as written.

Forbidden when Remapping default is Action and press style, and Demanding input default is Required as written.

Lists4 lists

Each list holds the rows this adoption supplies. A list can be empty.

Platform control sets

platform-control-sets

Id	Platform declared in	Methods declared in	Input method coverage	Remapping	Settings rule declared in
`pc`	`platforms.pc`	`controls.pc-keyboard-and-pointer`	`one-method-covers-all`	`use-game-default`	`controls.pc-remapping-and-conflicts`

Control presets

control-presets

This adoption declares no control presets.

Action bindings

action-bindings

Id	Platform control set	Preset	Context declared in	Action declared in	Physical input declared in	Action input	Press style	Motion use	Demanding input
`pc-select-area-primary-drag`	`pc`	—	—	`controls.selection-drag`	`controls.pointer-primary-drag-activation`	—	`gesture`	`no-motion`	`use-game-default`
`pc-context-order-secondary-release`	`pc`	—	—	`controls.context-order`	`controls.pointer-secondary-release-activation`	—	`release`	`no-motion`	`use-game-default`
`pc-queue-command-modifier-hold`	`pc`	—	—	`controls.queue-command-active`	`controls.queue-modifier-key-hold`	—	`hold`	`no-motion`	`required-as-written`
`pc-edge-pan-pointer-edge`	`pc`	—	—	`controls.tactical-edge-pan-action`	`controls.pointer-edge-activation`	—	`gesture`	`no-motion`	`use-game-default`
`pc-zoom-in-wheel-forward`	`pc`	—	—	`controls.tactical-zoom-actions-and-range`	`controls.zoom-in-wheel-activation`	—	`press`	`no-motion`	`use-game-default`
`pc-zoom-out-wheel-back`	`pc`	—	—	`controls.tactical-zoom-actions-and-range`	`controls.zoom-out-wheel-activation`	—	`press`	`no-motion`	`use-game-default`

Simpler inputs

simpler-inputs

This adoption declares no simpler inputs.

Test inputsscope and seeds

Some tests need a scope or seeds from the adoption before they can run.

This adoption supplies none; every test uses its defaults.

Acceptance tests73 tests apply

The contract comes with 64 tests. A test that runs once per row is counted once for each row. Tests that do not apply to these answers are still listed, with the reason.

control-options-vocabulary

control options uses control sets, presets, bindings, action inputs, and demanding inputs

scenarioonce

Applies to rts-pointer.

A control set is the complete current mapping for one platform and input method. A preset is an immutable named source set that can become current. A binding joins one physical input and press style to one candidate action. One physical activation emits one action input carrying every matched binding's action. A demanding input is a timed, held, rapid, repeated, double, simultaneous, input-sequence, or required-device-motion input.

Test steps and diagnostics

Given: the rts-pointer adoption and its cited control rules
When: the control path is identified from platform selection through physical activation
Then: a control set is the complete current mapping for one platform and input method
a preset is an immutable named source set that can become current
a binding joins one physical input and press style to one candidate action
one physical activation emits one action input carrying every matched binding's action
a demanding input is a timed, held, rapid, repeated, double, simultaneous, input-sequence, or required-device-motion input
Diagnostics: rts-pointer-current-set
rts-pointer-action-input-log

platform-row-selects-exactly-when-cited · pc

`pc` is selected exactly for its cited platform and devices

scenarioper platform-control-sets row

Applies to the pc row.

Platform row pc is the one selected row exactly on the platform, edition, and supported devices at platforms.pc. It is not selected where that citation excludes it. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: platform-control-set row pc and the Fixed platform rule at platforms.pc
When: the game runs on each cited platform, edition, and supported device combination and on the nearest combination the citation excludes
Then: pc is the one selected row for every combination the citation covers
pc is not selected for a combination the citation excludes
the test leaves the covered combinations to platforms.pc and restates nothing from it
Diagnostics: rts-pointer-platform-selection

starting-control-set-follows-platform-rule · pc

`pc` starts with the control set chosen by its cited rule

scenarioper platform-control-sets row

Applies to the pc row.

On first play for pc, the complete starting control set comes from controls.pc-remapping-and-conflicts, and every first binding lookup reads it as current. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: a first play on platform row pc and the Fixed settings rule at controls.pc-remapping-and-conflicts
When: the current set is first established
Then: the complete starting control set is the one selected through controls.pc-remapping-and-conflicts
every first binding lookup reads that current set
the test restates nothing from the cited rule
Diagnostics: rts-pointer-current-set

preset-selection-copies-complete-set

preset `Row.id` becomes current through its cited route

scenarioper control-presets row

Does not apply to rts-pointer: control-presets has no rows.

input-method-coverage-holds · pc

`pc` input methods cover its actions as promised

scenarioper platform-control-sets row

Applies to the pc row.

Audit class: observer-judged. An observer, not the running game, judges this in each preset-derived current set pc can make current. For every action bound on the platform, under the complete methods and any required switch at controls.pc-keyboard-and-pointer: the one complete method named by the citation performs every action bound on the platform without another method. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: platform row pc, every action bound on that platform, and the complete methods and any required switch at controls.pc-keyboard-and-pointer
When: in each preset-derived current set the platform can make current, an observer performs every action bound on the platform using the named method or methods
Then: the one complete method named by the citation performs every action bound on the platform without another method
an observer, not the running game, judges this
the test restates nothing from the cited rule
Diagnostics: rts-pointer-pc-observer-result

remapping-fixed-override

`Row.id` keeps fixed bindings by its row answer

scenarioper platform-control-sets row

Does not apply to rts-pointer: no row in platform-control-sets matches remapping fixed bindings.

remapping-fixed-default

`Row.id` keeps fixed bindings by the game default

scenarioper platform-control-sets row

Does not apply to rts-pointer: remapping default is any action any input, not fixed bindings.

remapping-swap-override

`Row.id` permits only exchanges by its row answer

scenarioper platform-control-sets row

Does not apply to rts-pointer: no row in platform-control-sets matches remapping swap only.

remapping-swap-default

`Row.id` permits only exchanges by the game default

scenarioper platform-control-sets row

Does not apply to rts-pointer: remapping default is any action any input, not swap only.

remapping-presets-override

`Row.id` permits only preset selection by its row answer

scenarioper platform-control-sets row

Does not apply to rts-pointer: no row in platform-control-sets matches remapping presets only.

remapping-presets-default

`Row.id` permits only preset selection by the game default

scenarioper platform-control-sets row

Does not apply to rts-pointer: remapping default is any action any input, not presets only.

remapping-free-override

`Row.id` permits free assignment by its row answer

scenarioper platform-control-sets row

Does not apply to rts-pointer: no row in platform-control-sets matches remapping any action any input.

remapping-free-default · pc

`pc` permits free assignment by the game default

scenarioper platform-control-sets row

Applies to the pc row.

Audit class: observer-judged. An observer, not the running game, judges this. The row uses the game default: every covered action can move independently to every supported remappable input, including an unused one; conflicts resolve visibly before use; the new binding performs the action and the old one does not. After an accepted change, the contract makes each binding row's promises follow its action to the input the current set assigns. An unsupported assignment is refused. Each accepted complete result becomes current for every later lookup. The route is at controls.pc-remapping-and-conflicts; the test restates nothing from it.

Test steps and diagnostics

Given: each covered action, each supported remappable input including an unused one, and controls.pc-remapping-and-conflicts for pc
When: an observer independently assigns an action to each supported input, resolves a conflicting assignment, performs the action, and attempts one unsupported assignment
Then: every supported independent assignment is accepted, including assignment to the unused input
a conflict is resolved visibly before use
the new binding performs the action and the old binding does not
after an accepted change, each binding row's promises follow its action to the input the current set assigns
the unsupported assignment is refused and leaves the current set unchanged
every accepted complete result becomes current for every later lookup
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-observer-result
rts-pointer-change-log
rts-pointer-current-set
rts-pointer-action-input-log

remapping-press-style-override

`Row.id` permits input and press-style changes by its row answer

scenarioper platform-control-sets row

Does not apply to rts-pointer: no row in platform-control-sets matches remapping action and press style.

remapping-press-style-default

`Row.id` permits input and press-style changes by the game default

scenarioper platform-control-sets row

Does not apply to rts-pointer: remapping default is any action any input, not action and press style.

binding-scope-follows-current-set · pc-select-area-primary-drag

`pc-select-area-primary-drag` exists in its declared control-set scope

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

Binding pc-select-area-primary-drag belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to pc's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. A preset or context the row does not name asserts nothing.

Test steps and diagnostics

Given: binding pc-select-area-primary-drag on platform row pc
When: the current set is inspected across its reachable control-set and play contexts
Then: the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
the binding exists throughout the selected control set, or only in the cited context where the row names one
a preset or context the row does not name asserts nothing
Diagnostics: rts-pointer-current-set
rts-pointer-match-trace

binding-scope-follows-current-set · pc-context-order-secondary-release

`pc-context-order-secondary-release` exists in its declared control-set scope

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

Binding pc-context-order-secondary-release belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to pc's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. A preset or context the row does not name asserts nothing.

Test steps and diagnostics

Given: binding pc-context-order-secondary-release on platform row pc
When: the current set is inspected across its reachable control-set and play contexts
Then: the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
the binding exists throughout the selected control set, or only in the cited context where the row names one
a preset or context the row does not name asserts nothing
Diagnostics: rts-pointer-current-set
rts-pointer-match-trace

binding-scope-follows-current-set · pc-queue-command-modifier-hold

`pc-queue-command-modifier-hold` exists in its declared control-set scope

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

Binding pc-queue-command-modifier-hold belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to pc's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. A preset or context the row does not name asserts nothing.

Test steps and diagnostics

Given: binding pc-queue-command-modifier-hold on platform row pc
When: the current set is inspected across its reachable control-set and play contexts
Then: the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
the binding exists throughout the selected control set, or only in the cited context where the row names one
a preset or context the row does not name asserts nothing
Diagnostics: rts-pointer-current-set
rts-pointer-match-trace

binding-scope-follows-current-set · pc-edge-pan-pointer-edge

`pc-edge-pan-pointer-edge` exists in its declared control-set scope

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

Binding pc-edge-pan-pointer-edge belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to pc's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. A preset or context the row does not name asserts nothing.

Test steps and diagnostics

Given: binding pc-edge-pan-pointer-edge on platform row pc
When: the current set is inspected across its reachable control-set and play contexts
Then: the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
the binding exists throughout the selected control set, or only in the cited context where the row names one
a preset or context the row does not name asserts nothing
Diagnostics: rts-pointer-current-set
rts-pointer-match-trace

binding-scope-follows-current-set · pc-zoom-in-wheel-forward

`pc-zoom-in-wheel-forward` exists in its declared control-set scope

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

Binding pc-zoom-in-wheel-forward belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to pc's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. A preset or context the row does not name asserts nothing.

Test steps and diagnostics

Given: binding pc-zoom-in-wheel-forward on platform row pc
When: the current set is inspected across its reachable control-set and play contexts
Then: the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
the binding exists throughout the selected control set, or only in the cited context where the row names one
a preset or context the row does not name asserts nothing
Diagnostics: rts-pointer-current-set
rts-pointer-match-trace

binding-scope-follows-current-set · pc-zoom-out-wheel-back

`pc-zoom-out-wheel-back` exists in its declared control-set scope

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

Binding pc-zoom-out-wheel-back belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to pc's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. A preset or context the row does not name asserts nothing.

Test steps and diagnostics

Given: binding pc-zoom-out-wheel-back on platform row pc
When: the current set is inspected across its reachable control-set and play contexts
Then: the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
the binding exists throughout the selected control set, or only in the cited context where the row names one
a preset or context the row does not name asserts nothing
Diagnostics: rts-pointer-current-set
rts-pointer-match-trace

binding-matches-cited-performance · pc-select-area-primary-drag

`pc-select-area-primary-drag` matches only its cited `gesture` performance

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

For pc-select-area-primary-drag, when the cited gesture completes under controls.pointer-primary-drag-activation, one action input carries the action at controls.selection-drag. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.

Test steps and diagnostics

Given: binding pc-select-area-primary-drag, action controls.selection-drag, and the physical input, device, and performance at controls.pointer-primary-drag-activation
When: the cited gesture completes in the current platform, device, method, and set, then the nearest non-matching performance is attempted
Then: the matching performance emits one action input carrying the action at controls.selection-drag
the non-matching performance emits nothing from this binding
the test leaves the physical details to controls.pointer-primary-drag-activation and restates nothing from it
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

binding-matches-cited-performance · pc-context-order-secondary-release

`pc-context-order-secondary-release` matches only its cited `release` performance

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

For pc-context-order-secondary-release, when the cited input is released under controls.pointer-secondary-release-activation, one action input carries the action at controls.context-order. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.

Test steps and diagnostics

Given: binding pc-context-order-secondary-release, action controls.context-order, and the physical input, device, and performance at controls.pointer-secondary-release-activation
When: the cited input is released in the current platform, device, method, and set, then the nearest non-matching performance is attempted
Then: the matching performance emits one action input carrying the action at controls.context-order
the non-matching performance emits nothing from this binding
the test leaves the physical details to controls.pointer-secondary-release-activation and restates nothing from it
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

binding-matches-cited-performance · pc-queue-command-modifier-hold

`pc-queue-command-modifier-hold` matches only its cited `hold` performance

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

For pc-queue-command-modifier-hold, when the cited input is held for its cited completion under controls.queue-modifier-key-hold, one action input carries the action at controls.queue-command-active. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.

Test steps and diagnostics

Given: binding pc-queue-command-modifier-hold, action controls.queue-command-active, and the physical input, device, and performance at controls.queue-modifier-key-hold
When: the cited input is held for its cited completion in the current platform, device, method, and set, then the nearest non-matching performance is attempted
Then: the matching performance emits one action input carrying the action at controls.queue-command-active
the non-matching performance emits nothing from this binding
the test leaves the physical details to controls.queue-modifier-key-hold and restates nothing from it
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

binding-matches-cited-performance · pc-edge-pan-pointer-edge

`pc-edge-pan-pointer-edge` matches only its cited `gesture` performance

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

For pc-edge-pan-pointer-edge, when the cited gesture completes under controls.pointer-edge-activation, one action input carries the action at controls.tactical-edge-pan-action. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.

Test steps and diagnostics

Given: binding pc-edge-pan-pointer-edge, action controls.tactical-edge-pan-action, and the physical input, device, and performance at controls.pointer-edge-activation
When: the cited gesture completes in the current platform, device, method, and set, then the nearest non-matching performance is attempted
Then: the matching performance emits one action input carrying the action at controls.tactical-edge-pan-action
the non-matching performance emits nothing from this binding
the test leaves the physical details to controls.pointer-edge-activation and restates nothing from it
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

binding-matches-cited-performance · pc-zoom-in-wheel-forward

`pc-zoom-in-wheel-forward` matches only its cited `press` performance

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

For pc-zoom-in-wheel-forward, when the cited input is pressed under controls.zoom-in-wheel-activation, one action input carries the action at controls.tactical-zoom-actions-and-range. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.

Test steps and diagnostics

Given: binding pc-zoom-in-wheel-forward, action controls.tactical-zoom-actions-and-range, and the physical input, device, and performance at controls.zoom-in-wheel-activation
When: the cited input is pressed in the current platform, device, method, and set, then the nearest non-matching performance is attempted
Then: the matching performance emits one action input carrying the action at controls.tactical-zoom-actions-and-range
the non-matching performance emits nothing from this binding
the test leaves the physical details to controls.zoom-in-wheel-activation and restates nothing from it
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

binding-matches-cited-performance · pc-zoom-out-wheel-back

`pc-zoom-out-wheel-back` matches only its cited `press` performance

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

For pc-zoom-out-wheel-back, when the cited input is pressed under controls.zoom-out-wheel-activation, one action input carries the action at controls.tactical-zoom-actions-and-range. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.

Test steps and diagnostics

Given: binding pc-zoom-out-wheel-back, action controls.tactical-zoom-actions-and-range, and the physical input, device, and performance at controls.zoom-out-wheel-activation
When: the cited input is pressed in the current platform, device, method, and set, then the nearest non-matching performance is attempted
Then: the matching performance emits one action input carrying the action at controls.tactical-zoom-actions-and-range
the non-matching performance emits nothing from this binding
the test leaves the physical details to controls.zoom-out-wheel-activation and restates nothing from it
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

binding-context-settles-at-accepted-moment

`Row.id` settles its context at the accepted moment

scenarioper action-bindings row

Does not apply to rts-pointer: no matching row in action-bindings has every field this test uses (context-declared-in).

binding-preset-is-current

`Row.id` exists only while preset `Bind preset` is current

scenarioper action-bindings row

Does not apply to rts-pointer: no matching row in action-bindings has every field this test uses (preset).

shared-physical-activation-stays-one-input

`Row.id` shares action input `Bind action input` consistently

scenarioper action-bindings row

Does not apply to rts-pointer: no matching row in action-bindings has every field this test uses (action-input).

simpler-input-matches-named-binding

`Row.id` matches as binding `Row.action binding`

scenarioper simpler-inputs row

Does not apply to rts-pointer: simpler-inputs has no rows.

demanding-none-override

`Row.id` has an ordinary route by its row answer

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches demanding-input no demanding presses.

demanding-none-default · pc-select-area-primary-drag

`pc-select-area-primary-drag` has an ordinary route by the game default

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

Audit class: observer-judged. An observer, not the running game, judges this. The row uses the game default: the action for pc-select-area-primary-drag has an ordinary route without a setting change, and performing that route emits an action input carrying the action. A demanding input is not its only route.

Test steps and diagnostics

Given: binding pc-select-area-primary-drag and its cited action and physical-input rules
When: an observer performs the covered action through its ordinary route without changing a setting
Then: the ordinary route produces an action input carrying the action at controls.selection-drag
no demanding input is the action's only route
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-select-area-primary-drag-observer-result
rts-pointer-action-input-log

demanding-none-default · pc-context-order-secondary-release

`pc-context-order-secondary-release` has an ordinary route by the game default

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

Audit class: observer-judged. An observer, not the running game, judges this. The row uses the game default: the action for pc-context-order-secondary-release has an ordinary route without a setting change, and performing that route emits an action input carrying the action. A demanding input is not its only route.

Test steps and diagnostics

Given: binding pc-context-order-secondary-release and its cited action and physical-input rules
When: an observer performs the covered action through its ordinary route without changing a setting
Then: the ordinary route produces an action input carrying the action at controls.context-order
no demanding input is the action's only route
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-context-order-secondary-release-observer-result
rts-pointer-action-input-log

demanding-none-default · pc-edge-pan-pointer-edge

`pc-edge-pan-pointer-edge` has an ordinary route by the game default

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

Audit class: observer-judged. An observer, not the running game, judges this. The row uses the game default: the action for pc-edge-pan-pointer-edge has an ordinary route without a setting change, and performing that route emits an action input carrying the action. A demanding input is not its only route.

Test steps and diagnostics

Given: binding pc-edge-pan-pointer-edge and its cited action and physical-input rules
When: an observer performs the covered action through its ordinary route without changing a setting
Then: the ordinary route produces an action input carrying the action at controls.tactical-edge-pan-action
no demanding input is the action's only route
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-edge-pan-pointer-edge-observer-result
rts-pointer-action-input-log

demanding-none-default · pc-zoom-in-wheel-forward

`pc-zoom-in-wheel-forward` has an ordinary route by the game default

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

Audit class: observer-judged. An observer, not the running game, judges this. The row uses the game default: the action for pc-zoom-in-wheel-forward has an ordinary route without a setting change, and performing that route emits an action input carrying the action. A demanding input is not its only route.

Test steps and diagnostics

Given: binding pc-zoom-in-wheel-forward and its cited action and physical-input rules
When: an observer performs the covered action through its ordinary route without changing a setting
Then: the ordinary route produces an action input carrying the action at controls.tactical-zoom-actions-and-range
no demanding input is the action's only route
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-zoom-in-wheel-forward-observer-result
rts-pointer-action-input-log

demanding-none-default · pc-zoom-out-wheel-back

`pc-zoom-out-wheel-back` has an ordinary route by the game default

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

Audit class: observer-judged. An observer, not the running game, judges this. The row uses the game default: the action for pc-zoom-out-wheel-back has an ordinary route without a setting change, and performing that route emits an action input carrying the action. A demanding input is not its only route.

Test steps and diagnostics

Given: binding pc-zoom-out-wheel-back and its cited action and physical-input rules
When: an observer performs the covered action through its ordinary route without changing a setting
Then: the ordinary route produces an action input carrying the action at controls.tactical-zoom-actions-and-range
no demanding input is the action's only route
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-zoom-out-wheel-back-observer-result
rts-pointer-action-input-log

demanding-simpler-press-style-override

the demanding press style of `Row.id` follows simpler-alternative by its row answer

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches demanding-input simpler alternative and press-style timed press or hold or rapid presses or repeated presses or double press or simultaneous inputs or input sequence and motion-use no motion or optional motion.

demanding-simpler-required-motion-override

the required motion of `Row.id` follows simpler-alternative by its row answer

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches demanding-input simpler alternative and motion-use required motion.

demanding-simpler-press-style-default

the demanding press style of `Row.id` follows simpler-alternative by the game default

scenarioper action-bindings row

Does not apply to rts-pointer: demanding input default is no demanding presses, not simpler alternative.

demanding-simpler-required-motion-default

the required motion of `Row.id` follows simpler-alternative by the game default

scenarioper action-bindings row

Does not apply to rts-pointer: demanding input default is no demanding presses, not simpler alternative.

demanding-setting-press-style-override

the demanding press style of `Row.id` follows player-can-change-it by its row answer

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches demanding-input player can change it and press-style timed press or hold or rapid presses or repeated presses or double press or simultaneous inputs or input sequence and motion-use no motion or optional motion.

demanding-setting-required-motion-override

the required motion of `Row.id` follows player-can-change-it by its row answer

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches demanding-input player can change it and motion-use required motion.

demanding-setting-press-style-default

the demanding press style of `Row.id` follows player-can-change-it by the game default

scenarioper action-bindings row

Does not apply to rts-pointer: demanding input default is no demanding presses, not player can change it.

demanding-setting-required-motion-default

the required motion of `Row.id` follows player-can-change-it by the game default

scenarioper action-bindings row

Does not apply to rts-pointer: demanding input default is no demanding presses, not player can change it.

demanding-required-press-style-override · pc-queue-command-modifier-hold

the demanding press style of `pc-queue-command-modifier-hold` follows required-as-written by its row answer

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

Audit class: observer-judged. An observer, not the running game, judges this. The row overrides the game default. The contract treats the press style of pc-queue-command-modifier-hold as demanding: completing it emits the action input and stopping before completion emits none from this contract.

Test steps and diagnostics

Given: binding pc-queue-command-modifier-hold and its cited demanding press style
When: an observer completes the demanding press style and separately stops before completion
Then: the complete demanding input emits the action input carrying the action at controls.queue-command-active
the incomplete demanding input emits no action input from this contract
an observer, not the running game, judges this
Diagnostics: rts-pointer-pc-queue-command-modifier-hold-observer-result
rts-pointer-match-trace
rts-pointer-action-input-log

demanding-required-required-motion-override

the required motion of `Row.id` follows required-as-written by its row answer

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches demanding-input required as written and motion-use required motion.

demanding-required-press-style-default

the demanding press style of `Row.id` follows required-as-written by the game default

scenarioper action-bindings row

Does not apply to rts-pointer: demanding input default is no demanding presses, not required as written.

demanding-required-required-motion-default

the required motion of `Row.id` follows required-as-written by the game default

scenarioper action-bindings row

Does not apply to rts-pointer: demanding input default is no demanding presses, not required as written.

simpler-route-is-distinct

`Row.id` performs the same action without resembling a failed demanding input

scenarioper simpler-inputs row

Does not apply to rts-pointer: simpler-inputs has no rows.

device-motion-rule-holds · pc-select-area-primary-drag

`pc-select-area-primary-drag` follows its `no-motion` device-motion rule

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

For pc-select-area-primary-drag under controls.pointer-primary-drag-activation: no device motion is read while the cited non-motion performance emits the action input. The test names the address, restates nothing from it, and asserts nothing about device-motion quality.

Test steps and diagnostics

Given: binding pc-select-area-primary-drag and its physical input and device at controls.pointer-primary-drag-activation
When: the cited performance and the corresponding motion or non-motion comparison are each attempted
Then: no device motion is read while the cited non-motion performance emits the action input
the test asserts nothing about device-motion quality
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

device-motion-rule-holds · pc-context-order-secondary-release

`pc-context-order-secondary-release` follows its `no-motion` device-motion rule

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

For pc-context-order-secondary-release under controls.pointer-secondary-release-activation: no device motion is read while the cited non-motion performance emits the action input. The test names the address, restates nothing from it, and asserts nothing about device-motion quality.

Test steps and diagnostics

Given: binding pc-context-order-secondary-release and its physical input and device at controls.pointer-secondary-release-activation
When: the cited performance and the corresponding motion or non-motion comparison are each attempted
Then: no device motion is read while the cited non-motion performance emits the action input
the test asserts nothing about device-motion quality
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

device-motion-rule-holds · pc-queue-command-modifier-hold

`pc-queue-command-modifier-hold` follows its `no-motion` device-motion rule

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

For pc-queue-command-modifier-hold under controls.queue-modifier-key-hold: no device motion is read while the cited non-motion performance emits the action input. The test names the address, restates nothing from it, and asserts nothing about device-motion quality.

Test steps and diagnostics

Given: binding pc-queue-command-modifier-hold and its physical input and device at controls.queue-modifier-key-hold
When: the cited performance and the corresponding motion or non-motion comparison are each attempted
Then: no device motion is read while the cited non-motion performance emits the action input
the test asserts nothing about device-motion quality
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

device-motion-rule-holds · pc-edge-pan-pointer-edge

`pc-edge-pan-pointer-edge` follows its `no-motion` device-motion rule

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

For pc-edge-pan-pointer-edge under controls.pointer-edge-activation: no device motion is read while the cited non-motion performance emits the action input. The test names the address, restates nothing from it, and asserts nothing about device-motion quality.

Test steps and diagnostics

Given: binding pc-edge-pan-pointer-edge and its physical input and device at controls.pointer-edge-activation
When: the cited performance and the corresponding motion or non-motion comparison are each attempted
Then: no device motion is read while the cited non-motion performance emits the action input
the test asserts nothing about device-motion quality
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

device-motion-rule-holds · pc-zoom-in-wheel-forward

`pc-zoom-in-wheel-forward` follows its `no-motion` device-motion rule

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

For pc-zoom-in-wheel-forward under controls.zoom-in-wheel-activation: no device motion is read while the cited non-motion performance emits the action input. The test names the address, restates nothing from it, and asserts nothing about device-motion quality.

Test steps and diagnostics

Given: binding pc-zoom-in-wheel-forward and its physical input and device at controls.zoom-in-wheel-activation
When: the cited performance and the corresponding motion or non-motion comparison are each attempted
Then: no device motion is read while the cited non-motion performance emits the action input
the test asserts nothing about device-motion quality
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

device-motion-rule-holds · pc-zoom-out-wheel-back

`pc-zoom-out-wheel-back` follows its `no-motion` device-motion rule

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

For pc-zoom-out-wheel-back under controls.zoom-out-wheel-activation: no device motion is read while the cited non-motion performance emits the action input. The test names the address, restates nothing from it, and asserts nothing about device-motion quality.

Test steps and diagnostics

Given: binding pc-zoom-out-wheel-back and its physical input and device at controls.zoom-out-wheel-activation
When: the cited performance and the corresponding motion or non-motion comparison are each attempted
Then: no device motion is read while the cited non-motion performance emits the action input
the test asserts nothing about device-motion quality
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log

one-physical-activation-emits-one-action-input

one physical activation emits one action input with all matched candidates

scenarioonce

Applies to rts-pointer.

Each reachable physical activation emits one action input carrying every matched binding's action as a candidate. N matched actions remain one input with N candidates, never N inputs. Where no activation matches several bindings, that comparison asserts nothing.

Test steps and diagnostics

Given: each reachable physical activation in the rts-pointer adoption, including one that matches several bindings where the adoption declares one
When: the current set is matched and the contract emits its game-facing result
Then: the activation emits one action input
that one input carries every matched binding's action as a candidate
N matched actions remain one input with N candidates and never become N inputs
where no activation matches several bindings, the multi-candidate comparison asserts nothing
Diagnostics: rts-pointer-match-trace
rts-pointer-action-input-log
rts-pointer-candidate-set

action-input-stops-at-handoff

the action input stops at the contract boundary

scenarioonce

Applies to rts-pointer.

The contract emits one action input with all matched candidates and stops there. Input forgiveness can supply the accepted moment; Action legibility, when adopted, selects a candidate before one action proposal. Otherwise the game's cited Fixed selection rule owns shared-candidate selection. This test asserts nothing about forgiveness windows, offered-action presentation, candidate ordering, proposal rejection, or action effects.

Test steps and diagnostics

Given: one action input emitted by the rts-pointer adoption with all matched candidates
When: the input crosses the contract boundary
Then: the emitted input is handed to Input forgiveness when adopted, which can supply the accepted moment, and then to Action legibility when adopted for candidate selection before one action proposal
without Action legibility, the game's cited Fixed selection rule owns shared-candidate selection
this test stops at emission and asserts nothing about forgiveness windows, offered-action presentation, candidate ordering, proposal rejection, or action effects
Diagnostics: rts-pointer-action-input-log

control-options-authority-order

control options keeps its authority order

scenarioonce

Applies to rts-pointer.

The authority order is platform, defaults, starting set, accepted control change, current set, physical match, demanding-input answer, simpler route, device-motion rule, one action-input creation, accepted-moment shared-action choice, and one action proposal. A later stage does not rewrite an earlier decision.

Test steps and diagnostics

Given: a run that reaches platform selection, control setup, a physical activation, and the action-input boundary
When: the decision trace is read in order
Then: the trace orders platform, defaults, starting set, accepted control change, current set, physical match, demanding-input answer, simpler route, device-motion rule, one action-input creation, accepted-moment shared-action choice, and one action proposal
a later stage does not rewrite an earlier decision
Diagnostics: rts-pointer-platform-selection
rts-pointer-change-log
rts-pointer-current-set
rts-pointer-match-trace
rts-pointer-action-input-log

control-options-boundaries

the adoption makes no promise beyond control options

scenarioonce

Applies to rts-pointer.

The contract asserts nothing about system-level remapping, virtual-control layout editing, chord member lists, device-motion quality, or saved profiles. Moving or resizing a touch control while keeping its action is not a control change. Presentation of the current binding is owned by Action legibility when adopted, otherwise by the game's UI rules. Beyond its stated hand-off order, the contract asserts nothing about an action input after emission.

Test steps and diagnostics

Given: the rts-pointer adoption and features adjacent to its control rules
When: the adoption's promise boundary is reviewed
Then: the contract asserts nothing about system-level remapping, virtual-control layout editing, chord member lists, device-motion quality, or saved profiles
moving or resizing a touch control while keeping its action is not a control change
presentation of the current binding is owned by Action legibility when adopted, otherwise by the game's UI rules
the contract asserts nothing about action-input behavior after emission except the stated hand-off order
Diagnostics: rts-pointer-declaration-record

empty-row-sets-make-no-promise

empty row sets and unanswered defaults make no promise

scenarioonce

Applies to rts-pointer.

This declaration check reads the adoption, not the running game. Where no platform row exists, no platform receives a physical-control promise, and the adoption makes no game-wide remapping or demanding-input promise; where a platform row exists, each clause asserts nothing. Where no preset, binding, or simpler-input row exists, its row set makes its stated empty-set promise; where a row exists, that clause asserts nothing.

Test steps and diagnostics

Given: the rts-pointer adoption, not the running game
When: a reviewer checks each row set and the two defaults that depend on a platform row
Then: where no platform-control-sets row exists, no platform receives a physical-control promise from this adoption; where a row exists, this clause asserts nothing
where no control-presets row exists, no named control preset is offered; where a row exists, this clause asserts nothing
where no action-bindings row exists, no physical input is promised to produce a game action; where a row exists, this clause asserts nothing
where no simpler-inputs row exists, no demanding binding promises a separate simpler input without a setting change; where a row exists, this clause asserts nothing
where no platform-control-sets row exists, this adoption makes no game-wide remapping promise; where a platform row exists, this clause asserts nothing
where no platform-control-sets row exists, this adoption makes no game-wide demanding-input promise; where a platform row exists, this clause asserts nothing
Diagnostics: rts-pointer-declaration-record

preset-platform-join

declaration check: preset `Row.id` names a platform row in this adoption

scenarioper control-presets row

Does not apply to rts-pointer: control-presets has no rows.

binding-platform-join · pc-select-area-primary-drag

declaration check: binding `pc-select-area-primary-drag` names a platform row in this adoption

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

This declaration check reads the adoption, not the running game. Binding pc-select-area-primary-drag must name an existing platform-control-sets row in this adoption: pc. A missing or misspelled join is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-select-area-primary-drag, not the running game
When: a reviewer checks its platform-control-set join
Then: a platform-control-sets row with id pc exists in this adoption
a missing or misspelled platform row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-platform-join · pc-context-order-secondary-release

declaration check: binding `pc-context-order-secondary-release` names a platform row in this adoption

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

This declaration check reads the adoption, not the running game. Binding pc-context-order-secondary-release must name an existing platform-control-sets row in this adoption: pc. A missing or misspelled join is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-context-order-secondary-release, not the running game
When: a reviewer checks its platform-control-set join
Then: a platform-control-sets row with id pc exists in this adoption
a missing or misspelled platform row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-platform-join · pc-queue-command-modifier-hold

declaration check: binding `pc-queue-command-modifier-hold` names a platform row in this adoption

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

This declaration check reads the adoption, not the running game. Binding pc-queue-command-modifier-hold must name an existing platform-control-sets row in this adoption: pc. A missing or misspelled join is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-queue-command-modifier-hold, not the running game
When: a reviewer checks its platform-control-set join
Then: a platform-control-sets row with id pc exists in this adoption
a missing or misspelled platform row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-platform-join · pc-edge-pan-pointer-edge

declaration check: binding `pc-edge-pan-pointer-edge` names a platform row in this adoption

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

This declaration check reads the adoption, not the running game. Binding pc-edge-pan-pointer-edge must name an existing platform-control-sets row in this adoption: pc. A missing or misspelled join is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-edge-pan-pointer-edge, not the running game
When: a reviewer checks its platform-control-set join
Then: a platform-control-sets row with id pc exists in this adoption
a missing or misspelled platform row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-platform-join · pc-zoom-in-wheel-forward

declaration check: binding `pc-zoom-in-wheel-forward` names a platform row in this adoption

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

This declaration check reads the adoption, not the running game. Binding pc-zoom-in-wheel-forward must name an existing platform-control-sets row in this adoption: pc. A missing or misspelled join is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-zoom-in-wheel-forward, not the running game
When: a reviewer checks its platform-control-set join
Then: a platform-control-sets row with id pc exists in this adoption
a missing or misspelled platform row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-platform-join · pc-zoom-out-wheel-back

declaration check: binding `pc-zoom-out-wheel-back` names a platform row in this adoption

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

This declaration check reads the adoption, not the running game. Binding pc-zoom-out-wheel-back must name an existing platform-control-sets row in this adoption: pc. A missing or misspelled join is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-zoom-out-wheel-back, not the running game
When: a reviewer checks its platform-control-set join
Then: a platform-control-sets row with id pc exists in this adoption
a missing or misspelled platform row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-preset-join

declaration check: binding `Row.id` names a preset on the same platform

scenarioper action-bindings row

Does not apply to rts-pointer: no matching row in action-bindings has every field this test uses (preset).

optional-motion-has-no-motion-sibling

declaration check: optional-motion binding `Row.id` has a no-motion sibling

scenarioper action-bindings row

Does not apply to rts-pointer: no row in action-bindings matches motion-use optional motion.

simpler-binding-join

declaration check: simpler route `Row.id` names a binding in this adoption

scenarioper simpler-inputs row

Does not apply to rts-pointer: simpler-inputs has no rows.

presets-only-has-complete-choice

declaration check: every presets-only platform has two selectable complete presets

scenarioonce

Applies to rts-pointer.

This declaration check reads the adoption, not the running game. Under the contract, every platform whose effective answer is presets-only must have at least two presets whose availability is starting-and-selectable or player-selectable, and every preset maps every action bound on that platform. Another effective answer asserts nothing in this comparison. A missing choice or incomplete preset is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, not the running game
When: a reviewer resolves each platform row's effective remapping answer and compares its preset and binding rows
Then: each platform whose effective answer is presets-only has at least two control-presets rows whose availability is starting-and-selectable or player-selectable
every preset for that platform maps every action bound on the platform with a matching action-bindings row
a platform with another effective answer asserts nothing in this comparison
a missing choice or incomplete preset is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

simpler-answer-has-row · pc-select-area-primary-drag

declaration check: every demanding simpler-alternative binding has a simpler row

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

This declaration check reads the adoption, not the running game. If pc-select-area-primary-drag has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise the requirement asserts nothing. A missing simpler row is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-select-area-primary-drag, not the running game
When: a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
Then: if pc-select-area-primary-drag has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it
otherwise this requirement asserts nothing
a missing simpler row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

simpler-answer-has-row · pc-context-order-secondary-release

declaration check: every demanding simpler-alternative binding has a simpler row

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

This declaration check reads the adoption, not the running game. If pc-context-order-secondary-release has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise the requirement asserts nothing. A missing simpler row is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-context-order-secondary-release, not the running game
When: a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
Then: if pc-context-order-secondary-release has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it
otherwise this requirement asserts nothing
a missing simpler row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

simpler-answer-has-row · pc-queue-command-modifier-hold

declaration check: every demanding simpler-alternative binding has a simpler row

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

This declaration check reads the adoption, not the running game. If pc-queue-command-modifier-hold has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise the requirement asserts nothing. A missing simpler row is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-queue-command-modifier-hold, not the running game
When: a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
Then: if pc-queue-command-modifier-hold has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it
otherwise this requirement asserts nothing
a missing simpler row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

simpler-answer-has-row · pc-edge-pan-pointer-edge

declaration check: every demanding simpler-alternative binding has a simpler row

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

This declaration check reads the adoption, not the running game. If pc-edge-pan-pointer-edge has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise the requirement asserts nothing. A missing simpler row is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-edge-pan-pointer-edge, not the running game
When: a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
Then: if pc-edge-pan-pointer-edge has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it
otherwise this requirement asserts nothing
a missing simpler row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

simpler-answer-has-row · pc-zoom-in-wheel-forward

declaration check: every demanding simpler-alternative binding has a simpler row

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

This declaration check reads the adoption, not the running game. If pc-zoom-in-wheel-forward has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise the requirement asserts nothing. A missing simpler row is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-zoom-in-wheel-forward, not the running game
When: a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
Then: if pc-zoom-in-wheel-forward has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it
otherwise this requirement asserts nothing
a missing simpler row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

simpler-answer-has-row · pc-zoom-out-wheel-back

declaration check: every demanding simpler-alternative binding has a simpler row

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

This declaration check reads the adoption, not the running game. If pc-zoom-out-wheel-back has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise the requirement asserts nothing. A missing simpler row is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and binding pc-zoom-out-wheel-back, not the running game
When: a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
Then: if pc-zoom-out-wheel-back has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it
otherwise this requirement asserts nothing
a missing simpler row is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

no-demanding-answer-has-ordinary-route · pc-select-area-primary-drag

declaration check: every no-demanding binding has an ordinary route

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, pc-select-area-primary-drag must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Another answer asserts nothing here. A demanding-only route is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, binding pc-select-area-primary-drag, and its cited prose, not the running game
When: a reviewer resolves the binding's effective demanding-input answer
Then: if the effective answer is no-demanding-presses, pc-select-area-primary-drag has a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action
otherwise this requirement asserts nothing
a demanding-only route is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

no-demanding-answer-has-ordinary-route · pc-context-order-secondary-release

declaration check: every no-demanding binding has an ordinary route

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, pc-context-order-secondary-release must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Another answer asserts nothing here. A demanding-only route is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, binding pc-context-order-secondary-release, and its cited prose, not the running game
When: a reviewer resolves the binding's effective demanding-input answer
Then: if the effective answer is no-demanding-presses, pc-context-order-secondary-release has a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action
otherwise this requirement asserts nothing
a demanding-only route is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

no-demanding-answer-has-ordinary-route · pc-queue-command-modifier-hold

declaration check: every no-demanding binding has an ordinary route

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, pc-queue-command-modifier-hold must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Another answer asserts nothing here. A demanding-only route is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, binding pc-queue-command-modifier-hold, and its cited prose, not the running game
When: a reviewer resolves the binding's effective demanding-input answer
Then: if the effective answer is no-demanding-presses, pc-queue-command-modifier-hold has a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action
otherwise this requirement asserts nothing
a demanding-only route is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

no-demanding-answer-has-ordinary-route · pc-edge-pan-pointer-edge

declaration check: every no-demanding binding has an ordinary route

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, pc-edge-pan-pointer-edge must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Another answer asserts nothing here. A demanding-only route is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, binding pc-edge-pan-pointer-edge, and its cited prose, not the running game
When: a reviewer resolves the binding's effective demanding-input answer
Then: if the effective answer is no-demanding-presses, pc-edge-pan-pointer-edge has a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action
otherwise this requirement asserts nothing
a demanding-only route is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

no-demanding-answer-has-ordinary-route · pc-zoom-in-wheel-forward

declaration check: every no-demanding binding has an ordinary route

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, pc-zoom-in-wheel-forward must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Another answer asserts nothing here. A demanding-only route is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, binding pc-zoom-in-wheel-forward, and its cited prose, not the running game
When: a reviewer resolves the binding's effective demanding-input answer
Then: if the effective answer is no-demanding-presses, pc-zoom-in-wheel-forward has a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action
otherwise this requirement asserts nothing
a demanding-only route is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

no-demanding-answer-has-ordinary-route · pc-zoom-out-wheel-back

declaration check: every no-demanding binding has an ordinary route

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, pc-zoom-out-wheel-back must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Another answer asserts nothing here. A demanding-only route is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, binding pc-zoom-out-wheel-back, and its cited prose, not the running game
When: a reviewer resolves the binding's effective demanding-input answer
Then: if the effective answer is no-demanding-presses, pc-zoom-out-wheel-back has a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action
otherwise this requirement asserts nothing
a demanding-only route is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

forbidden-effective-pair-does-not-reappear

declaration check: no platform or binding recreates the forbidden effective pair

scenarioonce

Applies to rts-pointer.

This declaration check reads the adoption, not the running game. The contract's demanding-input field forbids a binding from having effective required-as-written on a platform with effective action-and-press-style. A row override that recreates this forbidden pair is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption, not the running game
When: a reviewer resolves every platform's effective remapping answer and every binding's effective demanding-input answer
Then: no binding has effective required-as-written on a platform with effective action-and-press-style
any platform-row or binding-row override that recreates that pair is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

settings-citation-covers-effective-change-policy · pc

declaration check: `pc`'s settings citation covers its effective policy

scenarioper platform-control-sets row

Applies to the pc row.

This declaration check reads the adoption and controls.pc-remapping-and-conflicts, not the running game. Under any-action-any-input or action-and-press-style, that citation must state visible conflict handling before use; action-and-press-style must also state the press styles offered for each action. Under swap-only, it must state that a swap exchanges two existing assignments. Under presets-only, it must state that selection replaces the whole set and an individual binding change is refused. Under fixed-bindings, it must state the absence of changes. A missing duty is a defect this test fails by construction, and the test asserts nothing about reachability beyond what the citation states.

Test steps and diagnostics

Given: the rts-pointer adoption, platform row pc, and controls.pc-remapping-and-conflicts, not the running game
When: a reviewer resolves the row's effective remapping answer and checks the cited rule
Then: under any-action-any-input or action-and-press-style, the citation states visible conflict handling before use
under action-and-press-style, the citation states the press styles offered for each action
under swap-only, the citation states that a swap exchanges two existing assignments
under presets-only, the citation states that selection replaces the whole set and an individual binding change is refused
under fixed-bindings, the citation states the absence of changes
a missing duty is a defect this test fails by construction
the test asserts nothing about reachability beyond what the citation states
Diagnostics: rts-pointer-declaration-record

shared-action-input-declaration-agrees

declaration check: rows sharing an activation agree on one action input

scenarioonce

Applies to rts-pointer.

This declaration check reads the adoption and its cited physical activations and contexts, not the running game. Under the contract, one group contains only rows that can be current together: they use the same platform row, either all omit a preset or all name the same preset, have no disjoint cited contexts, and share one physical activation. Rows in mutually exclusive presets or disjoint contexts are not one group and assert nothing about each other's action-input value. Every row in a multi-binding group supplies and agrees on one value, and the emitted input carries every matched action as a candidate. A lone binding's name can remain implicit and asserts nothing in the shared-value comparison. A missing, different, or split value is a defect this test fails by construction. The check asserts nothing about a paired Action legibility adoption.

Test steps and diagnostics

Given: the rts-pointer adoption and the physical activations, platforms, presets, and contexts described by its binding rows and citations, not the running game
When: a reviewer groups rows that can be current together and share one physical activation
Then: one group contains only rows on the same platform row that either all omit a preset or all name the same preset, have no disjoint cited contexts, and share one physical activation
rows in mutually exclusive presets or disjoint cited contexts are not one group and assert nothing about each other's action-input value
every group with several bindings supplies one action-input value shared by every row in that group
the emitted input carries every matched binding's action as a candidate
a lone binding's action-input name can remain implicit and asserts nothing in the shared-value comparison
a missing, different, or split shared value is a defect this test fails by construction
the test asserts nothing about a paired Action legibility adoption
Diagnostics: rts-pointer-declaration-record
rts-pointer-candidate-set

rows-do-not-duplicate-meaning

declaration check: no two rows mean the same platform, preset, or binding

scenarioonce

Applies to rts-pointer.

This declaration check reads the adoption and its cited prose, not the running game. No two rows can mean the same platform, preset, binding, or simpler alternative for one binding. The contract sets no maximum row count. A duplicate meaning is a defect this test fails by construction.

Test steps and diagnostics

Given: the rts-pointer adoption and its cited prose, not the running game
When: a reviewer compares every pair of rows in each row set
Then: no two platform-control-sets rows mean the same platform, edition, devices, and policy scope
no two control-presets rows mean the same preset
no two action-bindings rows mean the same binding
no two simpler-inputs rows mean the same alternative for one binding
the contract imposes no maximum row count
a duplicate meaning is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

platform-citation-duty · pc

declaration check: `pc`'s platform citation states its duty

scenarioper platform-control-sets row

Applies to the pc row.

This declaration check reads the adoption and platforms.pc, not the running game. The citation must name one platform or edition and its supported devices; different control behavior belongs in another row. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and platforms.pc, not the running game
When: a reviewer checks the citation's meaning
Then: platforms.pc names one platform or edition and its supported devices, with different control behavior in another row
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

methods-citation-duty · pc

declaration check: `pc`'s methods citation states its duty

scenarioper platform-control-sets row

Applies to the pc row.

This declaration check reads the adoption and controls.pc-keyboard-and-pointer, not the running game. The citation must list every complete input method for pc and any required switch. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.pc-keyboard-and-pointer, not the running game
When: a reviewer checks the citation's meaning
Then: controls.pc-keyboard-and-pointer lists every complete input method for pc and any required switch between methods
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

settings-rule-citation-duty · pc

declaration check: `pc`'s settings citation states its duty

scenarioper platform-control-sets row

Applies to the pc row.

This declaration check reads the adoption and controls.pc-remapping-and-conflicts, not the running game. The citation must always state pc's control menu. Where the platform declares a preset, it must state preset selection. Under effective any-action-any-input or action-and-press-style, it must state conflict handling; action-and-press-style must also state the press styles offered for each action. Under effective fixed-bindings, it must state the explicit absence of changes. A duty outside its stated condition asserts nothing. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.pc-remapping-and-conflicts, not the running game
When: a reviewer resolves pc's effective remapping answer and checks the citation's meaning
Then: controls.pc-remapping-and-conflicts states pc's control menu
where the platform has a control-presets row, the citation states preset selection; where it has none, this clause asserts nothing
under effective any-action-any-input or action-and-press-style, the citation states conflict handling; under another effective answer, this clause asserts nothing
under effective action-and-press-style, the citation states the press styles offered for each action; under another effective answer, this clause asserts nothing
under effective fixed-bindings, the citation states the explicit absence of changes; under another effective answer, this clause asserts nothing
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

preset-selection-citation-duty

declaration check: preset `Row.id`'s selection citation states its duty

scenarioper control-presets row

Does not apply to rts-pointer: control-presets has no rows.

binding-action-citation-duty · pc-select-area-primary-drag

declaration check: `pc-select-area-primary-drag`'s action citation states its duty

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

This declaration check reads the adoption and controls.selection-drag, not the running game. The citation must name the game-facing action that pc-select-area-primary-drag contributes as a candidate. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.selection-drag, not the running game
When: a reviewer checks the citation's meaning
Then: controls.selection-drag names the game-facing action that pc-select-area-primary-drag contributes as a candidate
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-action-citation-duty · pc-context-order-secondary-release

declaration check: `pc-context-order-secondary-release`'s action citation states its duty

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

This declaration check reads the adoption and controls.context-order, not the running game. The citation must name the game-facing action that pc-context-order-secondary-release contributes as a candidate. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.context-order, not the running game
When: a reviewer checks the citation's meaning
Then: controls.context-order names the game-facing action that pc-context-order-secondary-release contributes as a candidate
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-action-citation-duty · pc-queue-command-modifier-hold

declaration check: `pc-queue-command-modifier-hold`'s action citation states its duty

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

This declaration check reads the adoption and controls.queue-command-active, not the running game. The citation must name the game-facing action that pc-queue-command-modifier-hold contributes as a candidate. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.queue-command-active, not the running game
When: a reviewer checks the citation's meaning
Then: controls.queue-command-active names the game-facing action that pc-queue-command-modifier-hold contributes as a candidate
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-action-citation-duty · pc-edge-pan-pointer-edge

declaration check: `pc-edge-pan-pointer-edge`'s action citation states its duty

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

This declaration check reads the adoption and controls.tactical-edge-pan-action, not the running game. The citation must name the game-facing action that pc-edge-pan-pointer-edge contributes as a candidate. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.tactical-edge-pan-action, not the running game
When: a reviewer checks the citation's meaning
Then: controls.tactical-edge-pan-action names the game-facing action that pc-edge-pan-pointer-edge contributes as a candidate
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-action-citation-duty · pc-zoom-in-wheel-forward

declaration check: `pc-zoom-in-wheel-forward`'s action citation states its duty

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

This declaration check reads the adoption and controls.tactical-zoom-actions-and-range, not the running game. The citation must name the game-facing action that pc-zoom-in-wheel-forward contributes as a candidate. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.tactical-zoom-actions-and-range, not the running game
When: a reviewer checks the citation's meaning
Then: controls.tactical-zoom-actions-and-range names the game-facing action that pc-zoom-in-wheel-forward contributes as a candidate
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-action-citation-duty · pc-zoom-out-wheel-back

declaration check: `pc-zoom-out-wheel-back`'s action citation states its duty

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

This declaration check reads the adoption and controls.tactical-zoom-actions-and-range, not the running game. The citation must name the game-facing action that pc-zoom-out-wheel-back contributes as a candidate. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.tactical-zoom-actions-and-range, not the running game
When: a reviewer checks the citation's meaning
Then: controls.tactical-zoom-actions-and-range names the game-facing action that pc-zoom-out-wheel-back contributes as a candidate
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-physical-input-citation-duty · pc-select-area-primary-drag

declaration check: `pc-select-area-primary-drag`'s physical-input citation states its duty

scenarioper action-bindings row

Applies to the pc-select-area-primary-drag row.

This declaration check reads the adoption and controls.pointer-primary-drag-activation, not the running game. The citation must name pc-select-area-primary-drag's physical input, supplying device, and the gesture completion. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.pointer-primary-drag-activation, not the running game
When: a reviewer checks the citation's meaning
Then: controls.pointer-primary-drag-activation names the physical input, its supplying device, and the gesture completion for pc-select-area-primary-drag
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-physical-input-citation-duty · pc-context-order-secondary-release

declaration check: `pc-context-order-secondary-release`'s physical-input citation states its duty

scenarioper action-bindings row

Applies to the pc-context-order-secondary-release row.

This declaration check reads the adoption and controls.pointer-secondary-release-activation, not the running game. The citation must name pc-context-order-secondary-release's physical input, supplying device, and the release performance. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.pointer-secondary-release-activation, not the running game
When: a reviewer checks the citation's meaning
Then: controls.pointer-secondary-release-activation names the physical input, its supplying device, and the release performance for pc-context-order-secondary-release
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-physical-input-citation-duty · pc-queue-command-modifier-hold

declaration check: `pc-queue-command-modifier-hold`'s physical-input citation states its duty

scenarioper action-bindings row

Applies to the pc-queue-command-modifier-hold row.

This declaration check reads the adoption and controls.queue-modifier-key-hold, not the running game. The citation must name pc-queue-command-modifier-hold's physical input, supplying device, and the hold completion. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.queue-modifier-key-hold, not the running game
When: a reviewer checks the citation's meaning
Then: controls.queue-modifier-key-hold names the physical input, its supplying device, and the hold completion for pc-queue-command-modifier-hold
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-physical-input-citation-duty · pc-edge-pan-pointer-edge

declaration check: `pc-edge-pan-pointer-edge`'s physical-input citation states its duty

scenarioper action-bindings row

Applies to the pc-edge-pan-pointer-edge row.

This declaration check reads the adoption and controls.pointer-edge-activation, not the running game. The citation must name pc-edge-pan-pointer-edge's physical input, supplying device, and the gesture completion. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.pointer-edge-activation, not the running game
When: a reviewer checks the citation's meaning
Then: controls.pointer-edge-activation names the physical input, its supplying device, and the gesture completion for pc-edge-pan-pointer-edge
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-physical-input-citation-duty · pc-zoom-in-wheel-forward

declaration check: `pc-zoom-in-wheel-forward`'s physical-input citation states its duty

scenarioper action-bindings row

Applies to the pc-zoom-in-wheel-forward row.

This declaration check reads the adoption and controls.zoom-in-wheel-activation, not the running game. The citation must name pc-zoom-in-wheel-forward's physical input, supplying device, and the press performance. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.zoom-in-wheel-activation, not the running game
When: a reviewer checks the citation's meaning
Then: controls.zoom-in-wheel-activation names the physical input, its supplying device, and the press performance for pc-zoom-in-wheel-forward
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-physical-input-citation-duty · pc-zoom-out-wheel-back

declaration check: `pc-zoom-out-wheel-back`'s physical-input citation states its duty

scenarioper action-bindings row

Applies to the pc-zoom-out-wheel-back row.

This declaration check reads the adoption and controls.zoom-out-wheel-activation, not the running game. The citation must name pc-zoom-out-wheel-back's physical input, supplying device, and the press performance. A missing duty is a defect this test fails by construction. The test names the address and restates nothing from it.

Test steps and diagnostics

Given: the rts-pointer adoption and controls.zoom-out-wheel-activation, not the running game
When: a reviewer checks the citation's meaning
Then: controls.zoom-out-wheel-activation names the physical input, its supplying device, and the press performance for pc-zoom-out-wheel-back
a missing duty is a defect this test fails by construction
Diagnostics: rts-pointer-declaration-record

binding-context-citation-duty

declaration check: `Row.id`'s context citation states its duty

scenarioper action-bindings row

Does not apply to rts-pointer: no matching row in action-bindings has every field this test uses (context-declared-in).

simpler-alternative-citation-duty

declaration check: `Row.id`'s alternative citation states its duty

scenarioper simpler-inputs row

Does not apply to rts-pointer: simpler-inputs has no rows.

simpler-distinction-citation-duty

declaration check: `Row.id`'s distinction citation states its duty

scenarioper simpler-inputs row

Does not apply to rts-pointer: simpler-inputs has no rows.

control-options-hold

control options holds for the whole run

generalonce

Applies to rts-pointer.

Across every platform row on its cited devices, every preset, every binding, and every simpler route of the audited run, every accepted control change follows the platform's effective remapping answer and every refused change is refused; every binding matches only under its cited performance and emits one action input; every demanding binding meets its effective answer; every simpler route produces the same action distinguishably; every device-motion rule holds; and no physical activation produces more than one action input.

Test steps and diagnostics

Holds: every accepted control change followed the platform's effective remapping answer and every refused change was refused; every binding matched only under its cited performance and emitted one action input; every demanding binding met its effective answer; every simpler route produced the same action distinguishably; every device-motion rule held; no physical activation produced more than one action input
Seeds: ["audit-a","audit-b"]
Scope: every platform row on its cited devices, every preset, every binding, and every simpler route of the audited run
Diagnostics: rts-pointer-platform-selection
rts-pointer-change-log
rts-pointer-current-set
rts-pointer-match-trace
rts-pointer-action-input-log
rts-pointer-observer-result
rts-pointer-setting-state

JSONthe adoption as one file

The adoption file as supplied. Answers you try on this page are not written into it; to change an adoption, open it in the authoring tool.

{
  "contract": "control-options",
  "version": 1,
  "summary": "Covers which physical inputs produce each action on every platform. It also covers complete input methods, named control presets, remapping, press styles, simpler alternatives, and device-motion inputs. Action prompts, input timing help, shared-action choice, and event order stay elsewhere.",
  "questions": {
    "remapping-default": {
      "asks": "How can players normally change the controls?",
      "rationale": "A platform may offer fixed controls, named layouts, or free changes. This answer supplies the ordinary choice before a platform states another one.",
      "when": {
        "row-count": {
          "platform-control-sets": "non-empty"
        }
      },
      "otherwise": "With no platform control set, this adoption makes no game-wide remapping promise.",
      "options": {
        "fixed-bindings": {
          "meaning": "The controls cannot be changed in the game. A puzzle game always keeps rotate on the space bar.",
          "semantics": "No player-facing setting changes an action's physical input or press style."
        },
        "swap-only": {
          "meaning": "Existing controls can only exchange actions. A platformer can swap jump and dash, but an unused button cannot receive either action.",
          "semantics": "A supported binding can exchange its current action with another supported binding; no action can move independently to an otherwise unused input."
        },
        "presets-only": {
          "meaning": "Players can choose only from named control sets. An action game offers Default and Alternate layouts without individual button changes.",
          "semantics": "The player may select a complete declared preset but cannot change one binding independently inside that preset. The platform offers at least two presets whose availability is starting-and-selectable or player-selectable."
        },
        "any-action-any-input": {
          "meaning": "Any action can move to any supported input. A strategy game can move end turn from Enter to an unused mouse button.",
          "semantics": "Every covered action can be assigned independently to any supported remappable input, including an otherwise unassigned input; conflicts are resolved visibly before use."
        },
        "action-and-press-style": {
          "meaning": "Both the input and the press style can change. An adventure game can move interact to another button and change a hold into one press.",
          "semantics": "Every covered action can change to a supported input and to any press style that its cited platform rule offers for that action."
        }
      }
    },
    "demanding-input-default": {
      "asks": "What normally happens when an action needs a difficult press?",
      "rationale": "Holds, rapid presses, double presses, and button combinations can block an otherwise known action. This answer supplies the ordinary choice.",
      "when": {
        "row-count": {
          "platform-control-sets": "non-empty"
        }
      },
      "otherwise": "With no platform control set, this adoption makes no game-wide demanding-input promise.",
      "options": {
        "no-demanding-presses": {
          "meaning": "No action needs a demanding press. A card game plays a selected card with one ordinary activation.",
          "semantics": "No covered binding requires timed, held, rapid, repeated, double, simultaneous, directional-sequence, or device-motion input as its only route to the action."
        },
        "simpler-alternative": {
          "meaning": "Every demanding press has a distinct simpler route with no setting change. A repair game offers a separate tap button beside its hold-to-repair control.",
          "semantics": "Every covered demanding binding has a declared alternative that performs the same action without configuration."
        },
        "player-can-change-it": {
          "meaning": "A setting can make the press easier. A racing game can change a held pit command into one ordinary press.",
          "semantics": "A player-facing setting replaces each covered demanding press with a declared easier press style before play uses the binding."
        },
        "required-as-written": {
          "meaning": "The demanding press remains required. A rhythm special still needs two buttons together and has no simpler route from this contract.",
          "semantics": "The covered demanding binding has no simpler alternative or press-style setting promised by this adoption."
        }
      }
    }
  },
  "declares": {
    "values": {},
    "rows": {
      "platform-control-sets": {
        "description": "Supported platforms or editions and their complete control policies. A separate row is required whenever mappings or options differ.",
        "when-empty": "No platform receives a physical-control promise from this adoption.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "A stable platform or edition name, such as pc or console-gamepad."
          },
          "platform-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed rule naming one platform or edition and its supported devices. Different control behavior requires another row."
          },
          "methods-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed list of complete input methods and any required switch between them. A PC row may name keyboard and pointer as one mixed method."
          },
          "input-method-coverage": {
            "type": "string",
            "required": true,
            "options": [
              "one-method-covers-all",
              "player-chooses-method",
              "mixed-methods-needed"
            ],
            "description": "Whether one named method covers every action bound on the platform, several named methods each do so, or the named methods must be mixed. A console may offer complete gamepad and accessibility-controller methods."
          },
          "remapping": {
            "type": "string",
            "required": true,
            "options": [
              "use-game-default",
              "fixed-bindings",
              "swap-only",
              "presets-only",
              "any-action-any-input",
              "action-and-press-style"
            ],
            "description": "The platform's remapping policy or the game's ordinary answer. A console edition may offer presets while the PC edition allows free assignment."
          },
          "settings-rule-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed rule for the platform's control menu and, as its effective remapping answer needs, preset selection, conflict handling, the press styles offered for each action, or the explicit absence of changes when bindings are fixed."
          }
        }
      },
      "control-presets": {
        "description": "Named complete binding sets offered on a platform. A preset maps every action bound on its platform.",
        "when-empty": "No named control preset is offered.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "A stable name for the preset, such as gamepad-default or gamepad-alternate."
          },
          "platform-control-set": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "description": "The supported platform or edition that offers this preset."
          },
          "label": {
            "type": "string",
            "required": true,
            "description": "The player-facing preset name, such as Standard or Southpaw."
          },
          "availability": {
            "type": "string",
            "required": true,
            "options": [
              "starting-and-selectable",
              "player-selectable",
              "mode-selected"
            ],
            "description": "Whether this preset is the starting set and remains selectable, is another selectable set, or follows a cited player mode. An assisted-play mode may select its own complete layout."
          },
          "selection-rule-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed route that selects this preset and makes its matching action-binding rows current."
          }
        }
      },
      "action-bindings": {
        "description": "Physical inputs that produce actions on a platform or inside one named preset.",
        "when-empty": "No physical input is promised to produce a game action.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "A stable platform, action, and input name, such as pc-jump-space. A per-character control set names the character too."
          },
          "platform-control-set": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "description": "The supported platform or edition where this binding exists."
          },
          "preset": {
            "type": "string",
            "pattern": "kebab-case",
            "description": "The named complete control set containing this binding. Absence means the platform's current base or freely remappable set. On a platform whose effective remapping allows changes, the preset is the starting source set and accepted changes mutate the current copy."
          },
          "context-declared-in": {
            "type": "citation",
            "description": "The Fixed context in which this binding exists, such as a vehicle layer, menu, training mode, or unlock gate. Absence means it exists throughout the selected control set."
          },
          "action-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed game-facing action this binding contributes as a candidate."
          },
          "physical-input-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed physical key, button, axis, touch region, gesture, directional sequence, or device-motion input and the device that supplies it."
          },
          "action-input": {
            "type": "string",
            "pattern": "kebab-case",
            "description": "The one game-facing input emitted by this physical activation. Name it when several bindings answer the same physical activation."
          },
          "press-style": {
            "type": "string",
            "required": true,
            "options": [
              "press",
              "release",
              "timed-press",
              "hold",
              "rapid-presses",
              "repeated-presses",
              "double-press",
              "simultaneous-inputs",
              "continuous-axis",
              "gesture",
              "input-sequence"
            ],
            "description": "The physical performance required by this binding. A timed press has a target moment, rapid presses have a rate, repeated presses have a count, and an input sequence is a directional sequence completed by a press."
          },
          "motion-use": {
            "type": "string",
            "required": true,
            "options": [
              "no-motion",
              "optional-motion",
              "required-motion"
            ],
            "description": "Whether this binding uses no device motion, is an optional device-motion route beside another binding, or requires device motion. A handheld aim action may offer tilt as an alternative to the stick. A required-motion binding is demanding by its motion, and a press-style setting does not relieve it, so its easier route is a simpler alternative or another binding. An optional-motion binding has a no-motion binding for the same action on the same platform and preset."
          },
          "demanding-input": {
            "type": "string",
            "required": true,
            "options": [
              "use-game-default",
              "no-demanding-presses",
              "simpler-alternative",
              "player-can-change-it",
              "required-as-written"
            ],
            "description": "The action binding's demanding-input answer or the game's ordinary answer. A repeated crafting input may allow a hold even when combat combinations remain fixed. No binding answers required-as-written on a platform whose effective remapping is action-and-press-style."
          }
        }
      },
      "simpler-inputs": {
        "description": "Distinct unconfigured alternatives for bindings whose effective demanding-input answer promises one.",
        "when-empty": "No demanding binding promises a separate simpler input without a setting change.",
        "record": {
          "id": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "unique": true,
            "description": "A stable alternative name, such as repair-tap-alternative."
          },
          "action-binding": {
            "type": "string",
            "required": true,
            "pattern": "kebab-case",
            "description": "The demanding binding for which this route is the simpler alternative."
          },
          "alternative-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed physical input and ordinary press style that perform the same game action without a setting change."
          },
          "distinction-rule-declared-in": {
            "type": "citation",
            "required": true,
            "description": "The Fixed rule proving that successful use of this alternative cannot be mistaken for failure to finish the demanding input."
          }
        }
      }
    }
  },
  "rules": {
    "press-style-change-needs-a-setting-answer": {
      "forbid": {
        "all": [
          {
            "flag": {
              "remapping-default": [
                "action-and-press-style"
              ]
            }
          },
          {
            "flag": {
              "demanding-input-default": [
                "required-as-written"
              ]
            }
          }
        ]
      },
      "message": "Controls that let players change a press style cannot also require every demanding press exactly as written."
    }
  },
  "origin": "https://opengdd.org/contracts/control-options-1",
  "mechanism": [
    "This is the single normative authority for platform selection, preset choice, remapping, physical-input matching, press style, simpler alternatives, device-motion use, and creation of game-facing action inputs. Questions and rows supply defaults and cited game rules; they do not define another sequence.",
    "A **control set** is the complete current mapping for one platform and input method. A **preset** is a named immutable source set that can become current. A **binding** joins one physical input and press style to one candidate action. An **action input** is the one game-facing signal emitted by a physical activation; it carries every matched binding's action as a candidate. Bindings that can be current together and share one physical activation share its optional `action-input` name, while a lone binding's name may remain implicit. A **demanding input** is a timed, held, rapid, repeated, double, simultaneous, input-sequence, or required-device-motion input.",
    "1. Select exactly one matching platform-control-set from the running platform, edition, and supported device rules. 2. Resolve the platform's effective remapping answer. A row value other than `use-game-default` wins; otherwise `remapping-default` applies. 3. Establish the starting control set from the platform's cited rule. When a preset is selected, copy its complete matching action-binding rows into the current set. The preset itself remains unchanged. 4. Apply control changes only through the effective remapping answer. Fixed bindings reject all changes. Swap-only exchanges two existing assignments. Presets-only replaces the whole set with another declared preset. Free assignment moves one action independently and resolves conflicts before use. Action-and-press-style also permits a supported press-style change. 5. After an accepted change, the resulting complete set becomes current. Every later binding lookup reads that set, and each binding row's promises follow its action to the input the current set assigns. Presentation of the current binding is owned by Action legibility when adopted, otherwise by the game's UI rules. 6. On physical input, read every binding with a matching physical input and performance in the current platform, device, method, and preset-derived set. A press, release, hold, repeated activation, double activation, simultaneous group, axis, gesture, directional input sequence, or device-motion input matches only under its cited Fixed rule. An optional binding context makes the match provisional: whether that context holds is settled at the accepted moment, once step 11's timing help fixes it. Rows that can be current together and share one physical activation agree on one `action-input` value. A physical input cited by a `simpler-inputs` row matches as if it were its named binding: it emits that binding's action input and contributes the same action. 7. Resolve the binding's effective demanding-input answer. A row value other than `use-game-default` wins; otherwise `demanding-input-default` applies. 8. Under no-demanding-presses, the covered action has an ordinary route. Under player-can-change-it, the selected setting supplies the easier current press style. Under required-as-written, an incomplete demanding input produces no action input from this contract. 9. Under simpler-alternative, the demanding route and every matching simpler row remain available together without configuration. The alternative produces the same action only through its distinct cited input; failure to finish the demanding route never becomes the alternative by itself. 10. A `no-motion` binding reads no device motion. An `optional-motion` binding contributes the same action as its non-device-motion alternative when its gesture completes. A `required-motion` binding produces no action input from a non-device-motion attempt. 11. Physical input → this contract emits the action input → Input forgiveness (when adopted) may shift the accepted moment → Action legibility (when adopted) selects the offered candidate at the accepted moment → one action proposal. Thus an interact buffered during a cutscene evaluates candidates in the situation where the input is accepted, not the situation where it was pressed. The emitted action input carries every matched binding's action as a candidate; it is one input with N candidates, never N inputs. 12. When Action legibility is adopted, its shared-input case consumes that one action input and selects one candidate. Otherwise the game's cited Fixed selection rule resolves shared candidates, and the game's UI rules own their presentation. Event resolution begins only after the one action proposal exists.",
    "The authority order is therefore: platform, defaults, starting set, accepted control change, current set, physical match, demanding-input answer, simpler route, device-motion rule, one action-input creation, accepted-moment shared-action choice, and one action proposal."
  ],
  "answers": {
    "remapping-default": "any-action-any-input",
    "demanding-input-default": "no-demanding-presses"
  },
  "values": {},
  "rows": {
    "platform-control-sets": [
      {
        "id": "pc",
        "platform-declared-in": "platforms.pc",
        "methods-declared-in": "controls.pc-keyboard-and-pointer",
        "input-method-coverage": "one-method-covers-all",
        "remapping": "use-game-default",
        "settings-rule-declared-in": "controls.pc-remapping-and-conflicts"
      }
    ],
    "control-presets": [],
    "action-bindings": [
      {
        "id": "pc-select-area-primary-drag",
        "platform-control-set": "pc",
        "action-declared-in": "controls.selection-drag",
        "physical-input-declared-in": "controls.pointer-primary-drag-activation",
        "press-style": "gesture",
        "motion-use": "no-motion",
        "demanding-input": "use-game-default"
      },
      {
        "id": "pc-context-order-secondary-release",
        "platform-control-set": "pc",
        "action-declared-in": "controls.context-order",
        "physical-input-declared-in": "controls.pointer-secondary-release-activation",
        "press-style": "release",
        "motion-use": "no-motion",
        "demanding-input": "use-game-default"
      },
      {
        "id": "pc-queue-command-modifier-hold",
        "platform-control-set": "pc",
        "action-declared-in": "controls.queue-command-active",
        "physical-input-declared-in": "controls.queue-modifier-key-hold",
        "press-style": "hold",
        "motion-use": "no-motion",
        "demanding-input": "required-as-written"
      },
      {
        "id": "pc-edge-pan-pointer-edge",
        "platform-control-set": "pc",
        "action-declared-in": "controls.tactical-edge-pan-action",
        "physical-input-declared-in": "controls.pointer-edge-activation",
        "press-style": "gesture",
        "motion-use": "no-motion",
        "demanding-input": "use-game-default"
      },
      {
        "id": "pc-zoom-in-wheel-forward",
        "platform-control-set": "pc",
        "action-declared-in": "controls.tactical-zoom-actions-and-range",
        "physical-input-declared-in": "controls.zoom-in-wheel-activation",
        "press-style": "press",
        "motion-use": "no-motion",
        "demanding-input": "use-game-default"
      },
      {
        "id": "pc-zoom-out-wheel-back",
        "platform-control-set": "pc",
        "action-declared-in": "controls.tactical-zoom-actions-and-range",
        "physical-input-declared-in": "controls.zoom-out-wheel-activation",
        "press-style": "press",
        "motion-use": "no-motion",
        "demanding-input": "use-game-default"
      }
    ],
    "simpler-inputs": []
  },
  "pack": "sha256:38a15db9590840c0b288298c204a1e2320ac8160bb99e0ff53997d3f65382cd6"
}

RTS pointer

Use in your game

The contract behind it

Questions

How can players normally change the controls?

What normally happens when an action needs a difficult press?

Platform control sets

Control presets

Action bindings

Simpler inputs

control options uses control sets, presets, bindings, action inputs, and demanding inputs

pc is selected exactly for its cited platform and devices

pc starts with the control set chosen by its cited rule

preset Row.id becomes current through its cited route

pc input methods cover its actions as promised

Row.id keeps fixed bindings by its row answer

Row.id keeps fixed bindings by the game default

Row.id permits only exchanges by its row answer

Row.id permits only exchanges by the game default

Row.id permits only preset selection by its row answer

Row.id permits only preset selection by the game default

Row.id permits free assignment by its row answer

pc permits free assignment by the game default

Row.id permits input and press-style changes by its row answer

Row.id permits input and press-style changes by the game default

pc-select-area-primary-drag exists in its declared control-set scope

pc-context-order-secondary-release exists in its declared control-set scope

pc-queue-command-modifier-hold exists in its declared control-set scope

pc-edge-pan-pointer-edge exists in its declared control-set scope

pc-zoom-in-wheel-forward exists in its declared control-set scope

pc-zoom-out-wheel-back exists in its declared control-set scope

pc-select-area-primary-drag matches only its cited gesture performance

pc-context-order-secondary-release matches only its cited release performance

pc-queue-command-modifier-hold matches only its cited hold performance

pc-edge-pan-pointer-edge matches only its cited gesture performance

pc-zoom-in-wheel-forward matches only its cited press performance

pc-zoom-out-wheel-back matches only its cited press performance

Row.id settles its context at the accepted moment

Row.id exists only while preset Bind preset is current

Row.id shares action input Bind action input consistently

Row.id matches as binding Row.action binding

Row.id has an ordinary route by its row answer

pc-select-area-primary-drag has an ordinary route by the game default

pc-context-order-secondary-release has an ordinary route by the game default

pc-edge-pan-pointer-edge has an ordinary route by the game default

pc-zoom-in-wheel-forward has an ordinary route by the game default

pc-zoom-out-wheel-back has an ordinary route by the game default

the demanding press style of Row.id follows simpler-alternative by its row answer

the required motion of Row.id follows simpler-alternative by its row answer

the demanding press style of Row.id follows simpler-alternative by the game default

the required motion of Row.id follows simpler-alternative by the game default

the demanding press style of Row.id follows player-can-change-it by its row answer

the required motion of Row.id follows player-can-change-it by its row answer

the demanding press style of Row.id follows player-can-change-it by the game default

the required motion of Row.id follows player-can-change-it by the game default

the demanding press style of pc-queue-command-modifier-hold follows required-as-written by its row answer

the required motion of Row.id follows required-as-written by its row answer

the demanding press style of Row.id follows required-as-written by the game default

the required motion of Row.id follows required-as-written by the game default

Row.id performs the same action without resembling a failed demanding input

pc-select-area-primary-drag follows its no-motion device-motion rule

pc-context-order-secondary-release follows its no-motion device-motion rule

pc-queue-command-modifier-hold follows its no-motion device-motion rule

pc-edge-pan-pointer-edge follows its no-motion device-motion rule

pc-zoom-in-wheel-forward follows its no-motion device-motion rule

pc-zoom-out-wheel-back follows its no-motion device-motion rule

one physical activation emits one action input with all matched candidates

the action input stops at the contract boundary

control options keeps its authority order

the adoption makes no promise beyond control options

empty row sets and unanswered defaults make no promise

declaration check: preset Row.id names a platform row in this adoption

declaration check: binding pc-select-area-primary-drag names a platform row in this adoption

declaration check: binding pc-context-order-secondary-release names a platform row in this adoption

declaration check: binding pc-queue-command-modifier-hold names a platform row in this adoption

declaration check: binding pc-edge-pan-pointer-edge names a platform row in this adoption

declaration check: binding pc-zoom-in-wheel-forward names a platform row in this adoption

declaration check: binding pc-zoom-out-wheel-back names a platform row in this adoption

declaration check: binding Row.id names a preset on the same platform

declaration check: optional-motion binding Row.id has a no-motion sibling

`pc` is selected exactly for its cited platform and devices

`pc` starts with the control set chosen by its cited rule

preset `Row.id` becomes current through its cited route

`pc` input methods cover its actions as promised

`Row.id` keeps fixed bindings by its row answer

`Row.id` keeps fixed bindings by the game default

`Row.id` permits only exchanges by its row answer

`Row.id` permits only exchanges by the game default

`Row.id` permits only preset selection by its row answer

`Row.id` permits only preset selection by the game default

`Row.id` permits free assignment by its row answer

`pc` permits free assignment by the game default

`Row.id` permits input and press-style changes by its row answer

`Row.id` permits input and press-style changes by the game default

`pc-select-area-primary-drag` exists in its declared control-set scope

`pc-context-order-secondary-release` exists in its declared control-set scope

`pc-queue-command-modifier-hold` exists in its declared control-set scope

`pc-edge-pan-pointer-edge` exists in its declared control-set scope

`pc-zoom-in-wheel-forward` exists in its declared control-set scope

`pc-zoom-out-wheel-back` exists in its declared control-set scope

`pc-select-area-primary-drag` matches only its cited `gesture` performance

`pc-context-order-secondary-release` matches only its cited `release` performance

`pc-queue-command-modifier-hold` matches only its cited `hold` performance

`pc-edge-pan-pointer-edge` matches only its cited `gesture` performance

`pc-zoom-in-wheel-forward` matches only its cited `press` performance

`pc-zoom-out-wheel-back` matches only its cited `press` performance

`Row.id` settles its context at the accepted moment

`Row.id` exists only while preset `Bind preset` is current

`Row.id` shares action input `Bind action input` consistently

`Row.id` matches as binding `Row.action binding`

`Row.id` has an ordinary route by its row answer

`pc-select-area-primary-drag` has an ordinary route by the game default

`pc-context-order-secondary-release` has an ordinary route by the game default

`pc-edge-pan-pointer-edge` has an ordinary route by the game default

`pc-zoom-in-wheel-forward` has an ordinary route by the game default

`pc-zoom-out-wheel-back` has an ordinary route by the game default

the demanding press style of `Row.id` follows simpler-alternative by its row answer

the required motion of `Row.id` follows simpler-alternative by its row answer

the demanding press style of `Row.id` follows simpler-alternative by the game default

the required motion of `Row.id` follows simpler-alternative by the game default

the demanding press style of `Row.id` follows player-can-change-it by its row answer

the required motion of `Row.id` follows player-can-change-it by its row answer

the demanding press style of `Row.id` follows player-can-change-it by the game default

the required motion of `Row.id` follows player-can-change-it by the game default

the demanding press style of `pc-queue-command-modifier-hold` follows required-as-written by its row answer

the required motion of `Row.id` follows required-as-written by its row answer

the demanding press style of `Row.id` follows required-as-written by the game default

the required motion of `Row.id` follows required-as-written by the game default

`Row.id` performs the same action without resembling a failed demanding input

`pc-select-area-primary-drag` follows its `no-motion` device-motion rule

`pc-context-order-secondary-release` follows its `no-motion` device-motion rule

`pc-queue-command-modifier-hold` follows its `no-motion` device-motion rule

`pc-edge-pan-pointer-edge` follows its `no-motion` device-motion rule

`pc-zoom-in-wheel-forward` follows its `no-motion` device-motion rule

`pc-zoom-out-wheel-back` follows its `no-motion` device-motion rule

declaration check: preset `Row.id` names a platform row in this adoption

declaration check: binding `pc-select-area-primary-drag` names a platform row in this adoption

declaration check: binding `pc-context-order-secondary-release` names a platform row in this adoption

declaration check: binding `pc-queue-command-modifier-hold` names a platform row in this adoption

declaration check: binding `pc-edge-pan-pointer-edge` names a platform row in this adoption

declaration check: binding `pc-zoom-in-wheel-forward` names a platform row in this adoption

declaration check: binding `pc-zoom-out-wheel-back` names a platform row in this adoption

declaration check: binding `Row.id` names a preset on the same platform

declaration check: optional-motion binding `Row.id` has a no-motion sibling

declaration check: simpler route `Row.id` names a binding in this adoption

declaration check: `pc`'s settings citation covers its effective policy

declaration check: `pc`'s platform citation states its duty

declaration check: `pc`'s methods citation states its duty

declaration check: `pc`'s settings citation states its duty

declaration check: preset `Row.id`'s selection citation states its duty

declaration check: `pc-select-area-primary-drag`'s action citation states its duty

declaration check: `pc-context-order-secondary-release`'s action citation states its duty

declaration check: `pc-queue-command-modifier-hold`'s action citation states its duty

declaration check: `pc-edge-pan-pointer-edge`'s action citation states its duty

declaration check: `pc-zoom-in-wheel-forward`'s action citation states its duty

declaration check: `pc-zoom-out-wheel-back`'s action citation states its duty

declaration check: `pc-select-area-primary-drag`'s physical-input citation states its duty

declaration check: `pc-context-order-secondary-release`'s physical-input citation states its duty

declaration check: `pc-queue-command-modifier-hold`'s physical-input citation states its duty

declaration check: `pc-edge-pan-pointer-edge`'s physical-input citation states its duty