urdtbittefnu / deadlock-external
git clone https://github.com/urdtbittefnu/deadlock-external.git
Deadlock external cheat: ESP wallhack, aimbot, skeleton overlay, radar β educational reverse-engineering reference, injector included.
+64
stars, 24h Β· #615
+64
stars, 7 days Β· #3,213
+64
stars, 30 days Β· #10,213
64
β
total Β· +64% this week
32
forks Β· 0 open issues
Star history starts 2026-10-23; the chart appears after the second daily snapshot.
LanguagePython
LicenseMIT
Created2026-10-22 (today)
Last pushtoday
Watchers28
OwnerOrganization
GitHub topics
deadlock-educationaldeadlock-external-espdeadlock-memory-readerdeadlock-moddingdeadlock-offsetsdeadlock-overlaydeadlock-sdkexternal-espexternal-esp-overlaygame-memory-readergame-overlay-imguimemory-readersource2-externaltrigger-botvalve-anti-tampervalve-source-engineworld-to-screen
Links
README excerpt
--- **Deadlock External Cheats** is an external, user-mode overlay that reads Deadlock's process from the outside β no DLL injection into the game image, no kernel driver, no rebooting into a test-signing mode. It is built as a learning artifact: a complete, readable external-cheat toolkit that veterans of D3D/Kez-style cheat dev will recognize, and newcomers can study. If you've ever stared at a paid sell-site for Deadlock cheats with a $30/month rental and an opaque updater that phones home, this repo is the opposite. It is one portable folder, one `.exe`, an INI config that is yours to read, and code logic that gets explained β not vendored into a 400 KB obfuscated blob. It replaces things like **buying subscription-based Deadlock cheats (renders / read-only overlays) that die on every Hero/weapon update** and **grey-market internal DLL exploits you have to flash via an anonymous loader**. This is something you own, inspect, and rebuild. > Disclaimer: for educational and research purposes only. You are responsible for complying with Valve's terms of service in your region. Do not use cheats to ruin other players' matches. --- ## π Table of Contents - Overview - The Problem - The Solution - Quick Start - Key Features - Is It Safe? β Detection Model & Limits - Does It Work on Steam? β Platform Notes - Will It Get Me Banned? β Read First - Module Matrix β 23 Modules Field-Tested - How It Actually Works (Internals narrative) - Comparison - System Requirements - Installation - Usage Guidelines β Allowed / Not Allowed - Tips for Best Results - Known Issues - FAQ - AI Integration in 2026 --- ## π§ Overview | Category | Details | |---|---| | Product type | External overlay cheat (user-mode, no injection) | | Target title | Deadlock (Valve) β Desktop, Windows | | Interface | DirectX 11 transparent window + ImGui menu | | Injection method | None β RPM/WPM through Handle access | | Config format | Plain INI (`deadlock.ini`), human-readable | | Distribution | Portable folder β extract β run `.exe` | | Update strategy | Sig-scan offsets auto-refresh (no reinstall, no patch hunting) | Deadlock is an unusual target: it's a MOBA-shooter running on Source 2, the game pushes frequent content patches (new heroes, weapon tuning), and its anti-cheat lives in a mix of detection gates that pre-date most public tools. That makes offsets shift more often than people expect β and that is why this tool leans on a runtime signature scanner instead of redump-on-every-patch internals. --- ## π©Ή The Problem - **Every subscription cheat dies on Tuesday's patch.** A Hero update lands, thumbcache shifts, and your $30/month cheat shows "OutDated β warte auf Update" for 48 hours. - **Internal DLL cheats get you caught by the import/handle scan.** Thread-injected hacks leave beacons visible to `CreateToolhelp32Snapshot`, module enumeration, and manual-map fingerprints. - **"Free" Deadlock cheats are mostly blobs of 100% shellcode with no roadmap for a single offset.** You're runnin