How pszachary/lockdown-protocol-external works
Project type and purpose
• This is a native C++ “external” game-enhancement tool (an “external cheat/overlay”) that hooks into a running game process to read/write memory, applies various player/weapon/inventory hacks, and renders a real-time overlay (ESP, radar, menu) using DirectX11 + Dear ImGui.
• The README confirms it’s meant to be built locally and injected or run alongside the target game (Lockdown Protocol) to enable features like ESP, aimbot, infinite ammo, etc.
File structure
• Top-level:
• main.cpp – entry point, game loop setup
• config/ + config/config.json – JSON-based settings file
• ItemProperties.h, game_*.hpp, game_*.h – data structures and game-specific offsets/types
• util.hpp, mem.hpp, common.hpp – utilities for string ops, memory scanning/reading/writing
• nlohmann/ – JSON parsing library
• overlay/ – overlay rendering code with subdirs:
– dx11/ – DirectX11 hook and overlay implementation (moverlay.cpp/.h)
– imgui/ – Dear ImGui source and platform/renderer backends
• fonts/ – custom font resources for overlay
• radar.cpp/h, menu.cpp/h – feature-specific modules
• Visual Studio solution: protocol.sln, protocol.vcxproj*
README for additional insights
• Features section lists ~25 hack categories, each implemented as a module that reads/writes game memory.
• Default hotkeys, usage instructions, and code example are provided.
a. Main components:
1. Game Process Interface
– MemoryManager (mem.hpp)
– DataCache (data_cache.h)
– Game Data Models (game_structures.hpp, ItemProperties.h)
2. Feature Modules
– ESP Renderer (overlay/imgui + overlay/dx11)
– Radar Module (radar.cpp/h)
– Player Hacks (speed, god mode, stamina, etc.)
– Weapon Hacks (rapid fire, no recoil, etc.)
– Inventory Hacks
– Aimbot Module
3. UI Layer
– ImGui Menu (menu.cpp/h)
4. Configuration
– ConfigManager (nlohmann/json.hpp + config/config.json)
5. Input Handling
– Keybinds (keybinds.hpp + menu/input integration)
6. External Dependencies
– DirectX11 (overlay/dx11)
– Dear ImGui (overlay/imgui)
– nlohmann JSON
b. Relationships & interactions:
• On each frame tick in main.cpp, InputHandler reads hotkeys → toggles feature flags in FeatureManager.
• FeatureManager uses MemoryManager to read game state into GameData models.
• Depending on toggles, Feature modules read/write memory via MemoryManager.
• OverlayRenderer (DX11 hook + ImGui) draws ESP, radar, and menu, consuming GameData.
• ConfigManager loads/saves feature toggles and user settings from/to config.json.
c. Architectural patterns/design principles:
• Modular feature services: each hack is encapsulated in its own module (.cpp/.hpp).
• Single main loop coordinating input, game data polling, feature execution, and rendering.
• Separation of concerns: memory abstraction, feature logic, rendering, input, config.
d. Key technologies & libraries:
• C++17 (presumed)
• DirectX11 (hook + device context)
• Dear ImGui (UI and overlay)
• nlohmann/json (configuration)
• iconv (text encoding, if used)