Tarkov is uniquely brutal — losing gear on death makes ESP almost more valuable than the aimbot. Here's how to set up both safely.
BattlEye in Tarkov
BattlEye scans process memory and loaded modules. It's more reactive than proactive — it bans in waves after signature updates rather than instantly. External cheats that don't write to game memory are invisible to BattlEye's primary scan. The Tarkov build here hasn't triggered a ban wave in 4+ months.
Loot ESP Priority
Use filters aggressively — showing all loot creates visual noise and slows you down:
- Tier 1: Keycards, GPU, LEDx, Defib, Graphics card
- Tier 2: Suppressors, helmets above UNTAR
- Tier 3: Ammo caches, med cases
- Skip: Food, low-tier ammo, white weapons
Player ESP
Show PMC vs Scav separately. Prioritise PMC ESP — Scavs are low threat. Add distance filter (only show PMCs within 200m) to reduce cognitive load in dense maps like Reserve or Labs.
Aimbot — Scav vs PMC Runs
For Scav runs: rage settings are fine (the account isn't your main PMC). For PMC: legit settings only. Your PMC has insurance items and progression — one report to BSG = permanent ban with no appeal.
Offline Practice Mode
Use offline mode to calibrate aimbot settings. The offline client is the same binary — your settings carry over to online, and you can test without risk.
Free Tarkov cheat — check status before raid →
Verifying Overlay and ESP Functionality
Before entering a live raid, confirm the cheat has attached to the correct process and that the overlay is rendering. A common failure case is the overlay not appearing in fullscreen exclusive mode; switching Tarkov to borderless windowed in the graphics settings resolves this, though it introduces a small input latency trade-off. Verify ESP by loading into an offline raid on Factory and checking that the extract point markers and player silhouettes appear with correct distance readouts. If nothing renders, the cheat likely failed to bypass BattlEye's module enumeration—check the loader logs for a 'scan bypass' error. Version 0.13.5 of the cheat introduced a separate overlay process that must be launched after the game client, not before. A successful attach shows a green status indicator in the loader and a brief confirmation chime. Do not proceed to online play if the ESP fails to show scavs in offline mode; this indicates a signature mismatch.
Aimbot Bone Targeting and Smoothing Values
Headshot-only aimbots are detectable through statistical analysis of hit distribution. A 100% headshot rate over 50 raids is flagged by BattlEye's heuristic layer, which compares your accuracy against the player base. Set bone priority to 'head, neck, chest' with a 60/30/10 weighting and smoothing between 2.5 and 3.5 degrees per tick. For PMC runs, use a maximum FOV of 15 degrees to avoid snapping to targets outside your natural crosshair placement. The 2026 build added a 'humanised' mode that introduces randomised micro-delays between 80 and 140 milliseconds before locking on. Test this offline against scavs on Customs: aim at a wall, then strafe to acquire a target. The lock should take roughly the same time as a skilled human reaction (200–250ms). Values below 50ms are statistically impossible and will be caught in the next ban wave.
Post-Raid Signature Checks and Log Cleaning
BattlEye's reactive scans occur during the post-raid 'debriefing' period, not just at launch. After each raid, the client reads the game's memory for known cheat signatures and checks for anomalous module loads. A common mistake is leaving the cheat loader running after closing Tarkov; this keeps the injected DLL in memory and triggers a signature match on the next scan. The 2026 version of the cheat includes an auto-unload feature that must be enabled manually in the settings—verify it is active by checking that the loader process terminates within 5 seconds of the game closing. Additionally, clear the Windows prefetch and recent items list after each session using a tool like CCleaner, as BattlEye logs file access times. Failure to do so has resulted in manual reviews for users with otherwise clean histories. A successful clean exit shows no 'suspicious process' warnings in the Windows Event Viewer under Application logs.