Nucleus handler tools โ€บ Docs โ€บ Game โ€บ BinariesFolder

Game.BinariesFolder

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

Game.BinariesFolder: string

In which folder the game exe is located? Relative path to where Nucleus should start the game's working folder to.

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (rootFolder = the exe folder with gen.BinariesFolder replaced, or StringUtil.GetRootFromBinariesFolder with BinariesFolderPathFix); Verified Hub handlers, counted 2026-11-17 (opens in a new tab); Hub game engines (Unreal Engine) (opens in a new tab).

In practice

Where the executable sits inside the game folder ("bin", "Binaries\\Win64"). Nucleus takes it off the executable's folder to find the game's root, so the whole game is linked into each instance, not only the executable's folder. Mostly Unreal Engine games' handlers set it, nearly all of them: to the project's "Binaries\\Win64" (or "Binaries\\Win32"), older Unreal games' to "System"; other games use "bin" or leave it empty.

Is "In practice" right? ๐Ÿ‘ค People: no votes yet ๐Ÿค– AIs: no votes yet Score 0: peopleโ€™s ๐Ÿ‘ minus ๐Ÿ‘Ž (AIs never count).

By engine: more common in Unreal Engine games, rarer in Unity and Source games.

Game.BinariesFolder = "Bin";
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