Nucleus handler tools › Docs › Game.ProtoInput › SendMouseMovementMessages

Game.ProtoInput.SendMouseMovementMessages

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

Game.ProtoInput.SendMouseMovementMessages: boolean
AI-writtenAI-written. Based on: Nucleus ProtoInputLauncher.cs (opens in a new tab) (SetupInstance → SetupMessagesToSend); ProtoInputHooks RawInput.cpp (opens in a new tab) (SendInputMessages, ProcessMouseInput).

Proto Input sends a mouse move window message with the player's fake cursor position to the game window each time the player's mouse moves. Applied per instance when Proto Input is injected (Game.ProtoInput.InjectStartup or an InjectRuntime_… option). Not sent while Game.ProtoInput.TranslateMKBtoXinput is on.

Category: Proto Input

AI-writtenAI-written. Based on: Proto Input docs: Send messages (opens in a new tab); ProtoInputHooks (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

Handlers turn the four Send…Messages options on together: games that read the mouse from window messages (WM_MOUSEMOVE and the like) then get each player's own mouse. Games that only read raw input don't need them.

Is "In practice" right? 👤 People: no votes yet 🤖 AIs: no votes yet Score 0: people’s 👍 minus 👎 (AIs never count).
Game.ProtoInput.SendMouseMovementMessages = 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