Input Actions

Loads and manages input action definitions from JSON files. Actions define what happens when an input binding triggers (key press, axis movement, etc.), including the command context (vehicle Lua, GE Lua, etc.) and action map assignment.

Public API

Action Definition Format (JSON)

{
  "steering": {
    "cat": "vehicle",
    "ctx": "vlua",
    "onChange": "input.event('steering', VALUE, FILTERTYPE, ANGLE, LOCKTYPE)",
    "isCentered": true,
    "desc": "ui.controls.steering"
  }
}

Command Contexts

Action Maps

Hooks

Module State

Usage Example

-- Get all active actions
local actions = core_input_actions.getActiveActions()

-- Check if an action exists
local action = core_input_actions.upgradeAction("steering")

-- Programmatically trigger an action
core_input_actions.triggerDownUp("reset_physics")

-- Execute an action command manually
local evt = { ctx = "vlua", onDown = "input.event('horn', 1)" }
core_input_actions.executeCommand(evt, 1, vehicleId)

Key Internals

• Vehicle-specific actions are read from vehicles/{name}/input_actions*.json and jbeam inputActions.
• Actions are name-mangled with vehicle name prefix for uniqueness.
• actionsEnabled from jbeam determines which vehicle actions are usable vs vehicle_specific_unusable.
• The menuIndependentPrefix is "MenuIndependent_".

See Also

• Input Action Filter - Related reference
• Input Bindings - Related reference
• Input Categories - Related reference
• Core Systems Guide - Guide