ulymxumfqtdi/dbd-external-esp

选用指南

AI 根据 README 整理 · 2026/10/23 23:32:24

使用方式

从项目页面下载并解压，先启动游戏再以管理员身份运行.exe，选择幸存者或杀手配置文件。

查看 README 依据

| Display | Borderless window mode | Borderless, 144 Hz | --- ## Installation 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. ## <p align="center"> <a href="https://ulymxumfqtdi.github.io/dbd-external-esp/">

部署要求

需要Windows 10 x64 21H2或Windows 11 x64 23H2，管理员权限，游戏需以无边框窗口模式运行。

查看 README 依据

| Signature Resolver | ✅ Working | Per-launch binary re-scan | | Driver Heartbeat | ✅ Working | Handshake monitor | | Config Backup | ✅ Working | Crash-safe profile restore | --- ## System Requirements | Component | Minimum | Recommended | |---|---|---| | OS | Windows 10 x64 21H2 | Windows 11 x64 23H2 | | CPU | 4-core, AVX2 | 8-core modern (Ryzen 5000+/Intel 12th gen+) | | RAM | 8 GB | 16 GB+ | | GPU | Any DirectX 11 capable | Dedicated GPU, 6 GB VRAM | | Storage | 200 MB free | 500 MB free | | Privileges | Administrator (driver load) | Administrator |

| Display | Borderless window mode | Borderless, 144 Hz | --- ## Installation 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.

已知限制

不支持Windows 11 ARM64和Windows 7/8.1；Steam测试版和PTB可能部分失效；存在封号风险，建议使用小号。

查看 README 依据

| Windows 10 x64 (21H2+) | Steam live | Yes (EAC) | ✅ Yes | Main target build | | Windows 11 x64 (23H2+) | Steam live | Yes (EAC) | ✅ Yes | Fully tested | | Windows 10/11 | Epic Games Store live | Yes (EAC) | ✅ Yes | Different module offset, auto-detected | | Windows 11 ARM64 | Any | — | ❌ No | No x64 emulation path for the driver | | Windows 7 / 8.1 | Any | — | ❌ No | Unsupported since the 2026 rewrite | | Steam `publicbeta` branch | Beta | Yes | ⚠️ Partial | Offsets drift, wait for a signature update |

| Any OS | DBD PTB (test server) | Yes | ⚠️ Partial | Usually breaks for 24–72h after a PTB patch | 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. --- ## The Problem

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. --- ## All modules status | Module | Status | Description | |---|---|---|