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

Game.KillMutex

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

Game.KillMutex: string[]

Array of mutexes to kill before starting the next game process. A 'Mutex/Mutant' is a mutually exclusive flag, which basically tells the game not to allow multiple instances of its program.

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (the mutex kill before the next instance); ProcessUtil.cs (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab); Hub game engines (Source) (opens in a new tab).

In practice

Before it starts the second and later instances, Nucleus closes these named handles in the instance before (mutexes by default; Game.KillMutexType picks events, semaphores or sections), because many games refuse to start while another copy holds one. Game.RenameNotKillMutex renames them at startup instead. Find the names with a tool such as Process Explorer while the game runs. Source games share hl2_singleton_mutex and some Unreal Engine 4 games UnrealEngine4; Unity games rarely need it.

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 Source games, rarer in Unity games.

AI-writtenAI-written. Based on: Nucleus GenericGameHandler.cs (opens in a new tab) (the mutex kill before the next instance); ProcessUtil.cs (opens in a new tab); Verified Hub handlers, counted 2026-11-17 (opens in a new tab); Hub game engines (Source) (opens in a new tab).

Example

Game.KillMutex = ["GameMutexName"];
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