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

Game.HookDontUpdateLegacyInMouseMsg

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

Game.HookDontUpdateLegacyInMouseMsg: boolean

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

**Nucleus Co-op will hook mouse movement messages and the GetCursorPos function to work around legacy input. Some games only need the GetCursorPos hook and conflict when mouse movement messages are edited. If this is the case, enable this option*

Category: Support for multiple mice and keyboards

AI-writtenAI-written. Based on: Nucleus DllsInjector.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 input hooks, injected into each instance (DllsInjector.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.HookDontUpdateLegacyInMouseMsg = 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