Nucleus handler tools โ€บ Docs โ€บ Context โ€บ StartArguments

Context.StartArguments

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

Context.StartArguments: string

Set launch(start) arguments for the exe from within the Game.Play() function

Copied from Game.StartArguments for the current instance.

Category: Path variables

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (startArgs read after Game.Play); Verified Hub handlers, counted 2026-11-17 (opens in a new tab); Hub game engines (opens in a new tab).

In practice

The command line the instance's game starts with. Set it in Game.Play: Nucleus reads it after Game.Play returns (it has no effect with Game.GamePlayAfterLaunch). Typically a windowed mode switch plus the instance's resolution, for games that take them on the command line (common in Unreal Engine and Unity games).

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