Sandbox / type
GamepadCode
Sandbox.GamepadCode Overview
Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.
Generated declaration summary
GamepadCode is a declared enum in the pinned release metadata.
Automatically derived from the pinned declaration; this is not a reviewed tutorial or runtime test.
Exact identity & snapshot
Type relationships
Declarations owned by this type
- Sandbox.GamepadCode.A enum_value
- Sandbox.GamepadCode.B enum_value
- Sandbox.GamepadCode.BUTTONS_MAX enum_value
- Sandbox.GamepadCode.DpadEast enum_value
- Sandbox.GamepadCode.DpadNorth enum_value
- Sandbox.GamepadCode.DpadSouth enum_value
- Sandbox.GamepadCode.DpadWest enum_value
- Sandbox.GamepadCode.Guide enum_value
- Sandbox.GamepadCode.LeftJoystickButton enum_value
- Sandbox.GamepadCode.LeftTrigger enum_value
- Sandbox.GamepadCode.Misc1 enum_value
- Sandbox.GamepadCode.None enum_value
- Sandbox.GamepadCode.Paddle1 enum_value
- Sandbox.GamepadCode.Paddle2 enum_value
- Sandbox.GamepadCode.Paddle3 enum_value
- Sandbox.GamepadCode.Paddle4 enum_value
- Sandbox.GamepadCode.RightJoystickButton enum_value
- Sandbox.GamepadCode.RightTrigger enum_value
- Sandbox.GamepadCode.SwitchLeftBumper enum_value
- Sandbox.GamepadCode.SwitchLeftMenu enum_value
- Sandbox.GamepadCode.SwitchRightBumper enum_value
- Sandbox.GamepadCode.SwitchRightMenu enum_value
- Sandbox.GamepadCode.Touchpad enum_value
- Sandbox.GamepadCode.X enum_value
- Sandbox.GamepadCode.Y enum_value
Inherited members
Direct inherited members are not expanded here because the pinned record does not establish a complete inheritance closure.
Flow
The diagram separates the declared inputs, operation and result. Connections describe the recorded relationship; they do not establish execution order or lifecycle behaviour.
Open this operation in the flow explorer →
Examples
No reviewed code example or workflow covers this declaration. Use the exact declaration and inputs/outputs flow as the available local teaching surface, then run a bounded installed-build probe before relying on behaviour. Open the exact declaration flow.
Constraints and pitfalls
- Execution context: game-or-shared-unknown
- A public declaration is not proof of sandbox allowlisting.
- No compile/runtime verification was run.
Prerequisites and limits
- Resolve the type identity in the pinned release before relying on its declaration.
Still unknown
- Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.
- No indexed implementation-source chunk is linked to this declaration; the entry is declaration-only.
declaration-onlymetadata-only
Upstream documentation availability
Documentation text is not copied into this export because the release metadata redistribution licence is unresolved.
Evidence and verification
pinned metadata source correspondence unverified
- declaration: pinned-release-metadata
Installed-build compile/runtime state: not run.
Related workflows
None selected.
Related diagrams
None selected.