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

Game.ProtoInput.BlockedMessages

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

Game.ProtoInput.BlockedMessages: number[]

In the Block tab, you can select individual windows messages to block from the game. Usually a good one to block is WM_KILLFOCUS (0x0008). You can search for the hexadecimal code on MSDN, e.g. for WM_KILLFOCUS. Add the blocks to a handler like so:

Category: Proto Input

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

In practice

Window messages the game never sees (Proto Input's message filter hook drops them), so it only works with Game.ProtoInput.MessageFilterHook on; some handlers list messages without it. [0x0008] (WM_KILLFOCUS) keeps the game from noticing it lost focus, the usual list in Unreal Engine games; Unity games' handlers usually add WM_MOUSELEAVE and WM_MOUSEHOVER: [0x0008, 0x02a3, 0x02a1]. A number goes through Proto Input's own message table: one it doesn't list but within the table's range lands on another message's switch (and blocks that one), and one past its end does nothing, so add only listed messages.

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