Mobile touch
mobile-touch · an adoption of Control options, 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 which physical inputs produce each action on every platform. It also covers complete input methods, named control presets, remapping, press styles, simpler alternatives, and device-motion inputs. This contract does not cover action prompts, input timing help, the choice between actions that share one input, or event order. The Action legibility contract covers action prompts and the choice between actions that share one input, the Input forgiveness contract covers input timing help, and the Event resolution contract covers event order.
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.
By default, how can players change the controls?
- Asked when
- the platform control sets list has at least one row.
- If not asked
- With no platform control set, this adoption makes no default remapping promise.
Why this is asked
A platform may offer fixed controls, presets, or free changes. This answer is the default answer. A platform row can choose another answer.
By default, what happens when an action needs a demanding press?
- Asked when
- the platform control sets list has at least one row.
- If not asked
- With no platform control set, this adoption makes no default demanding-input promise.
Why this is asked
A hold, rapid presses, a double press, or a button combination can stop a player from using an action that the player knows. This answer is the default answer.
Numbersno numbers
This contract has no numbers to set.
Rules1 rule
A rule is a check between the numbers. Validation reports a rule that fails.
-
Forbidden when Remapping default is Action and press style, and Demanding input default is Required as written.
Lists4 lists
Each list holds the rows this adoption supplies. A list can be empty.
Platform control sets
platform-control-sets
| Id | Platform declared in | Methods declared in | Input method coverage | Remapping | Settings rule declared in |
|---|---|---|---|---|---|
mobile | platforms.mobile-touch | controls.touch-only | one-method-covers-all | use-game-default | controls.touch-layout-editor-with-fixed-actions |
Control presets
control-presets
This adoption declares no control presets.
Action bindings
action-bindings
| Id | Platform control set | Preset | Context declared in | Action declared in | Physical input declared in | Action input | Press style | Motion use | Demanding input |
|---|---|---|---|---|---|---|---|---|---|
mobile-rotate-region | mobile | — | — | puzzle.rotate-tile | controls.rotate-touch-region | — | gesture | no-motion | use-game-default |
Simpler inputs
simpler-inputs
This adoption declares no simpler inputs.
Test inputsscope and seeds
Some tests need a scope or seeds from the adoption before they can run.
This adoption supplies no test inputs. Every test uses its default inputs.
Acceptance tests28 tests apply
The contract comes with 64 tests. A test that runs once per row is counted once for each row. Tests that do not apply to these answers are still listed, with the reason.
control-options-vocabulary
control options uses control sets, presets, bindings, action inputs, and demanding inputs
Applies to mobile-touch.
A control set is the complete current mapping for one platform and input method. A preset is an immutable named source set that can become current. A binding joins one physical input and press style to one candidate action. One physical activation emits one action input carrying every matched binding's action. A demanding input is a timed, held, rapid, repeated, double, simultaneous, input-sequence, or required-device-motion input.
Test steps and diagnostics
- Given
the
mobile-touchadoption and its cited control rules- When
- the control path is identified from platform selection through physical activation
- Then
- a control set is the complete current mapping for one platform and input method
- a preset is an immutable named source set that can become current
- a binding joins one physical input and press style to one candidate action
- one physical activation emits one action input carrying every matched binding's action
- a demanding input is a timed, held, rapid, repeated, double, simultaneous, input-sequence, or required-device-motion input
- Diagnostics
mobile-touch-current-setmobile-touch-action-input-log
platform-row-selects-exactly-when-cited · mobile
mobile is selected exactly for its cited platform and devices
Applies to the mobile row.
Platform row mobile is the one selected row exactly on the platform, edition, and supported devices at platforms.mobile-touch. It is not selected where that citation excludes it. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
platform-control-set row
mobileand the Fixed platform rule atplatforms.mobile-touch- When
- the game runs on each cited platform, edition, and supported device combination and on the nearest combination the citation excludes
- Then
mobileis the one selected row for every combination the citation coversmobileis not selected for a combination the citation excludes- the test leaves the covered combinations to
platforms.mobile-touchand restates nothing from it
- Diagnostics
mobile-touch-platform-selection
starting-control-set-follows-platform-rule · mobile
mobile starts with the control set chosen by its cited rule
Applies to the mobile row.
On first play for mobile, the complete starting control set comes from controls.touch-layout-editor-with-fixed-actions, and every first binding lookup reads it as current. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
a first play on platform row
mobileand the Fixed settings rule atcontrols.touch-layout-editor-with-fixed-actions- When
- the current set is first established
- Then
- the complete starting control set is the one selected through
controls.touch-layout-editor-with-fixed-actions - every first binding lookup reads that current set
- the test restates nothing from the cited rule
- the complete starting control set is the one selected through
- Diagnostics
mobile-touch-current-set
preset-selection-copies-complete-set
preset Row.id becomes current through its cited route
Does not apply to mobile-touch: control-presets has no rows.
input-method-coverage-holds · mobile
mobile input methods cover its actions as promised
Applies to the mobile row.
Audit class: observer-judged. An observer, not the running game, judges this in each preset-derived current set mobile can make current. For every action bound on the platform, under the complete methods and any required switch at controls.touch-only: the one complete method named by the citation performs every action bound on the platform without another method. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
platform row
mobile, every action bound on that platform, and the complete methods and any required switch atcontrols.touch-only- When
- in each preset-derived current set the platform can make current, an observer performs every action bound on the platform using the named method or methods
- Then
- the one complete method named by the citation performs every action bound on the platform without another method
- an observer, not the running game, judges this
- the test restates nothing from the cited rule
- Diagnostics
mobile-touch-mobile-observer-result
remapping-fixed-override
Row.id keeps fixed bindings by its row answer
Does not apply to mobile-touch: no row in platform-control-sets matches remapping fixed bindings.
remapping-fixed-default · mobile
mobile keeps fixed bindings by the default answer
Applies to the mobile row.
Audit class: observer-judged. An observer, not the running game, judges this. The row uses the default answer: every attempted change to an action's physical input or press style is refused, the current set stays unchanged, and the existing binding performs the action. Where this platform has a movable or resizable touch control, changing its layout while keeping its action is not a control change; where it has none, this test checks nothing about a touch control. The route is at controls.touch-layout-editor-with-fixed-actions; the test restates nothing from it.
Test steps and diagnostics
- Given
the current set for
mobileand its control setting route atcontrols.touch-layout-editor-with-fixed-actions- When
- an observer attempts to change an action's physical input and press style, then performs the action
- Then
- every control change is refused and the current set is unchanged
- the existing binding still performs the action
- where this platform has a movable or resizable touch control, changing its layout while keeping its action is not a control change; where it has none, this test checks nothing about a touch control
- an observer, not the running game, judges this
- Diagnostics
mobile-touch-mobile-observer-resultmobile-touch-change-logmobile-touch-current-set
remapping-swap-override
Row.id permits only exchanges by its row answer
Does not apply to mobile-touch: no row in platform-control-sets matches remapping swap only.
remapping-swap-default
Row.id permits only exchanges by the default answer
Does not apply to mobile-touch: remapping default is fixed bindings, not swap only.
remapping-presets-override
Row.id permits only preset selection by its row answer
Does not apply to mobile-touch: no row in platform-control-sets matches remapping presets only.
remapping-presets-default
Row.id permits only preset selection by the default answer
Does not apply to mobile-touch: remapping default is fixed bindings, not presets only.
remapping-free-override
Row.id permits free assignment by its row answer
Does not apply to mobile-touch: no row in platform-control-sets matches remapping any action any input.
remapping-free-default
Row.id permits free assignment by the default answer
Does not apply to mobile-touch: remapping default is fixed bindings, not any action any input.
remapping-press-style-override
Row.id permits input and press-style changes by its row answer
Does not apply to mobile-touch: no row in platform-control-sets matches remapping action and press style.
remapping-press-style-default
Row.id permits input and press-style changes by the default answer
Does not apply to mobile-touch: remapping default is fixed bindings, not action and press style.
binding-scope-follows-current-set · mobile-rotate-region
mobile-rotate-region exists in its declared control-set scope
Applies to the mobile-rotate-region row.
Binding mobile-rotate-region belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to mobile's base or freely remappable set. It exists throughout the selected control set, or only in the cited context where the row names one. For a preset or context that the row does not name, this test checks nothing.
Test steps and diagnostics
- Given
binding
mobile-rotate-regionon platform rowmobile- When
- the current set is inspected across its reachable control-set and play contexts
- Then
- the binding belongs to its named preset while that preset is current, where the row names one; otherwise it belongs to the platform's base or freely remappable set
- the binding exists throughout the selected control set, or only in the cited context where the row names one
- for a preset or context that the row does not name, this test checks nothing
- Diagnostics
mobile-touch-current-setmobile-touch-match-trace
binding-matches-cited-performance · mobile-rotate-region
mobile-rotate-region matches only its cited gesture performance
Applies to the mobile-rotate-region row.
For mobile-rotate-region, when the cited gesture completes under controls.rotate-touch-region, one action input carries the action at puzzle.rotate-tile. The nearest non-matching performance emits nothing from this binding. The test names both addresses and restates nothing from them.
Test steps and diagnostics
- Given
binding
mobile-rotate-region, actionpuzzle.rotate-tile, and the physical input, device, and performance atcontrols.rotate-touch-region- When
- the cited gesture completes in the current platform, device, method, and set, then the nearest non-matching performance is attempted
- Then
- the matching performance emits one action input carrying the action at
puzzle.rotate-tile - the non-matching performance emits nothing from this binding
- the test leaves the physical details to
controls.rotate-touch-regionand restates nothing from it
- the matching performance emits one action input carrying the action at
- Diagnostics
mobile-touch-match-tracemobile-touch-action-input-log
binding-context-settles-at-accepted-moment
the context of Row.id is decided at the accepted moment
Does not apply to mobile-touch: no matching row in action-bindings has every field this test uses (context-declared-in).
binding-preset-is-current
Row.id exists only while preset Bind preset is current
Does not apply to mobile-touch: no matching row in action-bindings has every field this test uses (preset).
shared-physical-activation-stays-one-input
Row.id shares action input Bind action input consistently
Does not apply to mobile-touch: no matching row in action-bindings has every field this test uses (action-input).
simpler-input-matches-named-binding
Row.id matches as binding Row.action binding
Does not apply to mobile-touch: simpler-inputs has no rows.
demanding-none-override
Row.id has an ordinary route by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input no demanding presses.
demanding-none-default · mobile-rotate-region
mobile-rotate-region has an ordinary route by the default answer
Applies to the mobile-rotate-region row.
Audit class: observer-judged. An observer, not the running game, judges this. The row uses the default answer: the action for mobile-rotate-region has an ordinary route without a setting change, and performing that route emits an action input carrying the action. A demanding input is not its only route.
Test steps and diagnostics
- Given
binding
mobile-rotate-regionand its cited action and physical-input rules- When
- an observer performs the covered action through its ordinary route without changing a setting
- Then
- the ordinary route produces an action input carrying the action at
puzzle.rotate-tile - no demanding input is the action's only route
- an observer, not the running game, judges this
- the ordinary route produces an action input carrying the action at
- Diagnostics
mobile-touch-mobile-rotate-region-observer-resultmobile-touch-action-input-log
demanding-simpler-press-style-override
the demanding press style of Row.id follows simpler-alternative by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input simpler alternative and press-style timed press or hold or rapid presses or repeated presses or double press or simultaneous inputs or input sequence and motion-use no motion or optional motion.
demanding-simpler-required-motion-override
the required motion of Row.id follows simpler-alternative by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input simpler alternative and motion-use required motion.
demanding-simpler-press-style-default
the demanding press style of Row.id follows simpler-alternative by the default answer
Does not apply to mobile-touch: demanding input default is no demanding presses, not simpler alternative.
demanding-simpler-required-motion-default
the required motion of Row.id follows simpler-alternative by the default answer
Does not apply to mobile-touch: demanding input default is no demanding presses, not simpler alternative.
demanding-setting-press-style-override
the demanding press style of Row.id follows player-can-change-it by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input player can change it and press-style timed press or hold or rapid presses or repeated presses or double press or simultaneous inputs or input sequence and motion-use no motion or optional motion.
demanding-setting-required-motion-override
the required motion of Row.id follows player-can-change-it by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input player can change it and motion-use required motion.
demanding-setting-press-style-default
the demanding press style of Row.id follows player-can-change-it by the default answer
Does not apply to mobile-touch: demanding input default is no demanding presses, not player can change it.
demanding-setting-required-motion-default
the required motion of Row.id follows player-can-change-it by the default answer
Does not apply to mobile-touch: demanding input default is no demanding presses, not player can change it.
demanding-required-press-style-override
the demanding press style of Row.id follows required-as-written by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input required as written and press-style timed press or hold or rapid presses or repeated presses or double press or simultaneous inputs or input sequence and motion-use no motion or optional motion.
demanding-required-required-motion-override
the required motion of Row.id follows required-as-written by its row answer
Does not apply to mobile-touch: no row in action-bindings matches demanding-input required as written and motion-use required motion.
demanding-required-press-style-default
the demanding press style of Row.id follows required-as-written by the default answer
Does not apply to mobile-touch: demanding input default is no demanding presses, not required as written.
demanding-required-required-motion-default
the required motion of Row.id follows required-as-written by the default answer
Does not apply to mobile-touch: demanding input default is no demanding presses, not required as written.
simpler-route-is-distinct
Row.id performs the same action without resembling a failed demanding input
Does not apply to mobile-touch: simpler-inputs has no rows.
device-motion-rule-holds · mobile-rotate-region
mobile-rotate-region follows its no-motion device-motion rule
Applies to the mobile-rotate-region row.
For mobile-rotate-region under controls.rotate-touch-region: no device motion is read while the cited non-motion performance emits the action input. This test names the address, restates nothing from it, and checks nothing about device-motion quality.
Test steps and diagnostics
- Given
binding
mobile-rotate-regionand its physical input and device atcontrols.rotate-touch-region- When
- the cited performance and the corresponding motion or non-motion comparison are each attempted
- Then
- no device motion is read while the cited non-motion performance emits the action input
- this test checks nothing about device-motion quality
- Diagnostics
mobile-touch-match-tracemobile-touch-action-input-log
one-physical-activation-emits-one-action-input
one physical activation emits one action input with all matched candidates
Applies to mobile-touch.
Each reachable physical activation emits one action input carrying every matched binding's action as a candidate. N matched actions remain one input with N candidates, never N inputs. Where no activation matches several bindings, this test checks nothing about several candidates.
Test steps and diagnostics
- Given
each reachable physical activation in the
mobile-touchadoption, including one that matches several bindings where the adoption declares one- When
- the current set is matched and the contract emits its result to the game
- Then
- the activation emits one action input
- that one input carries every matched binding's action as a candidate
- N matched actions remain one input with N candidates and never become N inputs
- where no activation matches several bindings, this test checks nothing about several candidates
- Diagnostics
mobile-touch-match-tracemobile-touch-action-input-logmobile-touch-candidate-set
action-input-stops-at-handoff
the action input stops at the contract boundary
Applies to mobile-touch.
The contract emits one action input with all matched candidates and stops there. Input forgiveness can supply the accepted moment; Action legibility, when adopted, selects a candidate before one action proposal. Otherwise the game's cited Fixed selection rule owns shared-candidate selection. This test checks nothing about forgiveness windows, offered-action presentation, candidate ordering, refusal of a proposal, or action effects.
Test steps and diagnostics
- Given
one action input emitted by the
mobile-touchadoption with all matched candidates- When
- the input crosses the contract boundary
- Then
- the emitted input is handed to Input forgiveness when adopted, which can supply the accepted moment, and then to Action legibility when adopted for candidate selection before one action proposal
- without Action legibility, the game's cited Fixed selection rule owns shared-candidate selection
- this test stops at emission and checks nothing about forgiveness windows, offered-action presentation, candidate ordering, refusal of a proposal, or action effects
- Diagnostics
mobile-touch-action-input-log
control-options-authority-order
control options keeps the order of its steps
Applies to mobile-touch.
The order of the steps is platform, defaults, starting set, accepted control change, current set, physical match, demanding-input answer, simpler route, device-motion rule, one action-input creation, accepted-moment shared-action choice, and one action proposal. A later step does not change an earlier decision.
Test steps and diagnostics
- Given
a run that reaches platform selection, control setup, a physical activation, and the action-input boundary
- When
- the decision trace is read in order
- Then
- the trace orders platform, defaults, starting set, accepted control change, current set, physical match, demanding-input answer, simpler route, device-motion rule, one action-input creation, accepted-moment shared-action choice, and one action proposal
- a later step does not change an earlier decision
- Diagnostics
mobile-touch-platform-selectionmobile-touch-change-logmobile-touch-current-setmobile-touch-match-tracemobile-touch-action-input-log
control-options-boundaries
the adoption makes no promise beyond control options
Applies to mobile-touch.
The contract makes no promise about system-level remapping, virtual-control layout editing, chord member lists, device-motion quality, or saved profiles. Moving or resizing a touch control while keeping its action is not a control change. Presentation of the current binding is owned by Action legibility when adopted, otherwise by the game's UI rules. Beyond its stated hand-off order, the contract makes no promise about an action input after emission.
Test steps and diagnostics
- Given
the
mobile-touchadoption and features adjacent to its control rules- When
- the adoption's promise boundary is reviewed
- Then
- the contract makes no promise about system-level remapping, virtual-control layout editing, chord member lists, device-motion quality, or saved profiles
- moving or resizing a touch control while keeping its action is not a control change
- presentation of the current binding is owned by Action legibility when adopted, otherwise by the game's UI rules
- the contract makes no promise about action-input behavior after emission except the stated hand-off order
- Diagnostics
mobile-touch-declaration-record
empty-row-sets-make-no-promise
empty row sets and absent default answers make no promise
Applies to mobile-touch.
This declaration check reads the adoption, not the running game. Where no platform row exists, no platform receives a physical-control promise, and the adoption makes no default remapping or demanding-input promise; where a platform row exists, this test checks nothing about these statements. Where no preset, binding, or simpler-input row exists, its row set makes its stated empty-set promise; where a row exists, this test checks nothing about that row set.
Test steps and diagnostics
- Given
the
mobile-touchadoption, not the running game- When
- a reviewer checks each row set and the two default answers that depend on a platform row
- Then
- where no platform-control-sets row exists, no platform receives a physical-control promise from this adoption; where a row exists, this test checks nothing about this statement
- where no control-presets row exists, no named control preset is offered; where a row exists, this test checks nothing about this statement
- where no action-bindings row exists, no physical input is promised to produce a game action; where a row exists, this test checks nothing about this statement
- where no simpler-inputs row exists, no demanding binding promises a separate simpler input without a setting change; where a row exists, this test checks nothing about this statement
- where no platform-control-sets row exists, this adoption makes no default remapping promise; where a platform row exists, this test checks nothing about this statement
- where no platform-control-sets row exists, this adoption makes no default demanding-input promise; where a platform row exists, this test checks nothing about this statement
- Diagnostics
mobile-touch-declaration-record
preset-platform-join
declaration check: preset Row.id names a platform row in this adoption
Does not apply to mobile-touch: control-presets has no rows.
binding-platform-join · mobile-rotate-region
declaration check: binding mobile-rotate-region names a platform row in this adoption
Applies to the mobile-rotate-region row.
This declaration check reads the adoption, not the running game. Binding mobile-rotate-region must name an existing platform-control-sets row in this adoption: mobile. When the named platform row is missing or misspelled, the adoption is invalid, and this test fails.
Test steps and diagnostics
- Given
the
mobile-touchadoption and bindingmobile-rotate-region, not the running game- When
- a reviewer checks the platform row that it names
- Then
- a platform-control-sets row with id
mobileexists in this adoption - a missing or misspelled platform row makes the adoption invalid, and this test fails
- a platform-control-sets row with id
- Diagnostics
mobile-touch-declaration-record
binding-preset-join
declaration check: binding Row.id names a preset on the same platform
Does not apply to mobile-touch: no matching row in action-bindings has every field this test uses (preset).
optional-motion-has-no-motion-sibling
declaration check: optional-motion binding Row.id has a no-motion binding for the same action
Does not apply to mobile-touch: no row in action-bindings matches motion-use optional motion.
simpler-binding-join
declaration check: simpler route Row.id names a binding in this adoption
Does not apply to mobile-touch: simpler-inputs has no rows.
presets-only-has-complete-choice
declaration check: every presets-only platform has two selectable complete presets
Applies to mobile-touch.
This declaration check reads the adoption, not the running game. Under the contract, every platform whose effective answer is presets-only must have at least two presets whose availability is starting-and-selectable or player-selectable, and every preset maps every action bound on that platform. For a platform with another effective answer, this test checks nothing. A missing choice or incomplete preset makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
mobile-touchadoption, not the running game- When
- a reviewer resolves each platform row's effective remapping answer and compares its preset and binding rows
- Then
- each platform whose effective answer is presets-only has at least two control-presets rows whose availability is starting-and-selectable or player-selectable
- every preset for that platform maps every action bound on the platform with a matching action-bindings row
- for a platform with another effective answer, this test checks nothing
- a missing choice or incomplete preset makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
simpler-answer-has-row · mobile-rotate-region
declaration check: every demanding simpler-alternative binding has a simpler row
Applies to the mobile-rotate-region row.
This declaration check reads the adoption, not the running game. If mobile-rotate-region has a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row must name it. Otherwise this test checks nothing. A missing simpler row makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
mobile-touchadoption and bindingmobile-rotate-region, not the running game- When
- a reviewer resolves the binding's effective demanding-input answer and classifies its cited performance
- Then
- if
mobile-rotate-regionhas a demanding press style or requires device motion, and its effective answer is simpler-alternative, at least one simpler-inputs row names it - otherwise this test checks nothing
- a missing simpler row makes the adoption invalid, and this test fails
- if
- Diagnostics
mobile-touch-declaration-record
no-demanding-answer-has-ordinary-route · mobile-rotate-region
declaration check: every no-demanding binding has an ordinary route
Applies to the mobile-rotate-region row.
This declaration check reads the adoption and its cited prose, not the running game. Under an effective no-demanding-presses answer, mobile-rotate-region must have a non-demanding press style and not require device motion, or have a cited ordinary route to the same action. Under another answer, this test checks nothing. A demanding-only route makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
mobile-touchadoption, bindingmobile-rotate-region, and its cited prose, not the running game- When
- a reviewer resolves the binding's effective demanding-input answer
- Then
- if the effective answer is no-demanding-presses,
mobile-rotate-regionhas a non-demanding press style and does not require device motion, or its cited prose states an ordinary route to the same action - otherwise this test checks nothing
- a demanding-only route makes the adoption invalid, and this test fails
- if the effective answer is no-demanding-presses,
- Diagnostics
mobile-touch-declaration-record
forbidden-effective-pair-does-not-reappear
declaration check: no platform or binding recreates the forbidden effective pair
Applies to mobile-touch.
This declaration check reads the adoption, not the running game. The contract's demanding-input field forbids a binding from having effective required-as-written on a platform with effective action-and-press-style. A row override that recreates this forbidden pair makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
mobile-touchadoption, not the running game- When
- a reviewer resolves every platform's effective remapping answer and every binding's effective demanding-input answer
- Then
- no binding has effective required-as-written on a platform with effective action-and-press-style
- any platform-row or binding-row override that recreates that pair makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
settings-citation-covers-effective-change-policy · mobile
declaration check: mobile's settings citation covers its effective policy
Applies to the mobile row.
This declaration check reads the adoption and controls.touch-layout-editor-with-fixed-actions, not the running game. Under any-action-any-input or action-and-press-style, that citation must state visible conflict handling before use; action-and-press-style must also state the press styles offered for each action. Under swap-only, it must state that a swap exchanges two existing assignments. Under presets-only, it must state that selection replaces the whole set and an individual binding change is refused. Under fixed-bindings, it must state the absence of changes. A missing duty makes the adoption invalid, and this test fails. This test checks nothing about reachability beyond what the citation states.
Test steps and diagnostics
- Given
the
mobile-touchadoption, platform rowmobile, andcontrols.touch-layout-editor-with-fixed-actions, not the running game- When
- a reviewer resolves the row's effective remapping answer and checks the cited rule
- Then
- under any-action-any-input or action-and-press-style, the citation states visible conflict handling before use
- under action-and-press-style, the citation states the press styles offered for each action
- under swap-only, the citation states that a swap exchanges two existing assignments
- under presets-only, the citation states that selection replaces the whole set and an individual binding change is refused
- under fixed-bindings, the citation states the absence of changes
- a missing duty makes the adoption invalid, and this test fails
- this test checks nothing about reachability beyond what the citation states
- Diagnostics
mobile-touch-declaration-record
shared-action-input-declaration-agrees
declaration check: rows sharing an activation agree on one action input
Applies to mobile-touch.
This declaration check reads the adoption and its cited physical activations and contexts, not the running game. Under the contract, one group contains only rows that can be current together: they use the same platform row, either all omit a preset or all name the same preset, have no disjoint cited contexts, and share one physical activation. Rows in mutually exclusive presets or disjoint contexts are not one group, and this test checks nothing about whether their action-input values agree. Every row in a multi-binding group supplies and agrees on one value, and the emitted input carries every matched action as a candidate. A lone binding's name can remain implicit, and this test checks nothing about a shared value for a lone binding. A missing, different, or split value makes the adoption invalid, and this test fails. This test checks nothing about a paired Action legibility adoption.
Test steps and diagnostics
- Given
the
mobile-touchadoption and the physical activations, platforms, presets, and contexts described by its binding rows and citations, not the running game- When
- a reviewer groups rows that can be current together and share one physical activation
- Then
- one group contains only rows on the same platform row that either all omit a preset or all name the same preset, have no disjoint cited contexts, and share one physical activation
- rows in mutually exclusive presets or disjoint cited contexts are not one group, and this test checks nothing about whether their action-input values agree
- every group with several bindings supplies one action-input value shared by every row in that group
- the emitted input carries every matched binding's action as a candidate
- a lone binding's action-input name can remain implicit, and this test checks nothing about a shared value for a lone binding
- a missing, different, or split shared value makes the adoption invalid, and this test fails
- this test checks nothing about a paired Action legibility adoption
- Diagnostics
mobile-touch-declaration-recordmobile-touch-candidate-set
rows-do-not-duplicate-meaning
declaration check: no two rows mean the same platform, preset, or binding
Applies to mobile-touch.
This declaration check reads the adoption and its cited prose, not the running game. No two rows can mean the same platform, preset, binding, or simpler alternative for one binding. The contract sets no maximum row count. A duplicate meaning makes the adoption invalid, and this test fails.
Test steps and diagnostics
- Given
the
mobile-touchadoption and its cited prose, not the running game- When
- a reviewer compares every pair of rows in each row set
- Then
- no two platform-control-sets rows mean the same platform, edition, devices, and policy scope
- no two control-presets rows mean the same preset
- no two action-bindings rows mean the same binding
- no two simpler-inputs rows mean the same alternative for one binding
- the contract imposes no maximum row count
- a duplicate meaning makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
platform-citation-duty · mobile
declaration check: mobile's platform citation states its duty
Applies to the mobile row.
This declaration check reads the adoption and platforms.mobile-touch, not the running game. The citation must name one platform or edition and its supported devices; different control behavior belongs in another row. A missing duty makes the adoption invalid, and this test fails. The test names the address and restates nothing from it.
Test steps and diagnostics
- Given
the
mobile-touchadoption andplatforms.mobile-touch, not the running game- When
- a reviewer checks the citation's meaning
- Then
platforms.mobile-touchnames one platform or edition and its supported devices, with different control behavior in another row- a missing duty makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
methods-citation-duty · mobile
declaration check: mobile's methods citation states its duty
Applies to the mobile row.
This declaration check reads the adoption and controls.touch-only, not the running game. The citation must list every complete input method for mobile and any required switch. 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
mobile-touchadoption andcontrols.touch-only, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.touch-onlylists every complete input method formobileand any required switch between methods- a missing duty makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
settings-rule-citation-duty · mobile
declaration check: mobile's settings citation states its duty
Applies to the mobile row.
This declaration check reads the adoption and controls.touch-layout-editor-with-fixed-actions, not the running game. The citation must always state mobile's control menu. Where the platform declares a preset, it must state preset selection. Under effective any-action-any-input or action-and-press-style, it must state conflict handling; action-and-press-style must also state the press styles offered for each action. Under effective fixed-bindings, it must state the explicit absence of changes. For a duty outside its stated condition, this test checks nothing. 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
mobile-touchadoption andcontrols.touch-layout-editor-with-fixed-actions, not the running game- When
- a reviewer resolves
mobile's effective remapping answer and checks the citation's meaning
- a reviewer resolves
- Then
controls.touch-layout-editor-with-fixed-actionsstatesmobile's control menu- where the platform has a control-presets row, the citation states preset selection; where it has none, this test checks nothing about preset selection
- under effective any-action-any-input or action-and-press-style, the citation states conflict handling; under another effective answer, this test checks nothing about conflict handling
- under effective action-and-press-style, the citation states the press styles offered for each action; under another effective answer, this test checks nothing about the offered press styles
- under effective fixed-bindings, the citation states the explicit absence of changes; under another effective answer, this test checks nothing about the absence of changes
- a missing duty makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
preset-selection-citation-duty
declaration check: preset Row.id's selection citation states its duty
Does not apply to mobile-touch: control-presets has no rows.
binding-action-citation-duty · mobile-rotate-region
declaration check: mobile-rotate-region's action citation states its duty
Applies to the mobile-rotate-region row.
This declaration check reads the adoption and puzzle.rotate-tile, not the running game. The citation must name the game action that mobile-rotate-region contributes as a candidate. 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
mobile-touchadoption andpuzzle.rotate-tile, not the running game- When
- a reviewer checks the citation's meaning
- Then
puzzle.rotate-tilenames the game action thatmobile-rotate-regioncontributes as a candidate- a missing duty makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
binding-physical-input-citation-duty · mobile-rotate-region
declaration check: mobile-rotate-region's physical-input citation states its duty
Applies to the mobile-rotate-region row.
This declaration check reads the adoption and controls.rotate-touch-region, not the running game. The citation must name mobile-rotate-region's physical input, supplying device, and the gesture completion. 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
mobile-touchadoption andcontrols.rotate-touch-region, not the running game- When
- a reviewer checks the citation's meaning
- Then
controls.rotate-touch-regionnames the physical input, its supplying device, and the gesture completion formobile-rotate-region- a missing duty makes the adoption invalid, and this test fails
- Diagnostics
mobile-touch-declaration-record
binding-context-citation-duty
declaration check: Row.id's context citation states its duty
Does not apply to mobile-touch: no matching row in action-bindings has every field this test uses (context-declared-in).
simpler-alternative-citation-duty
declaration check: Row.id's alternative citation states its duty
Does not apply to mobile-touch: simpler-inputs has no rows.
simpler-distinction-citation-duty
declaration check: Row.id's distinction citation states its duty
Does not apply to mobile-touch: simpler-inputs has no rows.
control-options-hold
control options holds for the whole run
Applies to mobile-touch.
Across every platform row on its cited devices, every preset, every binding, and every simpler route of the audited run, every accepted control change follows the platform's effective remapping answer and every refused change is refused; every binding matches only under its cited performance and emits one action input; every demanding binding meets its effective answer; every simpler route produces the same action distinguishably; every device-motion rule holds; and no physical activation produces more than one action input.
Test steps and diagnostics
- Holds
every accepted control change followed the platform's effective remapping answer and every refused change was refused; every binding matched only under its cited performance and emitted one action input; every demanding binding met its effective answer; every simpler route produced the same action distinguishably; every device-motion rule held; no physical activation produced more than one action input
- Seeds
["audit-a","audit-b"]- Scope
every platform row on its cited devices, every preset, every binding, and every simpler route of the audited run- Diagnostics
mobile-touch-platform-selectionmobile-touch-change-logmobile-touch-current-setmobile-touch-match-tracemobile-touch-action-input-logmobile-touch-observer-resultmobile-touch-setting-state
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": "control-options",
"version": 2,
"summary": "This contract covers which physical inputs produce each action on every platform. It also covers complete input methods, named control presets, remapping, press styles, simpler alternatives, and device-motion inputs. This contract does not cover action prompts, input timing help, the choice between actions that share one input, or event order. The Action legibility contract covers action prompts and the choice between actions that share one input, the Input forgiveness contract covers input timing help, and the Event resolution contract covers event order.",
"questions": {
"remapping-default": {
"asks": "By default, how can players change the controls?",
"rationale": "A platform may offer fixed controls, presets, or free changes. This answer is the default answer. A platform row can choose another answer.",
"when": {
"row-count": {
"platform-control-sets": "non-empty"
}
},
"otherwise": "With no platform control set, this adoption makes no default remapping promise.",
"options": {
"fixed-bindings": {
"meaning": "The controls cannot be changed in the game. A puzzle game always keeps rotate on the space bar.",
"semantics": "No player-facing setting changes an action's physical input or press style."
},
"swap-only": {
"meaning": "Existing controls can only exchange actions. A platformer can swap jump and dash, but an unused button cannot receive either action.",
"semantics": "A supported binding can exchange its current action with another supported binding; no action can move independently to an otherwise unused input."
},
"presets-only": {
"meaning": "Players can choose only between presets. An action game offers the presets Default and Alternate, and no single button can be changed.",
"semantics": "The player may select a complete declared preset but cannot change one binding independently inside that preset. The platform offers at least two presets whose availability is starting-and-selectable or player-selectable."
},
"any-action-any-input": {
"meaning": "Any action can move to any supported input. A strategy game can move end turn from Enter to an unused mouse button.",
"semantics": "Every covered action can be assigned independently to any supported remappable input, including an otherwise unassigned input; conflicts are resolved visibly before use."
},
"action-and-press-style": {
"meaning": "Both the input and the press style can change. An adventure game can move interact to another button and change a hold into one press.",
"semantics": "Every covered action can change to a supported input and to any press style that its cited platform rule offers for that action."
}
}
},
"demanding-input-default": {
"asks": "By default, what happens when an action needs a demanding press?",
"rationale": "A hold, rapid presses, a double press, or a button combination can stop a player from using an action that the player knows. This answer is the default answer.",
"when": {
"row-count": {
"platform-control-sets": "non-empty"
}
},
"otherwise": "With no platform control set, this adoption makes no default demanding-input promise.",
"options": {
"no-demanding-presses": {
"meaning": "No action needs a demanding press. A card game plays a selected card with one ordinary activation.",
"semantics": "No covered binding requires timed, held, rapid, repeated, double, simultaneous, directional-sequence, or device-motion input as its only route to the action."
},
"simpler-alternative": {
"meaning": "Every demanding press has a distinct simpler route with no setting change. A repair game offers a separate tap button beside its hold-to-repair control.",
"semantics": "Every covered demanding binding has a declared alternative that performs the same action without configuration."
},
"player-can-change-it": {
"meaning": "A setting can make the press easier. A racing game can change a held pit command into one ordinary press.",
"semantics": "A player-facing setting replaces each covered demanding press with a declared easier press style before play uses the binding."
},
"required-as-written": {
"meaning": "The demanding press remains required. A rhythm special still needs two buttons together and has no simpler route from this contract.",
"semantics": "The covered demanding binding has no simpler alternative or press-style setting promised by this adoption."
}
}
}
},
"declares": {
"values": {},
"rows": {
"platform-control-sets": {
"description": "Supported platforms or editions and their complete control policies. A separate row is required whenever mappings or options differ.",
"when-empty": "No platform receives a physical-control promise from this adoption.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name for the platform or edition in your game's words, such as pc or console-gamepad."
},
"platform-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules name one platform or edition and its supported devices. Use another row when the control behavior differs."
},
"methods-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules list the complete input methods and any required switch between them. A PC row may name keyboard and pointer as one mixed method."
},
"input-method-coverage": {
"type": "string",
"required": true,
"options": [
"one-method-covers-all",
"player-chooses-method",
"mixed-methods-needed"
],
"description": "Whether one named method covers every action bound on the platform, several named methods each do so, or the named methods must be mixed. A console may offer complete gamepad and accessibility-controller methods."
},
"remapping": {
"type": "string",
"required": true,
"options": [
"use-game-default",
"fixed-bindings",
"swap-only",
"presets-only",
"any-action-any-input",
"action-and-press-style"
],
"description": "The platform's remapping policy. Use the default answer, or choose another answer for this row. A console edition may offer presets while the PC edition allows free assignment."
},
"settings-rule-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules state the platform's control menu. The rules also state what the platform's effective remapping answer needs: preset selection, conflict handling, or the press styles offered for each action. When bindings are fixed, the rules state explicitly that no changes are possible."
}
}
},
"control-presets": {
"description": "Named complete binding sets offered on a platform. A preset maps every action bound on its platform.",
"when-empty": "No named control preset is offered.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name for the preset in your game's words, such as gamepad-default or gamepad-alternate."
},
"platform-control-set": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The supported platform or edition that offers this preset."
},
"label": {
"type": "string",
"required": true,
"description": "The player-facing preset name, such as Standard or Southpaw."
},
"availability": {
"type": "string",
"required": true,
"options": [
"starting-and-selectable",
"player-selectable",
"mode-selected"
],
"description": "Whether this preset is the starting set and remains selectable, is another selectable set, or follows a cited player mode. An assisted-play mode may select its own complete preset."
},
"selection-rule-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules state the route that selects this preset and makes its matching action-binding rows current."
}
}
},
"action-bindings": {
"description": "Physical inputs that produce actions on a platform or inside one named preset.",
"when-empty": "No physical input is promised to produce a game action.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name in your game's words for the platform, the action, and the input, such as pc-jump-space. A per-character control set names the character too."
},
"platform-control-set": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The supported platform or edition where this binding exists."
},
"preset": {
"type": "string",
"pattern": "kebab-case",
"description": "The preset that contains this binding. When this field is absent, the binding belongs to the platform's current base set or its freely remappable set. On a platform where players can change controls, the preset is the starting set. Accepted changes change only the current copy, not the preset."
},
"context-declared-in": {
"type": "citation",
"description": "Where your game's rules state the context in which this binding exists, such as a vehicle layer, menu, training mode, or unlock gate. When this field is absent, the binding exists throughout the selected control set."
},
"action-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules name the game action that this binding contributes as a candidate."
},
"physical-input-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules name the physical input and the device that supplies it. The physical input is a key, button, axis, touch region, gesture, directional sequence, or device-motion input."
},
"action-input": {
"type": "string",
"pattern": "kebab-case",
"description": "A name for the one input that the game receives from this physical activation. Give the name when several bindings use the same physical activation."
},
"press-style": {
"type": "string",
"required": true,
"options": [
"press",
"release",
"timed-press",
"hold",
"rapid-presses",
"repeated-presses",
"double-press",
"simultaneous-inputs",
"continuous-axis",
"gesture",
"input-sequence"
],
"description": "The physical performance required by this binding. A timed press has a target moment, rapid presses have a rate, repeated presses have a count, and an input sequence is a directional sequence completed by a press."
},
"motion-use": {
"type": "string",
"required": true,
"options": [
"no-motion",
"optional-motion",
"required-motion"
],
"description": "Whether this binding uses no device motion, is an optional device-motion route beside another binding, or requires device motion. A handheld aim action may offer tilt as an alternative to the stick. A required-motion binding is demanding because of its motion. A press-style setting does not make it easier, so its easier route is a simpler alternative or another binding. An optional-motion binding has a no-motion binding for the same action on the same platform and preset."
},
"demanding-input": {
"type": "string",
"required": true,
"options": [
"use-game-default",
"no-demanding-presses",
"simpler-alternative",
"player-can-change-it",
"required-as-written"
],
"description": "The demanding-input answer of this action binding. Use the default answer, or choose another answer for this row. A repeated crafting input may allow a hold even when combat combinations remain fixed. No binding answers required-as-written on a platform whose effective remapping is action-and-press-style."
}
}
},
"simpler-inputs": {
"description": "Separate simpler inputs that work without a setting change, for bindings whose effective demanding-input answer promises one.",
"when-empty": "No demanding binding promises a separate simpler input without a setting change.",
"record": {
"id": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"unique": true,
"description": "A short name for the alternative in your game's words, such as repair-tap-alternative."
},
"action-binding": {
"type": "string",
"required": true,
"pattern": "kebab-case",
"description": "The demanding binding for which this route is the simpler alternative."
},
"alternative-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules name the physical input and the ordinary press style that perform the same game action without a setting change."
},
"distinction-rule-declared-in": {
"type": "citation",
"required": true,
"description": "Where your game's rules prove that a successful use of this alternative cannot be mistaken for a failure to finish the demanding input."
}
}
}
}
},
"rules": {
"press-style-change-needs-a-setting-answer": {
"forbid": {
"all": [
{
"flag": {
"remapping-default": [
"action-and-press-style"
]
}
},
{
"flag": {
"demanding-input-default": [
"required-as-written"
]
}
}
]
},
"message": "Controls that let players change a press style cannot also require every demanding press exactly as written."
}
},
"origin": "https://opengdd.org/contracts/control-options-2",
"mechanism": [
"This text decides the order of the steps for platform selection, preset choice, remapping, physical-input matching, press style, simpler alternatives, device-motion use, and creation of action inputs. The questions and rows supply choices and cited game rules. They do not change the order.",
"A **control set** is the complete current mapping for one platform and input method. A **preset** is a named immutable source set that can become current. A **binding** joins one physical input and press style to one candidate action. An **action input** is the one signal that the game receives from a physical activation; it carries every matched binding's action as a candidate. Bindings that can be current together and share one physical activation share its optional `action-input` name, while a lone binding's name may remain implicit. A **demanding input** is a timed, held, rapid, repeated, double, simultaneous, input-sequence, or required-device-motion input.",
"1. Select exactly one matching platform-control-set from the running platform, edition, and supported device rules.",
"2. Resolve the platform's effective remapping answer. A row value other than `use-game-default` applies. Otherwise `remapping-default` applies.",
"3. Establish the starting control set from the platform's cited rule. When a preset is selected, copy its complete matching action-binding rows into the current set. The preset itself remains unchanged.",
"4. Apply control changes only through the effective remapping answer. Fixed bindings refuse all changes. Swap-only exchanges two existing assignments. Presets-only replaces the whole set with another declared preset. Free assignment moves one action independently and resolves conflicts before use. Action-and-press-style also permits a supported press-style change.",
"5. After an accepted change, the resulting complete set becomes current. Every later binding lookup reads that set, and each binding row's promises follow its action to the input the current set assigns. Presentation of the current binding is owned by Action legibility when adopted, otherwise by the game's UI rules.",
"6. On physical input, read every binding with a matching physical input and performance in the current platform, device, method, and preset-derived set. A press, release, hold, repeated activation, double activation, simultaneous group, axis, gesture, directional input sequence, or device-motion input matches only under its cited Fixed rule. An optional binding context makes the match provisional. Whether that context holds is decided at the accepted moment. Step 11 says how the accepted moment is determined. Rows that can be current together and share one physical activation agree on one `action-input` value. A physical input cited by a `simpler-inputs` row matches as if it were its named binding: it emits that binding's action input and contributes the same action.",
"7. Resolve the binding's effective demanding-input answer. A row value other than `use-game-default` applies. Otherwise `demanding-input-default` applies.",
"8. Under no-demanding-presses, the covered action has an ordinary route. Under player-can-change-it, the selected setting supplies the easier current press style. Under required-as-written, an incomplete demanding input produces no action input from this contract.",
"9. Under simpler-alternative, the demanding route and every matching simpler row remain available together without configuration. The alternative produces the same action only through its distinct cited input; failure to finish the demanding route never becomes the alternative by itself.",
"10. A `no-motion` binding reads no device motion. An `optional-motion` binding contributes the same action as its non-device-motion alternative when its gesture completes. A `required-motion` binding produces no action input from a non-device-motion attempt.",
"11. First, the physical input occurs. Then this contract emits the action input. Then Input forgiveness, when adopted, may shift the accepted moment. Then Action legibility, when adopted, selects the offered candidate at the accepted moment. The result is one action proposal. Thus an interact buffered during a cutscene evaluates candidates in the situation where the input is accepted, not the situation where it was pressed. The emitted action input carries every matched binding's action as a candidate; it is one input with N candidates, never N inputs.",
"12. When Action legibility is adopted, its shared-input case consumes that one action input and selects one candidate. Otherwise the game's cited Fixed selection rule resolves shared candidates, and the game's UI rules own their presentation. Event resolution begins only after the one action proposal exists.",
"The order of the steps is: platform, defaults, starting set, accepted control change, current set, physical match, demanding-input answer, simpler route, device-motion rule, one action-input creation, accepted-moment shared-action choice, and one action proposal."
],
"pack": "sha256:af872c7dbbd7b7faeacfbfb6f9015a7e9988a6e44b4726318aa9f91e20fe39b2",
"answers": {
"remapping-default": "fixed-bindings",
"demanding-input-default": "no-demanding-presses"
},
"values": {},
"rows": {
"platform-control-sets": [
{
"id": "mobile",
"platform-declared-in": "platforms.mobile-touch",
"methods-declared-in": "controls.touch-only",
"input-method-coverage": "one-method-covers-all",
"remapping": "use-game-default",
"settings-rule-declared-in": "controls.touch-layout-editor-with-fixed-actions"
}
],
"control-presets": [],
"action-bindings": [
{
"id": "mobile-rotate-region",
"platform-control-set": "mobile",
"action-declared-in": "puzzle.rotate-tile",
"physical-input-declared-in": "controls.rotate-touch-region",
"press-style": "gesture",
"motion-use": "no-motion",
"demanding-input": "use-game-default"
}
],
"simpler-inputs": []
}
}