FIELD MANUAL / 12
Whitelist & peripheral protection
Whitelist applications that must stay responsive while gaming. Choose whether the exemption covers one executable or its child processes as well.
- Where to find it
- Main navigation → Whitelist
- When it applies / restoration
- Whitelist entries exempt background suppression; protection boundaries remain across modes.
Step by step
- Drop an EXE or shortcut, pick a running application or browse to its path.
- Review the scope. Ordinary applications include children by default; command-line and script hosts protect only themselves by default.
- Use the context menu to select process-only or process-and-children protection. Keep the scope relevant.
- Start another session and check voice chat, recording, controller mapping or platform chat alongside the suppression log.
What is already protected
Driver containers, power/fan tools, input/audio paths and essential system components have built-in protection. Expand the current exemption list rather than manually duplicating every entry.
Game families and whitelists are different
Game-family exemptions follow the active game’s platform, directory and descendants. Whitelists express explicit application exemptions. For broken overlays, first check whether family-background suppression is enabled for that game.
Correcting entries
Whitelist real dependencies instead of all applications. Essential built-in entries cannot be removed. Restore the defaults if manual entries become confusing, then add back the applications you need.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.