Controls

The pad as the game reads it: the 16-bit button word, the analog sticks, and the markup tag that draws each button in text. Coney drives everything as a gamepad with analog sticks; on a PC pad the face buttons are positional (south is cross).

What is complete

Every button bit and both sticks are listed. What each does on foot is still to be written; the front end's accept and back are known (Front end).

18 entries. Data: research/references/controls.yaml.

pad

18 entries.

Input	Action	Bit	Glyph
L2		0x0001	<L2>
R2		0x0002	<R2>
L1		0x0004	<L1>
R1		0x0008	<R1>
triangle	Menus: back, on release.	0x0010	<T>
circle	Menus: back, on release.	0x0020	<O>
cross	Menus: accept, on release.	0x0040	<X>
square		0x0080	<S>
SELECT		0x0100	<SELECT>
L3		0x0200	<L3>
R3		0x0400	<R3>
START		0x0800	<START>
d-pad up	Menus: move up (auto-repeat).	0x1000	<DU>
d-pad right	Menus: move right (auto-repeat).	0x2000	<DR>
d-pad down	Menus: move down (auto-repeat).	0x4000	<DD>
d-pad left	Menus: move left (auto-repeat).	0x8000	<DL>
left stick	On foot: move; speed follows the deflection. Menus: move past half deflection.		<LAS>
right stick			<RAS>

Sources and evidence

Evidence levels used: inferred.

• pad record and libpad layout (docs/research/frontend.md#input)

Fields

Field	Type	Hand-written	Meaning
id	str		Our stable id.
context	str		Where it applies: pad, menus, on foot, scripts ...
input	str	yes	The pad input (gamepad with analog sticks).
action	str	yes	What it does there.
bit	hex		Bit in the game's button word.
glyph	str		The markup tag that shows its icon in text.
source	str	yes	Where the entry comes from: a script and binding, an address, a chunk.
evidence	str	yes	How we know: confirmed-code, confirmed-runtime, inferred or speculative (evidence levels).
notes	str	yes	Our own short notes.