Nucleus handler tools โ€บ Docs โ€บ Game.Hook โ€บ ForceFocusWindowName

Game.Hook.ForceFocusWindowName

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

Game.Hook.ForceFocusWindowName: string

If force focus is enabled, this is the window we are attaching ourselves to and the window we are going to keep on top. Needs the exact name of the window. If force focus is disabled you still need to set the game window name for resizing and positioning.

Default: ""

AI-writtenAI-written. Based on: Nucleus GlobalWindowMethods.cs (opens in a new tab) (UpdateAndRefreshGameWindows); GenericGameHandler.cs (opens in a new tab) (process.MainWindowTitle == gen.Hook.ForceFocusWindowName); XInputPlusDll.cs (opens in a new tab) (CustomDllEnabled: ForceFocusWindowRegex); Verified Hub handlers, counted 2026-11-17 (opens in a new tab).

In practice

Even without the custom XInput DLL, Nucleus uses it to recognise each instance's game window: the window must have this title (within 2 letters, unless Game.HasDynamicWindowTitle), and processes are matched on their main window title. Put the exact title the game window shows; practically every handler sets it.

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