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

Game.Hook.SDL2Enabled

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

Game.Hook.SDL2Enabled: boolean

If the game supports sdl2 joysticks(not a hook)

AI-writtenAI-written. Based on: Nucleus Tools/SDL2Dll/SDL2Dll.cs (opens in a new tab) (SetupSDL2Dll); GenericGameHandler.cs (opens in a new tab) (gen.Hook.SDL2Enabled); Controls/SetupScreen/DevicesFunctions.cs (opens in a new tab) (SDL2 devices); Verified Hub handlers, counted 2026-11-18 (opens in a new tab).

In practice

Not a hook: Nucleus lists SDL2 controllers for the game and, for each instance, copies its own SDL2.dll (utils\SDL2\<arch>) next to the game's .exe, or into each folder in Game.SDLPaths, and writes SDL2.ini with that player's controller number. So it only works for games that load SDL2.dll as a separate file; a game with SDL built into its .exe (or a differently named SDL DLL such as SDL264.dll) keeps its own SDL and ignores it. Rare in Hub handlers; some also set Game.SDLPaths.

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

Example: From Hub handlers

Game.Hook.SDL2Enabled = true;
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