Nucleus handler tools โ€บ Docs โ€บ Game โ€บ LockInputToggleKey

Game.LockInputToggleKey

Open in the workbench (search, and try it in a handler)

Game.LockInputToggleKey: number

See https://docs.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes

Default: 0x23 ยท Category: Support for multiple mice and keyboards

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (gen.LockInputToggleKey = App_Hotkeys.LockKeyValue); App_Hotkeys.cs (opens in a new tab); RawInputProcessor.cs (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

Nucleus overwrites it when a session starts: GenericGameHandler sets it to the lock key the player chose in Nucleus' settings (End, 0x23, unless changed), and the raw input processor only listens for that key. So the value in the handler has no effect; handlers that set it nearly all say 0x23 anyway.

Is "In practice" right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).
Game.LockInputToggleKey = 0x23;
Is the doc right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).

Handler API docs

Stuck, or not sure? Ask other handler authors: Discordr/nucleuscoop