Guardian's work is split into small, single-purpose "engines." Each one does exactly one job, and the main cycle runs them in order every 3 minutes. The Guardian page lists all 16 numbered engines on its status card; some run every cycle and the housekeeping ones run on slower schedules. Here's what each one actually does — in plain English.
The detection engines (always run)
- Emulator Detection — scans for the known Android emulators: GameLoop, BlueStacks, LDPlayer, Nox, MEmu and MuMu. This is the gatekeeper. If no emulator (and no native game) is found, the aggressive engines are skipped entirely.
- Memory Monitor — reads how much RAM is free and logs it. If you're not gaming and free RAM drops below roughly 10% of your total, it does a gentle working-set trim (throttled to once every 10 minutes). It will never do this mid-game.
- Game Detection — checks running processes against BRUTAL's built-in game profiles (both Android and native PC games). When it finds a match it can auto-apply that game's profile (Pro) with settings chosen for your hardware tier and GPU vendor. A native PC game launched while an emulator merely sits idle is correctly treated as a PC game — Guardian won't elevate or RAM-lock the idle emulator for it.
The aggressive engines (Pro, only while gaming)
These run only after a real game is confirmed. They target the game/emulator process, not your whole system.
- Priority Elevation — raises the game/emulator to High CPU priority (not Realtime — Realtime can starve the system). Reverted to Normal when gaming ends.
- Native runtime tuning (Pro) — handled by the NativeOptimizer. It activates a 0.5 ms system timer for tighter frame pacing, sets the game's I/O priority to High and memory priority to the maximum, disables Windows 11 EcoQoS power throttling so the game isn't downclocked or shoved onto efficiency cores, and locks a 512 MB minimum working set so the game's memory stays resident in RAM. The working-set lock only happens when there's at least double the RAM free, as a safety check.
- Process Watchdog — force-closes a curated list of background extras (Widgets, Phone Link, Cortana, the Edge updater, telemetry helpers, animated-wallpaper apps and known crypto miners). It deliberately never kills the Print Spooler, OneDrive or your chat apps — doing so would lose print jobs, sync progress or messages for almost no gaming benefit.
- Service Watchdog — temporarily stops the diagnostics and telemetry services (
DiagTrack, DiagSvc and DPS) for the session. The Print Spooler is excluded for the same reason as above. Crucially, every service it stops is restarted automatically when gaming ends.
Timer resolution is handled by the native tuning step above — there's no separate timer engine doing redundant work.
The App Priority Manager (Engine 12, Pro)
This is the engine that gives you back 2–4 GB of RAM during a session without breaking your chat. While gaming it:
- Uses a batched system query to identify Discord's processes, then demotes only the renderer/GPU child processes (the ones with
--type= in their command line) and trims their RAM — while protecting the main Discord voice process so calls stay clean. This applies to Discord, Discord Canary and Discord PTB.
- Demotes Steam WebHelper, Epic WebHelper, Spotify, Slack, Telegram and WhatsApp the same way — lowered priority, never closed.
When gaming ends, it restores every app it demoted back to Normal I/O and memory priority. These apps live between sessions, so leaving them throttled would be a bug — Guardian explicitly tracks and un-does it.
The slow-cadence housekeeping engines
These don't run every cycle — they're rate-limited so they stay out of your way:
- Driver Check — at most once per 24 hours, queries Windows Update for driver updates and counts how many (and how many are gaming-relevant). It only detects by default; optional Pro auto-update runs on a background task with a system-restore point and a 20-minute safety ceiling. If Windows Update can't be reached, Guardian doesn't falsely claim "0 updates" — it retries next cycle. See reading the log to spot these entries.
- Auto-Clean (free) — opt-in and off by default. When enabled, at most once per 24 hours while idle, it cleans only safe junk categories (never the Recycle Bin, never while gaming).
- Process Rules — applies your per-app priority/affinity/EcoQoS rules from the Process Rules page each cycle.
- Defender status (free) — a daily, read-only check of Microsoft Defender's posture. It only nudges (e.g. "definitions are old"); it never shows scareware or claims you're infected.
- Persistence baseline (Pro) — a daily, detect-only diff of startup/persistence entries. It records a known-good baseline and tells you about new items to review — it never auto-removes anything.
- App Updates and Junk Measure (free) — a rate-limited check for app updates and a once-a-day, read-only measure of reclaimable space, both skipped while you game. They feed the dashboard's Needs you card.
- Idle Service Restore (free) — restarts the Windows Update services an optimize run paused, once your PC is idle and you're not gaming.
- Unattended Updates — opt-in and off by default: installs app updates only when your PC is idle and no game has run recently, and tells you when it did.
Why "single responsibility" matters here
Each engine is wrapped so that if one fails, it logs a short note and the cycle carries on — one flaky check can never break the whole pass. That's why the log is full of short per-engine lines (e.g. ② Available RAM: 5120 MB). It's a deliberate, auditable design rather than one giant opaque "optimize" button.
FAQ
Why does Guardian set High priority instead of Realtime?
Realtime priority can starve essential system threads and cause stutter or hangs. High gives your game a strong, reliable scheduling advantage without that risk. Guardian sets High while gaming and reverts to Normal afterward.
Does Engine 12 mute my Discord calls?
No. Engine 12 only demotes Discord's renderer/GPU child processes (identified by --type= in their command line) and trims their memory. It specifically protects the main Discord voice process, so your call quality is unaffected. It restores everything when you stop gaming.
Why didn't Guardian kill the Print Spooler or clear my shader cache?
On purpose. Killing the Print Spooler would lose queued print/scan jobs for negligible FPS gain, and deleting the DirectX shader cache mid-game forces shaders to recompile, causing stutter. Guardian deliberately leaves both alone during a session.
How often does the driver and junk-clean work run?
Both are rate-limited to once per 24 hours. The driver check is detect-only by default (auto-install is optional Pro). Auto-Clean is off by default and, when on, only touches safe categories while idle. Neither runs while a game is active.