FIELD MANUAL / 13
Anti-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.
- Where to find it
- Advanced → Anti-cheat
- When it applies / restoration
- The master switch controls optional attempts. Disabling it does not remove general exemptions.
Step by step
- Identify the game’s anti-cheat group and any Protect only label. Leave optional throttling disabled initially.
- Only experiment with supported user-mode groups for a specific need, considering that game threads may wait for scanning.
- The current source offers Gentle, Balanced and Isolated tiers. Older descriptions of a single fixed strength are outdated.
- Revert after a rejected write or game problem and inspect compatibility records and logs rather than forcing repeated writes.
Updated group behavior
The 2.2.2.0 release makes Vanguard Protect only and disables old enabled settings at startup. Protect-only groups such as Perfect World, 5E and B5 do not offer throttling controls. Follow the current group description.
How the three tiers differ
Gentle retains efficiency-core frequency limiting and disk-I/O demotion; Balanced adds scheduling-priority changes; Isolated adds lower I/O and affinity policies. Slower scanning can increase the time a game waits, so stronger is not necessarily faster.
Compatibility records and kernel boundaries
Compatibility records avoid repeating known rejected writes and may expire after a game update. User-mode switches neither bypass kernel anti-cheat protection nor modify game memory.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.