MOBA selection and smart cast
moba-selection-and-smart-cast · an adoption of Pointer command, version 2
Use in your package
The first button opens the authoring tool with these answers and numbers already filled in. You still add the rules and tuning of your own game.
What is in the zip file
The zip file holds the adoption and its acceptance tests. In the authoring tool, choose Add contract and pick this zip file. If you edit your package outside the authoring tool, unpack the zip file in your package folder. The files of the zip file go into contracts/.
The contract that this adoption uses
This contract covers pointer gestures that select things in the world and issue commands to or at the world. It records direct world orders, chosen abilities and verbs, orders added to a queue, and cancellation. This contract does not cover physical bindings, the camera view, displayed information, pathfinding, unit AI, or formations. The Control options contract covers physical bindings, the Camera framing contract covers the camera view, and the Fact list contract covers displayed information.
Questions
The supplied answer is marked on each question. Pick other answers to see what changes. Nothing is saved here: the zip file and the authoring tool use the supplied answers.
Who receives a command made by pointing at the world?
Why this is asked
A pointer command may control one fixed actor, the current selection, or the place the pointer is on.
When the pointer just misses a target, what can it choose?
Why this is asked
The game can require the exact point or choose the nearest candidate inside a declared reach.
The player clicks or drags to select units, and nothing is there. What happens to the current selection?
- Asked when
- the selection gestures list has at least one row.
- If not asked
- No pointer gesture changes the current world selection.
Why this is asked
An empty click or box can clear the selection or leave the current selection in place. The answer applies only to selection gestures whose change is replace. When no such row exists, the answer has no effect.
The player points at an invalid target for the chosen ability or verb. Does the game keep waiting for another target?
- Asked when
- the targeted verbs list has at least one row.
- If not asked
- No chosen ability or verb waits for a world target from the pointer.
Why this is asked
The game can wait for the player to point again, or it can return to ordinary pointing.
The player holds the key that adds an order to the queue. Where does the new order go?
- Asked when
- the queue modifiers list has at least one row.
- If not asked
- No pointer modifier adds a command to a queue.
Why this is asked
The new order may wait at the end of the queue, or become the next order after the current one.
A new order arrives while another order is waiting. The player does not hold the key that adds an order to the queue. What happens?
- Asked when
- the context commands list has at least one row, or the targeted verbs list has at least one row.
- If not asked
- No pointer command can enter a queue.
Why this is asked
An order given without that key can replace the orders that wait in the queue, join the end of the queue, or be refused while its owner has an order waiting.
Numbersno numbers
This contract has no numbers to set.
Rulesno rules
A rule is a check between the numbers. Validation reports a rule that fails.
This contract has no rules between its numbers.
Lists5 lists
Each list holds the rows this adoption supplies. A list can be empty.
Selection gestures
selection-gestures
| Id | Gesture | Resolves on | Shape | Change | Gesture declared in | Candidates declared in |
|---|---|---|---|---|---|---|
add-ally-on-press | add-ally | press | point | add | controls.add-ally | units.ally-selection |
toggle-hero | toggle-hero | release | point | toggle | controls.toggle-hero | units.hero-selection |
remove-defeated-hero | remove-hero | release | point | remove | controls.remove-hero | units.defeated-hero-selection |
Context commands
context-commands
| Id | Gesture | Resolves on | Target kind | Command | Gesture declared in | Target declared in | Area declared in | Receiver condition | Command declared in |
|---|---|---|---|---|---|---|---|---|---|
move-hero-on-ground | hero-order | release | ground | move-hero | controls.hero-order | arena.pointer-target-kinds | — | — | orders.move-hero |
Targeted verbs
targeted-verbs
| Id | Verb | Order | Confirm style | Target gesture | Confirm gesture | Resolves on | After dispatch | Starts when declared in | Target gesture declared in | Confirm gesture declared in | Targets declared in | Area declared in | Command declared in |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
arc-stun-smart-cast | arc-stun | verb-first | at-entry-position | — | — | press | leave-targeting | abilities.choose-arc-stun | — | — | abilities.arc-stun-targets | — | abilities.arc-stun-command |
Queue modifiers
queue-modifiers
This adoption declares no queue modifiers.
Cancellations
cancellations
| Id | Action | Resolves on | Active state | Result | Action declared in | State declared in |
|---|---|---|---|---|---|---|
cancel-aim-mode | ability-key-again | press | targeting | ends-targeting | controls.ability-key-again | abilities.aim-mode-state |
clear-hero-selection | clear-selection-key | press | selection | empties-selection | controls.clear-selection-key | units.hero-selection-state |
Test inputsscope and seeds
Some tests need a scope or seeds from the adoption before they can run.
This adoption supplies no test inputs. Every test uses its default inputs.
Acceptance tests54 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.
pointer-command-vocabulary
pointer command uses actions, phases, snapshots, and states
Applies to moba-selection-and-smart-cast.
A game-facing pointer action arrives after physical input mapping. Its pointer phase is a press, release, completed drag, or canceled drag, and its pointer snapshot is the world point and classified object at that phase. A cited non-pointer action has one completion phase. A selection drag and a targeting state begin and end only as the contract states. This test checks nothing about device identity, several simultaneous pointers, or camera view or follow behavior.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption and its cited pointer, action, selection, and command rules- When
- the contract's state and records are identified before a pointer phase is resolved
- Then
- a game-facing pointer action is received after physical input mapping and a pointer phase is its press, release, completed drag, or canceled drag
- a pointer snapshot is the world point and classified object under the pointer at that phase
- a cited non-pointer action that supplies a verb, confirmation, or cancellation has one completion phase, recorded as press unless its cited rule names release
- a selection drag begins when its cited gesture rule crosses the drag threshold and ends when that action completes or cancels
- a targeting state holds one chosen verb or one target-first snapshot waiting for the verb
- device identity, several simultaneous pointers, and camera view or follow behavior are outside this contract, and this test checks nothing about them
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-targeting-state
selection-proposal-and-plan-vocabulary
selection, proposals, and waiting plans keep distinct meanings
Applies to moba-selection-and-smart-cast.
The current selection is one set and starts empty unless a cited load or scene-entry rule supplies it. It persists until a cited rule changes it. A command proposal contains one command, receiver shape, exact world target, and queue placement. A waiting plan contains pointer commands accepted for later execution for its cited plan owner.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption with distinguishable selection, proposal, and waiting-plan records- When
- a selection change and a pointer command are each followed through their declared route
- Then
- the current selection is one set of world objects and begins empty unless a cited load or scene-entry rule supplies it
- the selection persists until a cited pointer, control-group recall, death, roster, scene-entry, or load rule changes it
- one command proposal contains one command, its receiver shape, its exact world target, and its queue placement
- one waiting plan contains pointer commands accepted for later execution for the plan owner named by the cited command rule
- Diagnostics
moba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-plan-state
selection-gesture-resolves-at-declared-phase · add-ally-on-press
selection gesture add-ally-on-press resolves at its declared phase
Applies to the add-ally-on-press row.
Selection row add-ally-on-press matches action add-ally and resolves immediately from the press snapshot; a later drag or release is not inferred from that press under controls.add-ally. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
selection row
add-ally-on-pressand the gesture rule atcontrols.add-ally- When
- game-facing pointer action
add-allyis performed through its declared press, movement, and release
- game-facing pointer action
- Then
add-ally-on-pressresolves immediately from the press snapshot; a later drag or release is not inferred from that press- the row matches only its declared game-facing pointer action and resolving phase
- the test leaves recognition, thresholds, and geometry to
controls.add-allyand restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-log
selection-gesture-resolves-at-declared-phase · toggle-hero
selection gesture toggle-hero resolves at its declared phase
Applies to the toggle-hero row.
Selection row toggle-hero matches action toggle-hero and resolves from the final snapshot at release under controls.toggle-hero. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
selection row
toggle-heroand the gesture rule atcontrols.toggle-hero- When
- game-facing pointer action
toggle-herois performed through its declared press, movement, and release
- game-facing pointer action
- Then
toggle-heroresolves from the final snapshot at release- the row matches only its declared game-facing pointer action and resolving phase
- the test leaves recognition, thresholds, and geometry to
controls.toggle-heroand restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-log
selection-gesture-resolves-at-declared-phase · remove-defeated-hero
selection gesture remove-defeated-hero resolves at its declared phase
Applies to the remove-defeated-hero row.
Selection row remove-defeated-hero matches action remove-hero and resolves from the final snapshot at release under controls.remove-hero. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
selection row
remove-defeated-heroand the gesture rule atcontrols.remove-hero- When
- game-facing pointer action
remove-herois performed through its declared press, movement, and release
- game-facing pointer action
- Then
remove-defeated-heroresolves from the final snapshot at release- the row matches only its declared game-facing pointer action and resolving phase
- the test leaves recognition, thresholds, and geometry to
controls.remove-heroand restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-log
context-gesture-resolves-at-declared-phase · move-hero-on-ground
context command move-hero-on-ground resolves at its declared phase
Applies to the move-hero-on-ground row.
Context row move-hero-on-ground matches action hero-order and resolves from the final snapshot at release under controls.hero-order. Where that cited rule emits repeated completed phases while held, each emitted phase produces exactly one move-hero proposal; where it emits none, this test checks nothing about repeated phases. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
context row
move-hero-on-groundand the gesture rule atcontrols.hero-order- When
- game-facing pointer action
hero-orderis performed through its declared press, movement, and release
- game-facing pointer action
- Then
move-hero-on-groundresolves from the final snapshot at release- the row matches only its declared game-facing pointer action and resolving phase
- where
controls.hero-orderemits repeated completed phases while held, each emitted phase produces exactly onemove-heroproposal; where it emits none, this test checks nothing in this line - the test leaves recognition, thresholds, and geometry to
controls.hero-orderand restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-proposal-log
targeted-verb-resolves-at-declared-phase · arc-stun-smart-cast
targeted verb arc-stun-smart-cast resolves at its declared phase
Applies to the arc-stun-smart-cast row.
Targeted verb arc-stun-smart-cast uses the pointer snapshot at its declared press completion. One completed phase is recorded before validity is tested, and an incomplete phase creates no command proposal.
Test steps and diagnostics
- Given
targeted-verb row
arc-stun-smart-castin its declared targeting route- When
- its capture or confirmation reaches
press
- its capture or confirmation reaches
- Then
arc-stun-smart-castuses the pointer snapshot at its declared press completion- one completed phase is recorded before validity is tested
- an incomplete phase creates no command proposal
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-proposal-log
gesture-rule-alone-classifies-motion
the cited gesture rule alone classifies motion
Applies to moba-selection-and-smart-cast.
The cited gesture rule alone decides whether movement stays a point gesture, becomes a drag, or cancels. Its distance, duration, geometry, coordinate space, and boundary rule are read directly; this adoption contributes no number.
Test steps and diagnostics
- Given
each pointer action the
moba-selection-and-smart-castadoption can perform, including positions on either side of every cited gesture boundary- When
- the action moves and ends
- Then
- the cited gesture rule alone decides point, drag, or cancel
- the result follows the cited distance, duration, geometry, coordinate space, and boundary rule
- the adoption contributes no gesture quantity of its own
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-log
one-physical-sequence-one-result
one physical sequence produces one pointer result
Applies to moba-selection-and-smart-cast.
One physical sequence produces a point result or a drag result, never both. If the cited rule creates two distinct game-facing pointer actions, each has its own result; otherwise this test checks nothing about that exception.
Test steps and diagnostics
- Given
each physical pointer sequence the
moba-selection-and-smart-castadoption can recognize- When
- the sequence passes through press, movement, and release
- Then
- the sequence produces a point result or a drag result, never both
- where the cited gesture rule creates two distinct game-facing pointer actions, each action has its own result; otherwise this test checks nothing in this line
- Diagnostics
moba-selection-and-smart-cast-pointer-result
repeated-completed-phases-stay-distinct
each repeated completed command phase produces one proposal
Applies to moba-selection-and-smart-cast.
Where a cited gesture rule emits repeated completed command phases while held, each phase has its own result and produces exactly one proposal. A held interval with no repeated phase produces no extra proposal. Where no rule emits repeated phases, this test checks nothing.
Test steps and diagnostics
- Given
a held control whose cited gesture rule emits repeated completed command phases, where the adoption has one
- When
- the control remains held through two cited completed phases
- Then
- each emitted completed phase has its own pointer result
- each completed command phase produces exactly one command proposal
- a held interval that emits no repeated completed phase produces no extra proposal
- where no cited rule emits repeated completed phases, this test checks nothing
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-proposal-log
cancellation-applies-before-other-rows · cancel-aim-mode
cancellation cancel-aim-mode applies before any other row
Applies to the cancel-aim-mode row.
Cancellation cancel-aim-mode matches action ability-key-again, its press phase, and the holding state in abilities.aim-mode-state before any other row. It ends the targeting state, proposes no command, changes no selection beyond empties-selection, and ends the phase. Where more than one cancellation row could match, the contract checks the holding state in the order targeting, selection-drag, queued-commands, selection. A mismatch does not apply this row, and this test checks nothing about another cancellation row. This test checks nothing about an area cancellation.
Test steps and diagnostics
- Given
cancellation row
cancel-aim-mode, actionability-key-again, and the cited state atabilities.aim-mode-state- When
- a targeting state is active and
ability-key-againreaches press - the most similar case that does not match in action, phase, or holding state is also checked
- a targeting state is active and
- Then
- the complete match is checked before selection, context-command, or targeting rows and ends the targeting state
- the matched phase proposes no command, changes no selection beyond empties-selection, and ends immediately
- where more than one cancellation row could match, the holding state is checked in the order targeting, selection-drag, queued-commands, selection
- the mismatch does not apply
cancel-aim-mode, and this test checks nothing about another cancellation row that matches - this test checks nothing about an area cancellation, if the game has one, because this row has no dragged cancellation region
- Diagnostics
moba-selection-and-smart-cast-cancellation-logmoba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-plan-statemoba-selection-and-smart-cast-proposal-log
cancellation-applies-before-other-rows · clear-hero-selection
cancellation clear-hero-selection applies before any other row
Applies to the clear-hero-selection row.
Cancellation clear-hero-selection matches action clear-selection-key, its press phase, and the holding state in units.hero-selection-state before any other row. It empties the current selection, proposes no command, changes no selection beyond empties-selection, and ends the phase. Where more than one cancellation row could match, the contract checks the holding state in the order targeting, selection-drag, queued-commands, selection. A mismatch does not apply this row, and this test checks nothing about another cancellation row. This test checks nothing about an area cancellation.
Test steps and diagnostics
- Given
cancellation row
clear-hero-selection, actionclear-selection-key, and the cited state atunits.hero-selection-state- When
- the current selection is non-empty and
clear-selection-keyreaches press - the most similar case that does not match in action, phase, or holding state is also checked
- the current selection is non-empty and
- Then
- the complete match is checked before selection, context-command, or targeting rows and empties the current selection
- the matched phase proposes no command, changes no selection beyond empties-selection, and ends immediately
- where more than one cancellation row could match, the holding state is checked in the order targeting, selection-drag, queued-commands, selection
- the mismatch does not apply
clear-hero-selection, and this test checks nothing about another cancellation row that matches - this test checks nothing about an area cancellation, if the game has one, because this row has no dragged cancellation region
- Diagnostics
moba-selection-and-smart-cast-cancellation-logmoba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-plan-statemoba-selection-and-smart-cast-proposal-log
verb-first-begins-targeting · arc-stun-smart-cast
verb-first row arc-stun-smart-cast begins from its cited action
Applies to the arc-stun-smart-cast row.
For verb-first row arc-stun-smart-cast, the action at abilities.choose-arc-stun supplies arc-stun and begins targeting. A second entry does not replace an active state unless that cited rule explicitly does so. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
targeted-verb row
arc-stun-smart-castwith no active targeting state and the start rule atabilities.choose-arc-stun- When
- the cited game action supplies verb
arc-stun - the same entry is attempted while a targeting state is already active
- the cited game action supplies verb
- Then
- the first action begins a targeting entry holding
arc-stun - the second entry does not replace the active state unless
abilities.choose-arc-stunexplicitly replaces it - the test leaves the start action and any explicit replacement to
abilities.choose-arc-stunand restates nothing from it
- the first action begins a targeting entry holding
- Diagnostics
moba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-snapshot-log
target-first-captures-before-verb
target-first row Row.id captures its target before the verb
Does not apply to moba-selection-and-smart-cast: no row in targeted-verbs matches order target first.
separate-confirmation-reads-completion-snapshot
Row.id reads the target when confirmation completes
Does not apply to moba-selection-and-smart-cast: no row in targeted-verbs matches confirm-style separate gesture.
entry-position-confirmation-keeps-entry-snapshot · arc-stun-smart-cast
arc-stun-smart-cast confirms from its entry snapshot
Applies to the arc-stun-smart-cast row.
At-entry-position row arc-stun-smart-cast confirms from the pointer position captured when the verb-first entry begins. A later pointer position does not replace that snapshot.
Test steps and diagnostics
- Given
targeted-verb row
arc-stun-smart-castwith distinguishable entry and later pointer snapshots- When
- the row captures its declared entry-time snapshot and the pointer later occupies another position
- Then
- confirmation reads the pointer position captured when the verb-first entry begins
- the later pointer position does not replace that snapshot
- Diagnostics
moba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-targeting-state
targeted-drag-uses-cited-region
dragged verb Row.id uses its cited region
Does not apply to moba-selection-and-smart-cast: no row in targeted-verbs matches resolves-on drag complete.
targeted-verb-tests-candidate-and-validity · arc-stun-smart-cast
arc-stun-smart-cast resolves a candidate and tests validity
Applies to the arc-stun-smart-cast row.
Targeted verb arc-stun-smart-cast applies near-miss resolution and validity through abilities.arc-stun-targets. The result record distinguishes a valid target from an invalid one. The test names the address and restates nothing from it. This test checks nothing for a verb that needs several separately confirmed points.
Test steps and diagnostics
- Given
targeted-verb row
arc-stun-smart-castwith one cited valid target and one cited invalid target underabilities.arc-stun-targets- When
- each target reaches the row's confirmation route
- Then
- candidate lookup applies the adoption's near-miss-resolution answer through
abilities.arc-stun-targets - the cited validity test records valid for the valid target and invalid for the invalid target
- the test leaves target kinds, reach, tie-break, and validity content to
abilities.arc-stun-targetsand restates nothing from it - this test checks nothing for a verb that needs several separately confirmed points
- candidate lookup applies the adoption's near-miss-resolution answer through
- Diagnostics
moba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-targeting-state
invalid-target-keeps-targeting
an invalid target keeps targeting
Applies to moba-selection-and-smart-cast.
An invalid target creates no command proposal and keeps the same chosen verb active. The same phase is never matched against a context-command row. The result records invalid target rather than a refused proposal.
Test steps and diagnostics
- Given
each targeted verb in
moba-selection-and-smart-castwith an invalid target under its cited target rule- When
- the verb reaches confirmation and the target fails validity
- Then
- no command proposal is created
- the same chosen verb remains active for another target
- no context-command row runs from the same phase
- the pointer result records invalid target rather than a refused proposal
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-proposal-log
invalid-target-leaves-targeting
an invalid target leaves targeting
Does not apply to moba-selection-and-smart-cast: invalid target is keep targeting, not leave targeting.
valid-target-creates-one-proposal · arc-stun-smart-cast
a valid target creates one arc-stun-smart-cast proposal
Applies to the arc-stun-smart-cast row.
A valid target for arc-stun-smart-cast creates one proposal carrying the exact target, the command from abilities.arc-stun-command, and the receiver selected by the command-receiver answer. It ends targeting after the proposal is dispatched, placed, or refused. A refused command remains a dispatched proposal, and the refusal does not restore the earlier targeting instance. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
targeted-verb row
arc-stun-smart-castwith a valid resolved target underabilities.arc-stun-targets- When
- the row completes confirmation and its proposal reaches placement
- Then
- one command proposal is created with the command from
abilities.arc-stun-command, the receiver selected by the command-receiver answer, the validated exact target, and a placement outcome - the proposal preserves the row result that ends targeting after the proposal is dispatched, placed, or refused
- a refused command remains a dispatched proposal, and the refusal does not restore the earlier targeting instance
- the test leaves permission, cost, range, path, unreachable result, effect, and refusal to
abilities.arc-stun-commandand restates nothing from it
- one command proposal is created with the command from
- Diagnostics
moba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-plan-state
targeting-suppresses-selection-and-context · arc-stun-smart-cast
arc-stun-smart-cast targeting suppresses ordinary selection and context rows
Applies to the arc-stun-smart-cast row.
While the targeting state for arc-stun-smart-cast is active, an ordinary selection or context gesture has no meaning. If the same action and phase matches a cancellation row in the holding state, only the cancellation applies. Where the adoption cannot construct one of the two cases, this test checks nothing for that case.
Test steps and diagnostics
- Given
targeted-verb row
arc-stun-smart-cast's active targeting state and a game-facing pointer action that would match a selection or context row with no targeting state- When
- the action completes while targeting is active, first without and then with a matching cancellation row where one exists
- Then
- without a matching cancellation row, the action changes no selection and creates no context-command proposal
- with a matching cancellation row, only that cancellation result applies and the phase ends
- where one of the two cases cannot be constructed, this test checks nothing for that case
- Diagnostics
moba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-cancellation-log
selection-or-context-row-match
one selection or context row matches without targeting
Applies to moba-selection-and-smart-cast.
With no active targeting state, if a selection or context row matches action, phase, and classification, exactly one proceeds. A target-first capture gesture is resolved at targeting entry and is neither a selection or context row match nor an unmatched classification. If no row matches, no world-command state changes and the unmatched classification is recorded. Where no unmatched classification can be constructed, this test checks nothing for that case.
Test steps and diagnostics
- Given
no active targeting state and each classified pointer snapshot the
moba-selection-and-smart-castadoption can produce, including an unmatched classification where one can be constructed- When
- the game-facing pointer action reaches a completed phase
- Then
- where a row matches, exactly one selection or context row proceeds from its action, phase, and classification
- a target-first capture gesture is resolved at targeting entry and is neither a selection or context row match nor an unmatched classification
- where no row matches, no world-command state changes and the result records the unmatched classification
- where every classification that can be constructed matches a row, this test checks nothing for the unmatched case
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-proposal-log
receiver-conditioned-context-match
Row.id also matches its cited receiver class
Does not apply to moba-selection-and-smart-cast: no matching row in context-commands has every field this test uses (receiver-condition).
selection-row-uses-complete-candidate-set · add-ally-on-press
selection row add-ally-on-press commits its complete candidate set once
Applies to the add-ally-on-press row.
Selection row add-ally-on-press reads the complete candidate set at the pointer point from units.ally-selection and adds the complete non-empty set; an empty set keeps the current selection; a non-empty result is committed once and an unchanged empty result records no selection change. The phase ends without a proposal. This test checks nothing about selection layers. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
selection row
add-ally-on-presswith a non-empty and an empty result fromunits.ally-selection- When
add-allycompletes atpressfor each result
- Then
- candidate lookup returns the complete candidate set at the pointer point through
units.ally-selection - the row adds the complete non-empty set; an empty set keeps the current selection; a non-empty result is committed once and an unchanged empty result records no selection change
- the pointer phase ends without a command proposal
- the test leaves candidate kinds, inclusion, reach, and tie-break to
units.ally-selectionand restates nothing from it - this test checks nothing about selection layers, because the result is one set
- candidate lookup returns the complete candidate set at the pointer point through
- Diagnostics
moba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-proposal-log
selection-row-uses-complete-candidate-set · toggle-hero
selection row toggle-hero commits its complete candidate set once
Applies to the toggle-hero row.
Selection row toggle-hero reads the complete candidate set at the pointer point from units.hero-selection and toggles every member of the complete non-empty set; an empty set keeps the current selection; a non-empty result is committed once and an unchanged empty result records no selection change. The phase ends without a proposal. This test checks nothing about selection layers. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
selection row
toggle-herowith a non-empty and an empty result fromunits.hero-selection- When
toggle-herocompletes atreleasefor each result
- Then
- candidate lookup returns the complete candidate set at the pointer point through
units.hero-selection - the row toggles every member of the complete non-empty set; an empty set keeps the current selection; a non-empty result is committed once and an unchanged empty result records no selection change
- the pointer phase ends without a command proposal
- the test leaves candidate kinds, inclusion, reach, and tie-break to
units.hero-selectionand restates nothing from it - this test checks nothing about selection layers, because the result is one set
- candidate lookup returns the complete candidate set at the pointer point through
- Diagnostics
moba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-proposal-log
selection-row-uses-complete-candidate-set · remove-defeated-hero
selection row remove-defeated-hero commits its complete candidate set once
Applies to the remove-defeated-hero row.
Selection row remove-defeated-hero reads the complete candidate set at the pointer point from units.defeated-hero-selection and removes the complete non-empty set; an empty set keeps the current selection; a non-empty result is committed once and an unchanged empty result records no selection change. The phase ends without a proposal. This test checks nothing about selection layers. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
selection row
remove-defeated-herowith a non-empty and an empty result fromunits.defeated-hero-selection- When
remove-herocompletes atreleasefor each result
- Then
- candidate lookup returns the complete candidate set at the pointer point through
units.defeated-hero-selection - the row removes the complete non-empty set; an empty set keeps the current selection; a non-empty result is committed once and an unchanged empty result records no selection change
- the pointer phase ends without a command proposal
- the test leaves candidate kinds, inclusion, reach, and tie-break to
units.defeated-hero-selectionand restates nothing from it - this test checks nothing about selection layers, because the result is one set
- candidate lookup returns the complete candidate set at the pointer point through
- Diagnostics
moba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-proposal-log
empty-replace-clears-selection
an empty replacement clears the selection
Does not apply to moba-selection-and-smart-cast: empty selection is keep selection, not clear selection.
empty-replace-keeps-selection
an empty replacement keeps the selection
Applies to moba-selection-and-smart-cast.
When a replace selection row returns an empty complete candidate set, the earlier current selection remains unchanged. The result distinguishes the empty candidate set from a non-empty set with the same final members. The contract says the answer applies only to selection rows whose change is replace; where the adoption declares none, this answer has no effect, and this test checks nothing.
Test steps and diagnostics
- Given
each replace selection row in
moba-selection-and-smart-cast, a distinguishable current selection, and an empty complete candidate set- When
- the selection gesture completes
- Then
- the earlier current selection remains unchanged
- the result record distinguishes the empty candidate set from a non-empty set that gives the same selection
- where the adoption declares no replace selection row, this answer has no effect, and this test checks nothing
- Diagnostics
moba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-pointer-result
context-row-copies-target-and-creates-proposal · move-hero-on-ground
context row move-hero-on-ground copies its target into one proposal
Applies to the move-hero-on-ground row.
Context row move-hero-on-ground copies the classified ground point or object from arena.pointer-target-kinds as its exact target. One proposal is created with command move-hero and the receiver shape selected by the command-receiver answer; its Fixed command rule is at orders.move-hero. The copied target and receiver do not change before placement. The test names both addresses and restates nothing from them.
Test steps and diagnostics
- Given
context row
move-hero-on-groundand a classifiedgroundsnapshot underarena.pointer-target-kinds- When
hero-ordercompletes atreleasewith no active targeting state
- Then
- the row copies the classified point or object as the exact target
- one proposal is created with command
move-heroand the receiver shape selected by the command-receiver answer - the proposal proceeds to queue placement without changing the copied target or receiver
- the test leaves classification, reach, and tie-break to
arena.pointer-target-kindsand command content toorders.move-heroand restates nothing from them
- Diagnostics
moba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-pointer-result
context-drag-uses-cited-region
dragged context row Row.id uses its cited region
Does not apply to moba-selection-and-smart-cast: no row in context-commands matches resolves-on drag complete.
fixed-actor-receives-command
the cited fixed actor receives each command
Does not apply to moba-selection-and-smart-cast: command receiver is current selection, not fixed actor.
current-selection-receives-command
the complete current selection receives each command
Applies to moba-selection-and-smart-cast.
A non-empty complete current selection is copied as the receiver and its proposal proceeds to placement. An empty copy creates one refused proposal with no world effect and ends before placement or dispatch. For a valid targeted verb, the contract says an empty current selection makes one refused proposal in the same way. The result distinguishes that from no proposal. Later selection changes do not alter the copy.
Test steps and diagnostics
- Given
each matching context command and valid targeted verb in
moba-selection-and-smart-cast, first with a non-empty current selection and then with an empty one- When
- the command proposal reaches receiver resolution
- Then
- the non-empty case copies the complete current selection and creates one proposal that proceeds to placement
- the empty case creates one refused proposal with no world effect and ends before queue placement or command dispatch
- for a valid targeted verb, the contract says an empty current selection makes one refused proposal in the same way
- the result record distinguishes the refused proposal from no proposal
- later selection changes do not change the copied receiver
- Diagnostics
moba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-plan-state
world-target-owns-command
the exact world target owns each command
Does not apply to moba-selection-and-smart-cast: command receiver is current selection, not world target.
exact-point-only-resolves-candidates
candidate lookup uses the exact pointer point
Applies to moba-selection-and-smart-cast.
Every candidate lookup uses only the exact pointer point. No near-miss reach adds a candidate; the cited row rule still owns target kinds, point inclusion, and validity.
Test steps and diagnostics
- Given
each candidate lookup in
moba-selection-and-smart-cast, with one point on a cited target and one point just outside it- When
- the pointer snapshot is classified through the row's candidate or target rule
- Then
- only the exact pointer point is used
- no near-miss reach adds a candidate
- the cited rule still owns target kinds, point inclusion, and validity
- Diagnostics
moba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-pointer-result
nearest-within-reach-resolves-candidates
candidate lookup chooses the cited nearest candidate
Does not apply to moba-selection-and-smart-cast: near miss resolution is exact point only, not nearest within reach.
queue-modifier-appends-at-end
queue modifier Row.id appends a matching proposal
Does not apply to moba-selection-and-smart-cast: queued command placement is not asked for moba-selection-and-smart-cast.
queue-modifier-inserts-next
queue modifier Row.id inserts a matching proposal next
Does not apply to moba-selection-and-smart-cast: queued command placement is not asked for moba-selection-and-smart-cast.
unmodified-command-replaces-waiting
an unmodified command replaces waiting pointer commands
Applies to moba-selection-and-smart-cast.
With no matching queue modifier, the proposal clears every waiting pointer command for the same owner and is placed once. Whether a command already being carried out stops belongs to the cited command rule. The plan record distinguishes replacement from an append with the same visible count. This test checks nothing about placement differences between rows, because the answer applies to the whole adoption.
Test steps and diagnostics
- Given
an unmodified proposal in
moba-selection-and-smart-castfor a plan owner with distinguishable waiting pointer commands- When
- the proposal reaches placement with no matching queue modifier
- Then
- every waiting pointer command for the same owner is cleared
- the new proposal is placed once and proceeds to its cited command rule
- the command already being carried out stops only if the cited command rule says so
- the plan record distinguishes replacement from an append that leaves one visible entry
- this test checks nothing about placement differences between rows, because the answer applies to the whole adoption
- Diagnostics
moba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-plan-statemoba-selection-and-smart-cast-pointer-result
unmodified-command-always-appends
an unmodified command appends after waiting commands
Does not apply to moba-selection-and-smart-cast: unmodified command is replaces waiting, not always appends.
unmodified-command-rejects-while-busy
an unmodified command is accepted only when its plan is not busy
Does not apply to moba-selection-and-smart-cast: unmodified command is replaces waiting, not rejected while busy.
proposal-count-and-targeting-result
one completed phase creates no duplicate proposal
Applies to moba-selection-and-smart-cast.
Each completed phase that creates a proposal creates exactly one. A held modifier or update adds no copy. For a targeted verb, the row's after-dispatch result applies after placement or refusal; for a context command, this test checks nothing about that result.
Test steps and diagnostics
- Given
each completed pointer phase in
moba-selection-and-smart-castthat creates a proposal, including one with a held queue modifier where available- When
- the proposal is created, placed or refused, and any targeted-verb result is applied
- Then
- the completed phase creates exactly one proposal
- a held modifier or update creates no second copy within that phase
- for a targeted verb, its after-dispatch result applies after placement or refusal; for a context command, this test checks nothing in this line
- Diagnostics
moba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-plan-state
proposal-submission-stops-at-command-rule
dispatch stops at the cited command rule
Applies to moba-selection-and-smart-cast.
Each placed proposal is submitted once to its cited Fixed command rule at its declared place. Permission, cost, range, path, the unreachable case, effect, refusal, and whether a current command stops belong to that rule. Event resolution owns same-instant order. This test checks nothing about a paired Action legibility adoption.
Test steps and diagnostics
- Given
each placed proposal in
moba-selection-and-smart-cast, including one queued proposal when the adoption can create one- When
- the proposal reaches its declared place and is submitted
- Then
- the proposal is submitted once to its cited Fixed command rule at its declared place
- the pointer contract makes no claim about permission, cost, range, path, the unreachable case, effect, refusal, or whether a current command stops after submission
- when several proposals share one instant, their order is left to Event resolution
- this test checks nothing about a paired Action legibility adoption
- Diagnostics
moba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-plan-statemoba-selection-and-smart-cast-pointer-result
pointer-result-record-is-complete
the pointer result records the completed phase
Applies to moba-selection-and-smart-cast.
Every pointer result records its gesture, phase, snapshot, targeting states, changed selection, proposed command and receiver, target, placement outcome, cancellation, tested target validity, unmatched classification, and available cited game-rule result. Where the adoption cannot construct an optional circumstance, this test checks nothing for that circumstance.
Test steps and diagnostics
- Given
each completed pointer phase in
moba-selection-and-smart-cast, including every optional circumstance the adoption can construct- When
- the pointer result is read after resolution
- Then
- the result records gesture id, resolving phase, pointer snapshot, prior and final targeting state, and prior and final selection when changed
- it records command and receiver when proposed, target, queue modifier or unmodified placement outcome, cancellation when used, and target validity for every targeted verb that reached validity
- it records no-matching-row when applicable and the cited game-rule result when available
- where the adoption cannot construct an optional circumstance, this test checks nothing for that circumstance
- Diagnostics
moba-selection-and-smart-cast-pointer-result
authority-order-preserves-copies
later steps preserve the earlier snapshot and receiver
Applies to moba-selection-and-smart-cast.
The contract's order of the steps is physical mapping, gesture recognition, cancellation, targeting entry, confirmation, selection or context classification, receiver snapshot, placement, dispatch, game rule, and same-instant event order. Later steps never change an earlier snapshot or receiver; classification can read receiver class without copying the set. The questions and rows supply choices and cited game rules. They do not change the order.
Test steps and diagnostics
- Given
each completed pointer phase in
moba-selection-and-smart-castwith distinguishable snapshot, receiver, placement, and game-rule data- When
- the phase proceeds through every step it reaches
- Then
- physical mapping precedes gesture recognition, cancellation, targeting entry, target confirmation, selection or context classification, receiver snapshot, queue placement, command dispatch, game rule, and same-instant event order
- a later step never changes the pointer snapshot or receiver copied earlier
- classification can read receiver class without copying the receiver set
- the questions and rows supply choices and cited game rules, and they do not change the order
- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-plan-state
empty-collections-and-unasked-questions
absent rows and unasked questions keep their declared meaning
Applies to moba-selection-and-smart-cast.
This check reads the adoption shape. Each empty row set has exactly its when-empty meaning. Each gated question the adoption does not answer has exactly its otherwise meaning: without empty-selection, no pointer gesture changes the current world selection; without invalid-target, no chosen ability or verb waits for a world target from the pointer; without queued-command-placement, no pointer modifier adds a command to a queue; without unmodified-command, no pointer command can enter a queue. When the adoption answers a question or fills a row set, this test checks nothing for that question or row set.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption document, including each empty and non-empty row set and each gated question it does or does not answer- When
- a reviewer compares the adoption shape with every row-set when-empty sentence and every gated-question otherwise sentence
- Then
- an empty selection-gestures set means no pointer gesture changes the current selection; when non-empty, this test checks nothing in this line
- an empty context-commands set means no pointer gesture chooses a command directly from its world target; when non-empty, this test checks nothing in this line
- an empty targeted-verbs set means no chosen verb waits for a pointer target; when non-empty, this test checks nothing in this line
- an empty queue-modifiers set means no pointer modifier adds a command to a queue; when non-empty, this test checks nothing in this line
- an empty cancellations set means no action has a separate cancellation meaning in this adoption; when non-empty, this test checks nothing in this line
- when the adoption does not answer empty-selection, no pointer gesture changes the current world selection; when it answers, this test checks nothing in this line
- when the adoption does not answer invalid-target, no chosen ability or verb waits for a world target from the pointer; when it answers, this test checks nothing in this line
- when the adoption does not answer queued-command-placement, no pointer modifier adds a command to a queue; when it answers, this test checks nothing in this line
- when the adoption does not answer unmodified-command, no pointer command can enter a queue; when it answers, this test checks nothing in this line
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-and-context-rows-are-disjoint
declaration check: selection and context rows are disjoint
Applies to moba-selection-and-smart-cast.
This declaration check reads the adoption, not the running game. Under the contract's mutually exclusive classifications, no selection and context row, two selection rows, or target-first capture and selection or context row can match the same game-facing action, phase, and classification. No two cancellation rows match the same game-facing action and phase in one holding state under the contract's targeting, selection-drag, queued-commands, selection order. Context target kinds for one action and phase, together with any cited receiver class, must be mutually exclusive. One completed phase selects or commands, never both. Any other shape makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption, not the running game- When
- a reviewer compares every selection row, context row, target-first capture gesture, and cancellation row by its contract matching terms
- Then
- no selection row and context row match the same game-facing action, phase, and classification
- no two selection rows match the same game-facing action, phase, and classification
- no target-first capture gesture matches the same game-facing action, phase, and classification as a selection or context row
- no two cancellation rows match the same game-facing action and phase in one holding state
- for one context action and phase, target-kind values together with any cited receiver class are mutually exclusive
- one completed phase therefore selects or commands, never both
- any other shape makes the adoption invalid, and this test fails
- Diagnostics
moba-selection-and-smart-cast-declaration-record
queue-modifier-targets-declared-rows
declaration check: modifier Row.id names only declared commands, and at least one
Does not apply to moba-selection-and-smart-cast: queue-modifiers has no rows.
cancellation-state-can-exist · cancel-aim-mode
declaration check: cancellation cancel-aim-mode names a state this adoption can hold
Applies to the cancel-aim-mode row.
This declaration check reads the adoption, not the running game. For cancellation cancel-aim-mode in targeting, the adoption has a targeted-verb row, and its result must match that state. Any other shape makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption and cancellation rowcancel-aim-mode, not the running game- When
- a reviewer compares its active state with the adoption's rows and answers
- Then
- for active state
targeting, the adoption has a targeted-verb row - the result matches that state: targeting with ends-targeting, selection-drag with ends-drag, queued-commands with empties-queue, or selection with empties-selection
- any other shape makes the adoption invalid, and this test fails
- for active state
- Diagnostics
moba-selection-and-smart-cast-declaration-record
cancellation-state-can-exist · clear-hero-selection
declaration check: cancellation clear-hero-selection names a state this adoption can hold
Applies to the clear-hero-selection row.
This declaration check reads the adoption, not the running game. For cancellation clear-hero-selection in selection, the adoption has a selection gesture, and its result must match that state. Any other shape makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption and cancellation rowclear-hero-selection, not the running game- When
- a reviewer compares its active state with the adoption's rows and answers
- Then
- for active state
selection, the adoption has a selection gesture - the result matches that state: targeting with ends-targeting, selection-drag with ends-drag, queued-commands with empties-queue, or selection with empties-selection
- any other shape makes the adoption invalid, and this test fails
- for active state
- Diagnostics
moba-selection-and-smart-cast-declaration-record
current-selection-has-a-source
declaration check: current selection has a declared source
Applies to moba-selection-and-smart-cast.
This declaration check reads the adoption, not the running game. Under current-selection, at least one selection gesture or a cited load or scene-entry rule must supply the selection. Any other shape makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption and its selection, load, and scene-entry declarations, not the running game- When
- a reviewer checks how a non-empty current selection can first exist
- Then
- at least one selection gesture or a cited load or scene-entry rule supplies the selection
- any other shape makes the adoption invalid, and this test fails
- Diagnostics
moba-selection-and-smart-cast-declaration-record
targeted-verb-has-exit · arc-stun-smart-cast
declaration check: targeted verb arc-stun-smart-cast has a way to leave targeting
Applies to the arc-stun-smart-cast row.
This declaration check reads the adoption, the contract's targeted-verbs description, and abilities.choose-arc-stun, not the running game. The description requires every targeting state to be left through leave-targeting, a targeting cancellation row, or the cited start rule. Targeted verb arc-stun-smart-cast must therefore have leave-targeting as its applicable invalid-target answer or after-dispatch value, a targeting cancellation row, or an exit in that cited start rule. Any other shape makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption, the contract's targeted-verbs description, targeted-verb rowarc-stun-smart-cast, its start rule, and its cancellation rows, not the running game- When
- a reviewer checks every route by which this targeting state can end
- Then
- the targeted-verbs description requires every targeting state to be left through leave-targeting, a targeting cancellation row, or the cited start rule
- for
arc-stun-smart-cast, the applicable invalid-target answer or after-dispatch value is leave-targeting, or the adoption has a targeting cancellation row, orabilities.choose-arc-stunstates an exit - any other shape makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-gesture-citation-duty · add-ally-on-press
declaration check: add-ally-on-press gesture citation states its duty
Applies to the add-ally-on-press row.
This declaration check reads the adoption and controls.add-ally, not the running game. The citation must satisfy this duty: it recognizes the game-facing pointer action and its completion phase, including drag threshold and area geometry where used. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andcontrols.add-ally, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.add-allyrecognizes the game-facing pointer action and its completion phase, including drag threshold and area geometry where used- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-gesture-citation-duty · toggle-hero
declaration check: toggle-hero gesture citation states its duty
Applies to the toggle-hero row.
This declaration check reads the adoption and controls.toggle-hero, not the running game. The citation must satisfy this duty: it recognizes the game-facing pointer action and its completion phase, including drag threshold and area geometry where used. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andcontrols.toggle-hero, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.toggle-herorecognizes the game-facing pointer action and its completion phase, including drag threshold and area geometry where used- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-gesture-citation-duty · remove-defeated-hero
declaration check: remove-defeated-hero gesture citation states its duty
Applies to the remove-defeated-hero row.
This declaration check reads the adoption and controls.remove-hero, not the running game. The citation must satisfy this duty: it recognizes the game-facing pointer action and its completion phase, including drag threshold and area geometry where used. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andcontrols.remove-hero, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.remove-herorecognizes the game-facing pointer action and its completion phase, including drag threshold and area geometry where used- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-candidates-citation-duty · add-ally-on-press
declaration check: add-ally-on-press candidate citation states its duty
Applies to the add-ally-on-press row.
This declaration check reads the adoption and units.ally-selection, not the running game. The citation must satisfy this duty: it names selectable target kinds, point or area inclusion, near-miss reach when used, and a complete tie-break. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andunits.ally-selection, not the running game- When
- a reviewer checks the citation's meaning
- Then
units.ally-selectionnames selectable target kinds, point or area inclusion, near-miss reach when used, and a complete tie-break- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-candidates-citation-duty · toggle-hero
declaration check: toggle-hero candidate citation states its duty
Applies to the toggle-hero row.
This declaration check reads the adoption and units.hero-selection, not the running game. The citation must satisfy this duty: it names selectable target kinds, point or area inclusion, near-miss reach when used, and a complete tie-break. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andunits.hero-selection, not the running game- When
- a reviewer checks the citation's meaning
- Then
units.hero-selectionnames selectable target kinds, point or area inclusion, near-miss reach when used, and a complete tie-break- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
selection-candidates-citation-duty · remove-defeated-hero
declaration check: remove-defeated-hero candidate citation states its duty
Applies to the remove-defeated-hero row.
This declaration check reads the adoption and units.defeated-hero-selection, not the running game. The citation must satisfy this duty: it names selectable target kinds, point or area inclusion, near-miss reach when used, and a complete tie-break. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andunits.defeated-hero-selection, not the running game- When
- a reviewer checks the citation's meaning
- Then
units.defeated-hero-selectionnames selectable target kinds, point or area inclusion, near-miss reach when used, and a complete tie-break- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
context-gesture-citation-duty · move-hero-on-ground
declaration check: move-hero-on-ground gesture citation states its duty
Applies to the move-hero-on-ground row.
This declaration check reads the adoption and controls.hero-order, not the running game. The citation must satisfy this duty: it recognizes the game-facing pointer action and its completion phase. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andcontrols.hero-order, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.hero-orderrecognizes the game-facing pointer action and its completion phase- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
context-target-citation-duty · move-hero-on-ground
declaration check: move-hero-on-ground target citation states its duty
Applies to the move-hero-on-ground row.
This declaration check reads the adoption and arena.pointer-target-kinds, not the running game. The citation must satisfy this duty: it classifies the pointer snapshot, names the exact target, and states reach and a complete tie-break for nearest-within-reach. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andarena.pointer-target-kinds, not the running game- When
- a reviewer checks the citation's meaning
- Then
arena.pointer-target-kindsclassifies the pointer snapshot, names the exact target, and states reach and a complete tie-break for nearest-within-reach- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
context-area-citation-duty
declaration check: Row.id area citation states its duty
Does not apply to moba-selection-and-smart-cast: no row in context-commands matches resolves-on drag complete.
context-receiver-condition-citation-duty
declaration check: Row.id receiver-condition citation states its duty
Does not apply to moba-selection-and-smart-cast: no matching row in context-commands has every field this test uses (receiver-condition).
context-command-citation-duty · move-hero-on-ground
declaration check: move-hero-on-ground command citation states its duty
Applies to the move-hero-on-ground row.
This declaration check reads the adoption and orders.move-hero, not the running game. The citation must satisfy this duty: it names the command, receiver, target, per-target plan owner, permission, unreachable-target result, and complete accepted or refused effect. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andorders.move-hero, not the running game- When
- a reviewer checks the citation's meaning
- Then
orders.move-heronames the command, receiver, target, per-target plan owner, permission, unreachable-target result, and complete accepted or refused effect- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
targeted-start-citation-duty · arc-stun-smart-cast
declaration check: arc-stun-smart-cast start citation states its duty
Applies to the arc-stun-smart-cast row.
This declaration check reads the adoption and abilities.choose-arc-stun, not the running game. The citation must satisfy this duty: it names the game action that supplies the verb and any targeting-state replacement or exit it owns. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andabilities.choose-arc-stun, not the running game- When
- a reviewer checks the citation's meaning
- Then
abilities.choose-arc-stunnames the game action that supplies the verb and any targeting-state replacement or exit it owns- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
targeted-target-gesture-citation-duty
declaration check: Row.id target-gesture citation states its duty
Does not apply to moba-selection-and-smart-cast: no row in targeted-verbs matches order target first.
targeted-confirm-gesture-citation-duty
declaration check: Row.id confirmation citation states its duty
Does not apply to moba-selection-and-smart-cast: no row in targeted-verbs matches confirm-style separate gesture.
targeted-targets-citation-duty · arc-stun-smart-cast
declaration check: arc-stun-smart-cast targets citation states its duty
Applies to the arc-stun-smart-cast row.
This declaration check reads the adoption and abilities.arc-stun-targets, not the running game. The citation must satisfy this duty: it names target capture, every valid target, near-miss reach and tie-break when used, and the complete invalid-target test. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andabilities.arc-stun-targets, not the running game- When
- a reviewer checks the citation's meaning
- Then
abilities.arc-stun-targetsnames target capture, every valid target, near-miss reach and tie-break when used, and the complete invalid-target test- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
targeted-area-citation-duty
declaration check: Row.id area citation states its duty
Does not apply to moba-selection-and-smart-cast: no row in targeted-verbs matches resolves-on drag complete.
targeted-command-citation-duty · arc-stun-smart-cast
declaration check: arc-stun-smart-cast command citation states its duty
Applies to the arc-stun-smart-cast row.
This declaration check reads the adoption and abilities.arc-stun-command, not the running game. The citation must satisfy this duty: it names the command, receiver, per-target plan owner, permission, cost, unreachable-target result, and complete effect or refusal. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andabilities.arc-stun-command, not the running game- When
- a reviewer checks the citation's meaning
- Then
abilities.arc-stun-commandnames the command, receiver, per-target plan owner, permission, cost, unreachable-target result, and complete effect or refusal- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
queue-modifier-citation-duty
declaration check: Row.id modifier citation states its duty
Does not apply to moba-selection-and-smart-cast: queue-modifiers has no rows.
queue-applicability-citation-duty
declaration check: Row.id applicability citation states its duty
Does not apply to moba-selection-and-smart-cast: queue-modifiers has no rows.
cancellation-action-citation-duty · cancel-aim-mode
declaration check: cancel-aim-mode action citation states its duty
Applies to the cancel-aim-mode row.
This declaration check reads the adoption and controls.ability-key-again, not the running game. The citation must satisfy this duty: it recognizes the cancellation action and its completion phase. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andcontrols.ability-key-again, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.ability-key-againrecognizes the cancellation action and its completion phase- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
cancellation-action-citation-duty · clear-hero-selection
declaration check: clear-hero-selection action citation states its duty
Applies to the clear-hero-selection row.
This declaration check reads the adoption and controls.clear-selection-key, not the running game. The citation must satisfy this duty: it recognizes the cancellation action and its completion phase. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andcontrols.clear-selection-key, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.clear-selection-keyrecognizes the cancellation action and its completion phase- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
cancellation-state-citation-duty · cancel-aim-mode
declaration check: cancel-aim-mode state citation states its duty
Applies to the cancel-aim-mode row.
This declaration check reads the adoption and abilities.aim-mode-state, not the running game. The citation must satisfy this duty: it names when the affected targeting, selection-drag, waiting-plan, or selection state exists. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andabilities.aim-mode-state, not the running game- When
- a reviewer checks the citation's meaning
- Then
abilities.aim-mode-statenames when the affected targeting, selection-drag, waiting-plan, or selection state exists- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
cancellation-state-citation-duty · clear-hero-selection
declaration check: clear-hero-selection state citation states its duty
Applies to the clear-hero-selection row.
This declaration check reads the adoption and units.hero-selection-state, not the running game. The citation must satisfy this duty: it names when the affected targeting, selection-drag, waiting-plan, or selection state exists. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
moba-selection-and-smart-castadoption andunits.hero-selection-state, not the running game- When
- a reviewer checks the citation's meaning
- Then
units.hero-selection-statenames when the affected targeting, selection-drag, waiting-plan, or selection state exists- a missing duty makes the adoption invalid, and this test fails
- the test names the address and restates nothing from it
- Diagnostics
moba-selection-and-smart-cast-declaration-record
pointer-command-holds
pointer command holds for the whole run
Applies to moba-selection-and-smart-cast.
Across every completed pointer phase of the audited run in every state the adoption can be in, every completed phase matches at most one row in the contract's precedence; every selection change commits once from the complete candidate set; every proposal keeps its copied snapshot and receiver to its declared place; every cancellation clears only its declared state; every targeting state ends only as declared; and no phase produces two proposals.
Test steps and diagnostics
- Holds
every completed pointer phase matched at most one row in the precedence the contract fixes; every selection change committed once from the complete candidate set; every command proposal carried its copied snapshot and receiver unchanged to its declared place; every cancellation cleared only its declared state; every targeting state ended only as declared; no phase produced two proposals
- Seeds
["audit-a","audit-b"]- Scope
every completed pointer phase of the audited run in every state the adoption can be in- Diagnostics
moba-selection-and-smart-cast-pointer-resultmoba-selection-and-smart-cast-snapshot-logmoba-selection-and-smart-cast-selection-statemoba-selection-and-smart-cast-targeting-statemoba-selection-and-smart-cast-proposal-logmoba-selection-and-smart-cast-plan-statemoba-selection-and-smart-cast-cancellation-log
JSONthe adoption as one file
Answers you try on this page do not change this file. To change an adoption, open it in the authoring tool.
{
"contract": "pointer-command",
"version": 2,
"summary": "This contract covers pointer gestures that select things in the world and issue commands to or at the world. It records direct world orders, chosen abilities and verbs, orders added to a queue, and cancellation. This contract does not cover physical bindings, the camera view, displayed information, pathfinding, unit AI, or formations. The Control options contract covers physical bindings, the Camera framing contract covers the camera view, and the Fact list contract covers displayed information.",
"questions": {
"command-receiver": {
"asks": "Who receives a command made by pointing at the world?",
"rationale": "A pointer command may control one fixed actor, the current selection, or the place the pointer is on.",
"options": {
"fixed-actor": {
"meaning": "One fixed actor or party receives every world command. An ARPG hero moves wherever the ground is clicked.",
"semantics": "Every proposed command names the actor or party fixed by its cited command rule. No world selection is required to supply a receiver."
},
"current-selection": {
"meaning": "The current world selection receives every command. An RTS order moves the selected squad.",
"semantics": "The receiver set is the complete current selection. An empty set is refused as a receiver."
},
"world-target": {
"meaning": "The command belongs to the place or object under the pointer, without a selected actor. A colony work order marks one ore tile for any worker.",
"semantics": "A proposed command names its world target and no selected receiver. The cited game rule owns any later choice of actor, worker, structure, or world system that carries it out."
}
}
},
"near-miss-resolution": {
"asks": "When the pointer just misses a target, what can it choose?",
"rationale": "The game can require the exact point or choose the nearest candidate inside a declared reach.",
"options": {
"exact-point-only": {
"meaning": "Only the exact place or object under the pointer counts. A click beside a chest does not choose it.",
"semantics": "Candidate lookup uses the exact pointer point and applies no near-miss reach."
},
"nearest-within-reach": {
"meaning": "The nearest candidate inside the game's declared reach counts. A click beside a small lever can choose it.",
"semantics": "Candidate lookup chooses the nearest selectable candidate inside the cited reach and uses the cited complete tie-break."
}
}
},
"empty-selection": {
"asks": "The player clicks or drags to select units, and nothing is there. What happens to the current selection?",
"rationale": "An empty click or box can clear the selection or leave the current selection in place. The answer applies only to selection gestures whose change is replace. When no such row exists, the answer has no effect.",
"when": {
"row-count": {
"selection-gestures": "non-empty"
}
},
"otherwise": "No pointer gesture changes the current world selection.",
"options": {
"clear-selection": {
"meaning": "The current selection is cleared. A tactics click on open ground leaves no unit selected.",
"semantics": "An empty result empties the current selection."
},
"keep-selection": {
"meaning": "The current selection stays. A colony drag across bare ground leaves the chosen workers selected.",
"semantics": "An empty result keeps the current selection."
}
}
},
"invalid-target": {
"asks": "The player points at an invalid target for the chosen ability or verb. Does the game keep waiting for another target?",
"rationale": "The game can wait for the player to point again, or it can return to ordinary pointing.",
"when": {
"row-count": {
"targeted-verbs": "non-empty"
}
},
"otherwise": "No chosen ability or verb waits for a world target from the pointer.",
"options": {
"keep-targeting": {
"meaning": "The game keeps waiting for another point. An ARPG fire spell still waits after the player points outside its range.",
"semantics": "After an invalid target, the same chosen verb stays active."
},
"leave-targeting": {
"meaning": "The game stops waiting after the invalid point. A tower placement returns to ordinary pointing after a blocked tile.",
"semantics": "After an invalid target, the chosen verb is cleared."
}
}
},
"queued-command-placement": {
"asks": "The player holds the key that adds an order to the queue. Where does the new order go?",
"rationale": "The new order may wait at the end of the queue, or become the next order after the current one.",
"when": {
"row-count": {
"queue-modifiers": "non-empty"
}
},
"otherwise": "No pointer modifier adds a command to a queue.",
"options": {
"append-at-end": {
"meaning": "The new order goes to the end of the queue. An RTS shift-order adds a final waypoint.",
"semantics": "The declared placement is after every waiting command for the same plan owner."
},
"insert-next": {
"meaning": "The new order becomes the next order after the current one. A colony emergency repair runs before work already waiting.",
"semantics": "The declared placement is before every waiting command for the same plan owner."
}
}
},
"unmodified-command": {
"asks": "A new order arrives while another order is waiting. The player does not hold the key that adds an order to the queue. What happens?",
"rationale": "An order given without that key can replace the orders that wait in the queue, join the end of the queue, or be refused while its owner has an order waiting.",
"when": {
"any": [
{
"row-count": {
"context-commands": "non-empty"
}
},
{
"row-count": {
"targeted-verbs": "non-empty"
}
}
]
},
"otherwise": "No pointer command can enter a queue.",
"options": {
"replaces-waiting": {
"meaning": "The new order replaces every order waiting in its owner's queue. A hero turns toward the newest clicked destination.",
"semantics": "The unmodified placement clears waiting pointer commands for the same plan owner."
},
"always-appends": {
"meaning": "The new order goes to the end of its owner's queue. A colony keeps each new work mark.",
"semantics": "The unmodified placement is after every waiting pointer command for the same plan owner."
},
"rejected-while-busy": {
"meaning": "The new order is refused while its owner has an order waiting. A build tool accepts no second placement until the first is no longer waiting.",
"semantics": "An unmodified proposal is refused while its plan owner has a waiting pointer command."
}
}
}
},
"declares": {
"values": {},
"rows": {
"selection-gestures": {
"description": "Pointer gestures that replace, add, remove, or toggle actors or world objects in the current selection.",
"when-empty": "No pointer gesture changes the current world selection.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name in your game's words, such as point-select or box-select."
},
"gesture": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The pointer action that the game receives after physical input mapping, such as select-point or select-area."
},
"resolves-on": {
"type": "string",
"required": true,
"options": [
"press",
"release",
"drag-complete"
],
"description": "The pointer phase that settles the selection. A tactics point may settle on release; an RTS box settles when its drag completes."
},
"shape": {
"type": "string",
"required": true,
"options": [
"point",
"area"
],
"description": "Whether the gesture tests one pointer point or the cited dragged area."
},
"change": {
"type": "string",
"required": true,
"options": [
"replace",
"add",
"remove",
"toggle"
],
"description": "How the selectable results change the current selection. A strategy box may replace it while a modified click adds one unit."
},
"gesture-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say how the game recognizes this press, release, or drag. The rules include any drag threshold and the geometry of the area."
},
"candidates-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say which kinds of target can be selected. The rules say when the pointer point or the dragged area includes a target. They give the near-miss reach, when the game uses one. They give a complete tie-break. A point rule may return several candidates, as in double-click select-type."
}
}
},
"context-commands": {
"description": "Commands chosen directly from the classified world target under a pointer gesture, such as moving on ground or attacking an enemy.",
"when-empty": "No pointer gesture chooses a command directly from what lies under it.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name in your game's words, such as move-on-ground or attack-enemy."
},
"gesture": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The pointer action that the game receives after physical input mapping, such as world-command or context-order."
},
"resolves-on": {
"type": "string",
"required": true,
"options": [
"press",
"release",
"drag-complete"
],
"description": "The pointer phase that proposes the command. An action RPG may move on release while a colony designation completes as a drag."
},
"target-kind": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The mutually exclusive world classification that selects this row, such as ground, enemy, door, or buildable-tile."
},
"command": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The game command proposed by this row, such as move, basic-attack, open-door, or place-tower."
},
"gesture-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say how the game recognizes the pointer action and which phase completes it."
},
"target-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say how the game classifies what is under the pointer and what the exact target is. For nearest-within-reach, the rules also give the reach and the tie-break."
},
"area-declared-in": {
"type": "citation",
"when": {
"row": {
"resolves-on": [
"drag-complete"
]
}
},
"description": "Where your game's rules say what the dragged region is, whether its boundary is included, and how the region becomes the command target."
},
"receiver-condition": {
"type": "citation",
"description": "Where your game's rules say which receiver class this row is limited to, such as worker or soldier. This field is optional."
},
"command-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say what the command is. The rules name its receiver. They name its target. They say who owns the queue for each target. They say when the command is permitted. They say what happens when the target cannot be reached. They give the complete effect of the command when it is accepted and when it is refused."
}
}
},
"targeted-verbs": {
"description": "Abilities and verbs that use a pointer-captured world target, whether the verb or the target arrives first. Every targeting state can be left: through leave-targeting, a targeting cancellation row, or the cited start rule.",
"when-empty": "No chosen ability or verb waits for a world target from the pointer.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name in your game's words, such as artillery-target or use-key-on-door."
},
"verb": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The chosen ability or verb applied to the captured world target."
},
"order": {
"type": "string",
"required": true,
"options": [
"verb-first",
"target-first"
],
"description": "Whether the verb starts before target capture or arrives from a cited game action after the pointer captures the target."
},
"confirm-style": {
"type": "string",
"required": true,
"options": [
"separate-gesture",
"at-entry-position"
],
"description": "Whether confirmation needs another pointer gesture or uses the pointer snapshot captured when this verb entry begins."
},
"target-gesture": {
"type": "string",
"pattern": "kebab-case",
"when": {
"row": {
"order": [
"target-first"
]
}
},
"description": "The pointer action that captures the world target before the verb arrives."
},
"confirm-gesture": {
"type": "string",
"pattern": "kebab-case",
"when": {
"row": {
"confirm-style": [
"separate-gesture"
]
}
},
"description": "The action that separately confirms this target. It may be a pointer gesture or a cited non-pointer action, such as releasing the held ability key."
},
"resolves-on": {
"type": "string",
"required": true,
"options": [
"press",
"release",
"drag-complete"
],
"description": "The phase that this row uses. With a separate confirmation, it is the phase of the confirming gesture. For a target-first row, it is the phase that captures the target. For a verb-first row that confirms at the entry position, it is the phase that completes the cited entry action. A row that resolves on a completed drag also cites its region rule."
},
"after-dispatch": {
"type": "string",
"required": true,
"options": [
"leave-targeting",
"keep-targeting"
],
"description": "Whether a valid dispatched command ends targeting or keeps the same verb ready for another target. A tower tool may remain active for repeated placement."
},
"starts-when-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say which game action supplies the verb. For a target-first row, this action arrives after the target is captured."
},
"target-gesture-declared-in": {
"type": "citation",
"when": {
"row": {
"order": [
"target-first"
]
}
},
"description": "Where your game's rules say how the game recognizes the target-first pointer action and in which phase it captures the target."
},
"confirm-gesture-declared-in": {
"type": "citation",
"when": {
"row": {
"confirm-style": [
"separate-gesture"
]
}
},
"description": "Where your game's rules say how the game recognizes the confirmation gesture and which phase completes it."
},
"targets-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say how a target is captured. The rules name every valid target. They give the near-miss reach and the tie-break, when the game uses them. They give the complete test for an invalid target."
},
"area-declared-in": {
"type": "citation",
"when": {
"row": {
"resolves-on": [
"drag-complete"
]
}
},
"description": "Where your game's rules say what the dragged region is, whether its boundary is included, and how the region becomes the target of the verb."
},
"command-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say what the command is. The rules name its receiver. They say who owns the queue for each target. They say when the command is permitted. They say what the command costs. They say what happens when the target cannot be reached. They give the complete effect of the command, or its refusal."
}
}
},
"queue-modifiers": {
"description": "Modifier actions that add matching pointer commands to a queue.",
"when-empty": "No pointer modifier adds a command to a queue.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name in your game's words, such as queue-orders or urgent-work-next."
},
"modifier-action": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The mapped game action held or active when the pointer command completes."
},
"modifier-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say when this modifier action is active, what the capacity of the queue is, if it has one, and what happens when the queue has no free place."
},
"applies-to-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say to which context commands and targeted verbs this modifier applies. The rules name every one of them, and they name at least one row of this adoption."
}
}
},
"cancellations": {
"description": "Actions that end targeting, abort a selection drag, clear the orders waiting in a queue, or clear the current selection without proposing another command.",
"when-empty": "No action has a separate cancellation meaning in this adoption.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name in your game's words, such as cancel-ability-target or abort-box-select."
},
"action": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The pointer action or other game action that has a cancellation meaning in the cited state."
},
"resolves-on": {
"type": "string",
"required": true,
"options": [
"press",
"release",
"drag-cancel"
],
"description": "The phase of the action that applies the cancellation."
},
"active-state": {
"type": "string",
"required": true,
"options": [
"targeting",
"selection-drag",
"queued-commands",
"selection"
],
"description": "The state in which this row applies. The state named selection exists while the current selection is not empty. A cancel of an ability uses targeting. An RTS gesture that clears planned orders uses queued-commands."
},
"result": {
"type": "string",
"required": true,
"options": [
"ends-targeting",
"ends-drag",
"empties-queue",
"empties-selection"
],
"description": "The state change made without another world command. The result matches the row's active state; empties-queue clears the queue named at state-declared-in."
},
"action-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say how the game recognizes the cancellation action and which phase completes it."
},
"state-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules say when the affected state exists: the targeting state, the selection drag, the queue, or the selection."
}
}
}
}
},
"rules": {},
"origin": "https://opengdd.org/contracts/pointer-command-2",
"mechanism": [
"This text decides the order of the steps for what a pointer press, drag, or release over the world means; how selection, context command, and targeting states advance; where a queue modifier places a command; and what a cancellation clears. The questions and rows supply choices and cited game rules. They do not change the order.",
"A **game-facing pointer action** is the action received after Control options maps a mouse, touch, or stick-driven cursor input. A **pointer phase** is its press, release, completed drag, or canceled drag. A **pointer snapshot** is the world point and classified object under the pointer at that phase. The broader **game-facing action** also includes a cited non-pointer action that supplies a verb, confirmation, or cancellation; a non-pointer action has one completion phase, recorded as its press unless its cited rule names release. The **current selection** is one set of world objects. It starts empty unless a cited load or scene-entry rule supplies it, lasts until a rule changes it, and may also change through cited control-group recall, unit death, roster change, scene entry, or load. A **selection drag** starts when its cited gesture rule crosses the drag threshold and lasts until that same gesture completes or cancels. A **targeting state** holds one chosen ability or verb, or a target-first snapshot while it waits for the verb. A **command proposal** contains one command, its receiver shape, exact world target, and queue placement. A **waiting plan** contains pointer commands accepted for later execution for the owner named by the cited command rule. The questions and field descriptions call a waiting plan a queue, and call its commands orders. The game's Fixed command rules own whether a proposal is accepted and what it does.",
"### Recognize the gesture",
"1. Control options maps physical input to one game-facing pointer action. The matching cited gesture rule observes its press, movement, and release. This contract does not inspect device identity.",
"2. On press, record the pointer snapshot needed by the cited gesture rule. A row that resolves on press proceeds immediately, and no later drag or release result is inferred from that press for this contract.",
"3. While the pointer moves, the cited rule alone decides whether it remains a point gesture, becomes a drag, or is canceled. Its cited distance, duration, geometry, coordinate space, and boundary rule are read directly; this adoption contributes no number. A cited gesture rule may emit repeated completed phases while a control is held.",
"4. On release, create the final pointer snapshot. A release row resolves now. A recognized drag creates one `drag-complete` phase; an aborted drag creates one `drag-cancel` phase belonging to that drag's own game-facing action. One physical sequence cannot produce both a point result and a drag result unless the cited rule creates two distinct game-facing actions.",
"### Resolve cancellation and targeting",
"5. At each completed action phase, check cancellation before any other row. A cancellation row matches on three terms of its own: the game-facing action, its resolving phase, and the currently holding active state, checked in this order: targeting, selection-drag, queued-commands, selection. Apply its declared result and end this phase. It proposes no command and performs no selection change beyond `empties-selection`.",
"6. For `verb-first`, a game action named by `starts-when-declared-in` supplies the verb and begins its targeting entry. For `target-first`, the capture gesture — matched on its game-facing action, phase, and classified snapshot — captures the world target and begins a target-first state; then the cited game action — a verb coin, pie menu, or command card — supplies the verb. A second entry does not change the active targeting state unless the cited start rule explicitly replaces it.",
"7. While targeting is active, ordinary selection and direct-command rows do not run. Under `separate-gesture`, a matching confirmation action reads the pointer snapshot at its completion moment — for a non-pointer confirmation such as a key release, the pointer's position at that release. Under `at-entry-position`, confirmation reads the entry-time snapshot: the pointer position when a verb-first entry begins or the already captured target for target-first. A `drag-complete` row also reads its cited region rule, and validity is tested on that region. Apply `near-miss-resolution` through `targets-declared-in`, then test validity. A non-matching pointer action has no meaning here unless it matches a cancellation row.",
"8. For an invalid target, propose no command. Under `keep-targeting`, preserve the active verb. Under `leave-targeting`, clear it. The same pointer phase is not then matched against the context-command rows.",
"9. For a valid target, create one command proposal from the targeted row and its cited rules; under `current-selection` an empty selection makes it one refused proposal, as in step 12. Preserve the row's `after-dispatch` result with the proposal. A refused command is still a dispatched proposal, so refusal does not restore targeting unless the cited game rule starts a new instance.",
"### Resolve selection or a context command",
"10. With no active targeting state, find the one selection or context row that matches the game-facing action, pointer phase, and classified pointer snapshot. A context row with `receiver-condition` also matches the receiver class named by that citation; receiver class therefore participates in classification when a row cites it. A receiver-conditioned adoption keeps its receiver set homogeneous for that action: when rows cite different receiver classes for one action, phase, and target kind, the selection holds one class at a time under the receiver-condition citation. This version cannot express different commands for the members of one mixed selection. For one game-facing action and phase, selection rows, context rows, and target-first capture gestures have mutually exclusive classifications. Apply `near-miss-resolution` through the row's cited target or candidate rule. If no row matches, change no world-command state and record the unmatched classification in step 16.",
"11. For a selection row, compute its complete candidate set from the cited point or area rule. With an empty result, a `replace` row applies `empty-selection`; an `add`, `remove`, or `toggle` row always keeps the current selection, because an empty result gives such a row nothing to add, remove, or toggle. With a non-empty result, apply `replace`, `add`, `remove`, or `toggle` to the complete set. Commit the new selection once and end this pointer phase.",
"12. For a context row, copy its classified point or object as the command target. Under `fixed-actor`, read the fixed receiver from the cited command rule. Under `current-selection`, copy the complete current selection. An empty copy creates one refused proposal with no world effect and ends at this step; it never reaches queue placement or dispatch. Under `world-target`, attach no selected receiver and read that exact target's plan owner from the cited command rule. Create one command proposal and continue.",
"### Place and dispatch the command",
"13. Read queue modifiers only after the command, receiver, and target are fixed. A matching modifier changes placement, not meaning. Under `append-at-end`, place the proposal after every waiting pointer command for the same waiting-plan owner. Under `insert-next`, place it before those waiting commands and after the command already being carried out. The cited modifier rule owns plan capacity and the complete result of the refusal when no place is available; this contract never drops another command implicitly.",
"14. With a matching modifier, add the proposal at the position from step 13. Without one, read `unmodified-command`: `replaces-waiting` clears waiting pointer commands for the same owner, `always-appends` places the proposal after them, and `rejected-while-busy` records a refusal and stops when one is waiting. A proposal exists once per completed phase; a held modifier or update cannot add another copy within that phase. After a targeted proposal is dispatched, placed, or refused at this step, apply its row's `after-dispatch` result: `leave-targeting` ends the state and `keep-targeting` preserves it.",
"15. Submit each dispatched proposal to its cited Fixed command rule. That rule owns permission, cost, range, path request, the unreachable-destination case, effect, refusal, and whether the command already being carried out stops. A queued proposal is submitted when it reaches its declared place. Event resolution owns the order when several proposals share one instant.",
"16. Record the pointer result: gesture id, resolving phase, pointer snapshot, prior and final targeting state, prior and final selection when changed, command and receiver when proposed, target, queue modifier or unmodified placement outcome, cancellation when used, target validity for every targeted verb that reached a validity test, a no-matching-row result when applicable, and the cited game-rule result when available.",
"The order of the steps is: physical mapping, gesture recognition, cancellation, targeting entry, target confirmation, selection or context classification, receiver snapshot, queue placement, command dispatch, game rule, and same-instant event order. A later step never changes the pointer snapshot or receiver copied by an earlier step; classification may read receiver class without copying the receiver set."
],
"pack": "sha256:e5103351d21ef47e6f90b1e34ceba968cf5bf77ec393a38413f80aa8e442eee1",
"answers": {
"command-receiver": "current-selection",
"near-miss-resolution": "exact-point-only",
"empty-selection": "keep-selection",
"invalid-target": "keep-targeting",
"unmodified-command": "replaces-waiting"
},
"values": {},
"rows": {
"selection-gestures": [
{
"id": "add-ally-on-press",
"gesture": "add-ally",
"resolves-on": "press",
"shape": "point",
"change": "add",
"gesture-declared-in": "controls.add-ally",
"candidates-declared-in": "units.ally-selection"
},
{
"id": "toggle-hero",
"gesture": "toggle-hero",
"resolves-on": "release",
"shape": "point",
"change": "toggle",
"gesture-declared-in": "controls.toggle-hero",
"candidates-declared-in": "units.hero-selection"
},
{
"id": "remove-defeated-hero",
"gesture": "remove-hero",
"resolves-on": "release",
"shape": "point",
"change": "remove",
"gesture-declared-in": "controls.remove-hero",
"candidates-declared-in": "units.defeated-hero-selection"
}
],
"context-commands": [
{
"id": "move-hero-on-ground",
"gesture": "hero-order",
"resolves-on": "release",
"target-kind": "ground",
"command": "move-hero",
"gesture-declared-in": "controls.hero-order",
"target-declared-in": "arena.pointer-target-kinds",
"command-declared-in": "orders.move-hero"
}
],
"targeted-verbs": [
{
"id": "arc-stun-smart-cast",
"verb": "arc-stun",
"order": "verb-first",
"confirm-style": "at-entry-position",
"resolves-on": "press",
"after-dispatch": "leave-targeting",
"starts-when-declared-in": "abilities.choose-arc-stun",
"targets-declared-in": "abilities.arc-stun-targets",
"command-declared-in": "abilities.arc-stun-command"
}
],
"queue-modifiers": [],
"cancellations": [
{
"id": "cancel-aim-mode",
"action": "ability-key-again",
"resolves-on": "press",
"active-state": "targeting",
"result": "ends-targeting",
"action-declared-in": "controls.ability-key-again",
"state-declared-in": "abilities.aim-mode-state"
},
{
"id": "clear-hero-selection",
"action": "clear-selection-key",
"resolves-on": "press",
"active-state": "selection",
"result": "empties-selection",
"action-declared-in": "controls.clear-selection-key",
"state-declared-in": "units.hero-selection-state"
}
]
}
}