Nucleus handler tools โ€บ Docs โ€บ Game.ProtoInput โ€บ MessageFilterHook

Game.ProtoInput.MessageFilterHook

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

Game.ProtoInput.MessageFilterHook: boolean

Hooks the GetMessage and PeekMessage functions to intercept every windows message for every window owned by the process. (Note this method is superior to changing WndProc since it works for all windows without knowing what they are, and is less fragile). This hook is used to make the message filters and blocks work. This should always be enabled.

Category: Proto Input

AI-writtenAI-written. Based on: ProtoInputHooks MessageFilterHook.cpp (opens in a new tab); Nucleus ProtoInputLauncher.cs (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

The filters (RawInputFilter, MouseButtonFilter, ...) and Game.ProtoInput.BlockedMessages only act inside this hook, so they do nothing while it is off. Most Proto Input handlers turn it on, and many then enable the filters only while input is locked, from Game.ProtoInput.OnInputLocked with ProtoInput.EnableMessageFilter.

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