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

Game.ForwardRawKeyboardInput

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

Game.ForwardRawKeyboardInput: boolean

Deprecated: use Proto Input instead (see https://www.splitscreen.me/docs/proto).

The same as ForwardRawMouseInput, but for keyboards. Again, this should almost never be used instead of re-register raw input.

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

AI-writtenAI-written. Based on: Nucleus RawInputProcessor.cs (opens in a new tab); Proto Input guide protoinput.md (opens in a new tab) (Handler development with Nucleus Co-op); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

Read by Nucleus' own raw input forwarding (RawInputProcessor.cs), from before Proto Input. The Proto Input guide lists it among the options a Proto Input handler must set to false explicitly (some of them default to true), so Proto Input handlers set it false. No Hub handler sets it true.

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