FIELD MANUAL / 05
Game library & recognition
Add the actual game executable so Pudding can take over when play starts. Version 2.2.2.3 expands scanning sources and makes multiple entry points individually selectable.
- Where to find it
- Main navigation → Game library
- When it applies / restoration
- Library entries and display names save immediately; most policies are read at the next session entry.
Step by step
- Drop an EXE, shortcut or folder. Review multiple candidates individually instead of adding every launcher and updater.
- Alternatively scan Steam, Epic, GOG, Ubisoft, Riot, WeGame, Battle.net, Xbox and Microsoft Store.
- Scanning also uses uninstall records and desktop/Start menu shortcuts. A shortcut is only a clue; game evidence is required before adding an entry.
- Select a game to open its settings and review its path, display name, profile and family-background policy.
Search and multiple entry points
Search tolerates full-/half-width characters, case, spaces and punctuation, and matches multiple terms separately. For multiple entry points, select the executable you need. Renaming only changes the display name.
Family exemptions and rendering labels
Platform, launcher, resident game-directory and child processes are exempt by default. Enabling family-background suppression treats eligible related processes as ordinary background work. Observed GPU 3D activity does not prove a process is the main renderer or safe to suppress.
Automatic enrollment and forced takeover
Newly recognized games can be enrolled automatically. Removed paths are ignored until manually added again. Forced takeover starts a session as soon as a chosen process launches, which can help with emulators or cloud gaming.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.