What Is the Order of Operations to Use Cheats Safely?
The safe order is: cold boot Windows, run Raw Spoofer as administrator to randomize 16 hardware identifiers, launch the Raw loader and enter your cheat license, open the game via Steam, Epic, Battle.net, or NetEase, wait at the main menu for the anti-cheat to initialize, click Inject in the loader, then press INSERT to open the menu. Skipping the spoofer step or launching the game before the loader breaks the chain.
Order matters more than any individual setting. Anti-cheats cache hardware identifiers and process tree state at launch. Running steps out of sequence — opening Steam before spoofing, injecting before the anti-cheat finishes initializing, skipping cold boot — produces telemetry patterns that get accounts flagged even when every other element is clean.
Why cold boot before anything else
A cold boot (full power-off, then power-on) clears the Windows Fast Startup cache that hibernates kernel state between restarts. Without this, BattlEye and Easy Anti-Cheat telemetry from your previous session can survive into the new one — particularly the cached SMBIOS reads that get pinned on first launch of steamservice.exe or the Epic Launcher. Restart from the Start menu does not equal cold boot on Windows 10/11.
Spoofer before game launcher
Run Raw Spoofer as administrator before opening Steam, Epic, Battle.net, NetEase, or the Riot client. The spoofer randomizes 16 identifiers including SMBIOS UUID, motherboard serial, disk serials, MAC addresses, GPU UUID, MachineGuid, RAM SPD, and monitor EDID. If the game launcher opens first, it pins the pre-spoof identifiers — running the spoofer afterward leaves an obvious mismatch that some kernel anti-cheats now log.
Loader before game
Open the Raw loader, enter your cheat license, select the target game. The loader auto-checks the forum status board and refuses to inject if the build is paused for a signature update. Doing this before launching the game gives you a clean abort if status is red — you save a session of risk by closing the loader and walking away.
Game launches via legitimate launcher
Start the game through Steam, Epic, Battle.net, or whatever publisher launcher it normally uses. Don't use third-party launchers, modded loaders, or shortcuts that bypass the anti-cheat's normal init path — kernel anti-cheats notice unusual launch patterns. Wait at the main menu for 10-15 seconds so the anti-cheat fully initializes before you inject.
Inject at the main menu, not mid-match
The Raw loader's Inject button attaches the external overlay outside the game process. Inject at the main menu — never mid-match. Mid-match injection produces a sudden draw layer change that some replay reviewers and behavioral systems flag. The 2-3 second window between Inject and menu-open is fast enough at the menu, suspicious mid-game.
Configure once, save to a slot
Open the menu with INSERT, set aimbot, ESP, and humanizer once, save to a config slot. Reloading a saved config on subsequent sessions is faster and more consistent than reconfiguring every session — and consistency keeps your stats line believable to behavioral anti-cheat like Anybrain and Activision Ricochet.
What breaks the chain
Common mistakes: opening Steam before spoofing, running the spoofer without admin (partial spoof), injecting while still in lobby loading screen, switching games without re-spoofing, party-ing with a legit friend while running the cheat (account-link bans from Overwatch's February 2023 update still apply), running a free cheat on the same machine.
For per-session checklists see the setup-safely cluster. For HWID-side coverage see the HWID spoofer pillar and the Raw Spoofer product.
Related Pages
Sources
- About Easy Anti-Cheat — Epic Games
- BattlEye Support FAQ — BattlEye Innovations
- Defense Matrix: Peripheral Vision — Blizzard
- RICOCHET Anti-Cheat — Activision
Related Questions
Launch your game first and wait at the main menu, then open the Raw loader, select the matching game from the dropdown, and click Inject. The cheat attaches as an external overlay outside the protected game process, so Easy Anti-Cheat and BattlEye see no DLL load events or memory writes inside the game. The menu opens within 2-3 seconds. Default keybind is INSERT. No manual offsets, no Cheat Engine, no DLL handling required.
Cold boot Windows before launching anything, right-click the Raw Spoofer binary and select Run as administrator, paste your spoofer license into the activation field, and click Spoof. The tool randomizes 16 hardware identifiers including SMBIOS UUID, motherboard serial, disk serials, MAC addresses, GPU UUID, MachineGuid, RAM SPD, and monitor EDID in about 4 seconds. Reboot is not required. Launch your cheat loader and game afterward.
Buy the Raw cheat for your game plus the Raw Spoofer add-on, cold boot Windows, run Raw Spoofer as administrator and enter your spoofer license to randomize 16 hardware identifiers, launch the Raw loader and enter the cheat license, select your game from the dropdown, then start the game via Steam, Epic, or Battle.net. Click Inject in the loader at the main menu and press INSERT in-game to open the overlay.
First-time setup takes 5-10 minutes — cold boot (about 60s), run Raw Spoofer as admin (4s spoof time + license activation), launch the Raw loader and enter cheat license (about 30s), launch the game and wait for anti-cheat init (about 15s), click Inject (2-3s overlay attach), and configure aimbot/ESP settings (3-5 minutes if tuning carefully). Subsequent sessions take under 2 minutes once your config slot is saved.
Yes, every session if you have ever been hardware-flagged, and as cheap insurance even if you haven''t. Cold boot Windows, run Raw Spoofer as administrator before opening Steam, Epic, Battle.net, or NetEase. The spoof persists until reboot. Skipping the spoofer means one signature detection bans your hardware permanently across every account on that machine. The 4-second spoof time per session is the cheapest insurance in the cheat workflow.
