PUDDING / FIELD MANUAL
Understand it.
Then take control.
18 standalone modules, from mechanisms to practical steps. Understand suppression, game priority and resource yielding before configuring your session.
HOW PUDDING WORKS
What yields, and how?
CPU, disk I/O, memory, GPU and timers — follow the scheduling flow of a session.
Getting started
How it works: making room for the game ↗
Background suppression is central to Pudding: eligible background work yields when the game needs resources. Follow a session to understand what each control changes, which processes it affects and how restoration works.
Steps · Settings · Recovery02 / Getting startedInstallation & your first game ↗
Start with Smart mode and complete one real game session. Confirm that protection activates and session changes restore before adjusting individual settings.
Steps · Settings · Recovery03 / Getting startedOverview & game protection ↗
Overview tells you which game is protected, which policy is active and what needs attention. Version 2.2.2.3 adds actionable notices and a diagnostic summary.
Steps · Settings · Recovery04 / Getting startedModes & power plans ↗
Modes set the scope of background suppression and additional policies. Start with Smart and use Esports, Handheld or Custom for a specific need.
Steps · Settings · Recovery05 / Getting startedGame 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.
Steps · Settings · RecoveryControls & modules
Per-game profiles ↗
Different games do not need the same policy. Override only the options you want to change and let everything else inherit global settings.
Steps · Settings · Recovery07 / Controls & modulesCore scheduling & exclusivity ↗
Core selection now has its own page. Start with all cores and restrict the game only after understanding CPU topology and workload.
Steps · Settings · Recovery08 / Controls & modulesPolicies & background suppression ↗
Policies cover game priority, background scope and session extras. The current source uses Core control, Preset details and Session extras; core selection has moved to its own page.
Steps · Settings · Recovery09 / Controls & modulesMemory, power & session extras ↗
Memory cleaning, cache warm-up and power-budget sharing solve different problems. Identify the bottleneck before enabling an option.
Steps · Settings · Recovery10 / Controls & modulesGraphics & driver policies ↗
Adjust only options supported by your GPU and driver. Common, NVIDIA, AMD and Intel groups expose different capabilities.
Steps · Settings · Recovery11 / Controls & modulesSystem environment & input ↗
These changes can persist, and some require a restart. Read each option and distinguish environment settings from temporary session policies.
Steps · Settings · Recovery12 / Controls & modulesWhitelist & peripheral protection ↗
Whitelist applications that must stay responsive while gaming. Choose whether the exemption covers one executable or its child processes as well.
Steps · Settings · Recovery13 / Controls & modulesAnti-cheat & compatibility ↗
General background suppression and anti-cheat-specific controls are separate. Anti-cheat is protected by default; optional controls do not control kernel drivers or guarantee compatibility.
Steps · Settings · Recovery14 / Controls & modulesDevice interrupts & verification ↗
Version 2.2.2.3 reorganizes interrupts into observation, device selection and evidence-based core configuration. Use multiple sessions of the same game and configuration.
Steps · Settings · RecoveryMaintenance & recovery
Audit, reports & logs ↗
Use evidence before changing settings. Session reports describe play, System audit checks the machine, and logs record actions and failures.
Steps · Settings · Recovery16 / Maintenance & recoverySettings, language & data ↗
Settings brings together appearance, language, startup, data and cleanup. Interface preferences and system-changing operations have different effects.
Steps · Settings · Recovery17 / Maintenance & recoveryLoL & WeGame extensions ↗
These game-specific extensions are separate from general scheduling. Login, extra processes, lobby UI and file deletion each have distinct behavior.
Steps · Settings · Recovery18 / Maintenance & recoveryRecovery, uninstall & troubleshooting ↗
Determine whether a change is session-based, persistent or a file operation before choosing a recovery action. Preserve recovery records rather than deleting the application first.
Steps · Settings · RecoveryContent reviewed against the 2.2.2.3 source, README and release notes. Follow current on-device notices when version, mode or hardware changes the interface.