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

Game.ProtoInput.InjectStartup

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

Game.ProtoInput.InjectStartup: boolean
AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (StartGame launch branch, runtime inject condition); ProtoInputLauncher.cs (opens in a new tab) (InjectStartup, SetupInstance); ProtoInputLoader EasyHookStartup.cpp (opens in a new tab) (RtlCreateSuspendedProcess).

Nucleus starts each instance's game suspended, injects Proto Input, applies the Game.ProtoInput options and only then lets the game run, so the hooks are in place from its first line of code. This replaces Nucleus's other launch methods and the InjectRuntime_โ€ฆ options; it is not used with Game.ThirdPartyLaunch or Game.NeedsSteamEmulation. If injection fails, Nucleus shows an error and ends the session.

Category: Proto Input

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (if gen.ProtoInput.InjectStartup: ProtoInputLauncher.InjectStartup; the runtime branch needs !InjectStartup); Verified Hub handlers, counted 2026-11-17 (opens in a new tab); Hub game engines (opens in a new tab).

In practice

For games that need the hooks before their first frame (raw input registered at startup, a launcher that checks focus), mostly Unreal Engine games; few handlers need it. It wins over the InjectRuntime_โ€ฆ options: Nucleus doesn't inject again at runtime when it is true.

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