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

Game.LockInputAtStart

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

Game.LockInputAtStart: boolean

Once you have finished setting up the input options, enable this to automatically lock input (equivalent to pressing End) once all of the instances have been set up.
This is usually convenient to leave disabled whilst testing.

Default: false ยท Category: Support for multiple mice and keyboards

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (if gen.LockInputAtStart: Thread.Sleep(5000), LockInputRuntime.Lock); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

After the last instance is set up, Nucleus waits 5 seconds and locks the input by itself, as if the player pressed the lock key (End). Handlers usually leave it off, so players can arrange things first and lock when they're ready.

Is "In practice" right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).
Game.LockInputAtStart = true;
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