ulymxumfqtdi/dbd-external-esp

Before you touch anything, check this matrix. This is the single most common question I get from people who pulled the repo before reading and then opened an issue because their build was from Steam's beta channel and the overlay never drew.

If your row says ❌, stop here. Everything below assumes a live Steam or EGS install on Windows 10/11 x64 with the anti-cheat handshake completing normally at game launch.

I took this project over in late 2025 because the previous maintainer vanished and the repo sat for eight months with a broken overlay and an offset list from a build that no longer existed. Here's what actually goes wrong when you try to use a Dead by Daylight external cheat in the wild — the stuff you only find out after a few hundred hours:

• Every DBD patch nukes your offsets. Behaviour Interactive ships balance patches and hotfixes constantly. A single Unreal Engine object layout change and your ESP renders the wrong thing or draws nothing at all — usually with no error, just silence.
• The old project hardcoded a signature scan window. Fine on Steam, dead on Epic, and it silently failed on the publicbeta branch. You'd think the cheat was broken when it was just looking in the wrong memory region.
• External overlays fight with EAC's process enumeration. Naive ReadProcessMemory loops get the handle yanked mid-match, and you get a friendly "connection lost" that isn't the game's fault.
• Killer vs. Survivor ESP needs different data. Survivor players want to see the killer's aura and totem positions; killer players want survivor silhouettes, pallet states, and generator progress. One-size-fits-all ESP is useless.
• Aimbot on a 3rd-person camera is not the same as FPS aimbot. The camera pivot, aim assist curves, and hit registration on DBD's melee/hatchet weapons behave completely differently, and generic FPS aim math makes your crosshair slide past the target.
• Detection is not just "don't rage." External reads, overlay window class names, and driver signatures all get fingerprinted. If you don't think about stealth at the process and driver level, you get flagged on a Tuesday.
• Nobody documents the recovery path. When the .exe crashes mid-match, people panic-reinstall the game. There's a clean way back.

Grab the current build from the project page, extract, run.

These numbers come from a clean test bench — single DBD instance, killer present, 5-minute Survivor match, ESP fully enabled with all aura modules, no aimbot. Framerate is what DBD itself reports; read latency is the round-trip from the external process reading game memory to the overlay frame.

If you're below 96 fps on the full load, it's almost always the aura refresh rate set too high in the config — drop esp.refresh_hz to 30 and you'll claw back the frames.

Under the hood, this is an external cheat in the strict sense: the .exe never injects a DLL into the game process. A signed user-mode loader opens a read-only handle to DeadByDaylight-Win64-Shipping via a minimal kernel driver that I rewrote in 2026 to stop the handle-revocation dance EAC does on process enumeration. The driver exposes only what the external process asks for — a bounded region of the game's UObject and UWorld graph — and the external side walks that graph every frame to resolve entity transforms, actor class pointers, pallet and totem states, and generator progression. The overlay itself is a separate layered window owned by the external process, never by the game, so it can't be enumerated as part of the game's own window tree. Aimbot runs entirely on the external side: it reads the current camera transform, projects candidate hit-spheres to screen space, runs a small predictive filter on target velocity, and emits relative mouse deltas — it does not touch the game's input pipeline, which is what keeps it outside most of the input-integrity checks that catch injected aim modules. The signature resolver re-scans the shipped binary on every launch and caches results in a local hash file; if a scan fails, the loader refuses to enable the affected module rather than running on stale offsets, which is the single biggest cause of silent ESP breakage in the old build. Everything is config-file driven, nothing phones home, and the whole thing is designed to be boring — no injected code, no patched bytes, no funny business with the game's own heap.

Fair framing: what do the common alternatives actually give you, and where does this one land?

18 modules, grouped by what they actually do in a match — not alphabetically, not "general tools." Each category is a place where you play.

• Survivor Aura ESP — reveals survivor silhouettes through walls and terrain, distance-tinted so far targets fade.
• Killer Aura ESP — always-on killer outline with nameplate and held-item icon.
• Totem Tracker — hex totem positions, lit/unlit state, and a subtle pulse when a dull totem has been blessed.
• Generator Aura — all five generators with live progress ring and regression flag.
• Hatch Aura — hatch position the moment it spawns, plus a bearing arrow when you're in chase.

• Hit-Sphere Aimbot — projects melee and hatchet hit-spheres to screen space, snaps with a configurable curve.
• Predictive Lead — velocity-compensated aim for hatchets and ranged killer powers.
• Smooth Assist — non-snappy aim-assist that nudges crosshair toward the nearest valid target, tunable strength.
• Hit-Registration Check — highlights whether the current aim line actually intersects a target capsule before you swing.

• Pallet Aura — pallet positions with standing/dropped/broken state.
• Vault Point Markers — window vaults and their safe/unsafe status from your current position.
• Loop Helper — draws the chase loop route with pallet and window nodes so you can read the tile at a glance.

• Survivor Silhouettes — through-wall silhouettes for all survivors, color-coded by injured / healthy / downed.
• Scratch Mark Highlighter — recent scratch marks emphasized so you don't lose a trail in tall grass.
• Status Feed — a small corner readout of survivor states (healing, unhooking, repairing) as they change.

• Generator Progress Overlay — per-generator progress bar in-world, with a small "pop" warning.
• Chest & Item Tracker — closed chest positions and the item inside once opened.
• Exit Gate Aura — gate positions and open-state indicator.

• Signature Resolver — re-scans the shipped binary each launch, refuses stale offsets.
• Driver Heartbeat — monitors the kernel driver handshake and auto-reloads on drop.
• Config Backup — snapshots your config on clean exit and restores after a crash.

• Set esp.refresh_hz to 30 for aura modules and 120 only for aimbot input — most people run everything at 144 and wonder why their fps tanked.
• Run the .exe as administrator; the driver handshake fails silently without elevation on some Win11 builds.
• If your ESP draws the wrong silhouettes after a patch, don't tweak the config — check for a signature update first. The loader will refuse to enable stale modules and log it.
• Keep the config backup on by default. If the game crashes mid-match, restart the .exe and it restores your profile instead of you rebuilding it from memory.
• For survivor ESP, use the shipped survivor profile; for killer, use the killer profile. Mixing them wastes reads and slows the overlay.
• Don't alt-tab out of a fullscreen match while aimbot is enabled — the input delta tracking assumes the game window has focus.
• If the overlay is invisible but the process is running, check that DBD is in Borderless, not exclusive Fullscreen. The layered window can't draw over exclusive-fullscreen.
• On a laptop, force the .exe to use the dedicated GPU in Windows graphics settings — integrated-only benches are in the table above and they're not pretty.

1. Overlay doesn't appear at all → is DBD Borderless? Is the .exe elevated? Does the log show a signature scan failure?
2. Overlay appears but draws nothing → signature resolver is refusing modules; check the log for the failed scan and update.
3. ESP draws stale/off positions → offsets are from a previous patch; do not trust the config, update.
4. Aimbot feels sluggish → lower aimbot.tick_ms, and check you're not on the integrated GPU.
5. Process is killed mid-match → driver heartbeat dropped; restart .exe and check elevation.

There is no such thing as an "undetectable" external cheat and I'm not going to pretend otherwise. What this project does offer is a window of validity: signed loader, external-only reads, no injected code, and a signature resolver that refuses to run on stale offsets. That combination is why the 2026 rewrite has held up through the last several patches where the old build would have flagged instantly. That's still not a guarantee — EAC updates, and the project updates in response. Use it on an account you're willing to lose, and treat every patch day as a reason to wait before launching.

Yes — the loader auto-detects which distribution you're running by hashing the shipped binary and matching against known-stable signature sets for both Steam and EGS. The only wrinkle is that EGS pushes the anti-cheat handshake slightly later than Steam, so the loader waits for the handshake before enabling modules. If your ESP is blank for the first ~10 seconds on EGS, that's expected, not a bug.

It can. Any external cheat can. The design minimizes the surface — no injection, no patched bytes, signed loader, external overlay — but EAC is a moving target and Behaviour Interactive does ban waves. The honest answer is: use an alt, expect to lose it eventually, and don't run this on an account you care about. What the project promises is not immunity; it's a clean external architecture and fast turnaround when a detection-relevant update lands.

1. Download and extract. Grab the archive from the project page and extract it to a folder you control — not Program Files, not a synced OneDrive folder. Windows Defender will likely flag the .exe; that's expected for a cheat loader, and you'll need to add an exclusion.
2. Launch DBD first, then the .exe. The loader waits for the game process and the anti-cheat handshake before doing anything. If you start the .exe first, it'll sit idle until DBD appears.
3. Run the .exe as administrator. Right-click → Run as administrator. The signed driver load fails silently without elevation on some Win11 configurations, so this isn't optional.
4. Pick your profile. Survivor or killer — the shipped configs are tuned for each. You can edit config.ini on the side, but start from the shipped profile before you tune.
5. Play. Overlay appears on top of the game in Borderless mode. If it doesn't, go back to the troubleshooting flow above.

Extract, elevate, run. That's the whole install.

I picked this project up off the floor and rebuilt it because the original was genuinely useful to people who understood the tradeoffs, and then it stopped working and nobody explained why. The 2026 rewrite is external-only, signed, and loud about failure instead of silent. Read the compatibility matrix, run it as admin, use an alt, and treat patch day as a reason to wait. If something breaks, the log tells you what — that's the whole point of the rewrite.