How intelsdm/huntdma works
1. This repository is a Windows C++ external cheat for Hunt: Showdown built around DMA-based memory access. The core architecture is not game injection; instead, it reads game state through PCILeech/MemProcFS-style libraries and then renders its own overlay/UI.
2. The top-level entry point is Main.cpp, which likely boots the runtime, initializes memory access, loads config, starts the GUI/overlay, and enters the main update loop.
3. The lowest-level boundary is Memory/. This is the hardware-facing layer: Memory.cpp, InputManager.cpp, and Registry.cpp encapsulate DMA reads, input handling, and any OS-level persistence or support functions. The included leechcore.h, vmmdll.h, and FTD3XX.lib show the project depends on external DMA tooling and an FTDI-based device stack.
4. SDK/ is the game model layer. It defines typed views over Hunt’s in-memory data, such as WorldEntity, Camera, and Environment. This is where raw memory offsets become meaningful objects like players, bosses, items, and the world state used by the cheat features.
5. The feature layer is split by use case:
- Esp/PlayerEsp.cpp and Esp/OtherEsp.cpp handle rendering logic for players and world entities.
- Aimbot/Aimbot.cpp contains target selection and aim assistance behavior.
- Misc/SpectatorAlarm.cpp, Misc/FPS.cpp, and related files implement auxiliary runtime features like spectator warning and frame-rate display.
These modules consume SDK data and produce either visual output or input-side actions.
6. Graphics/ is a self-contained UI and rendering framework. Graphics/Drawing.* provides primitive drawing, while Graphics/Entities/ implements custom controls such as tabs, buttons, sliders, toggles, dropdowns, color pickers, and text boxes. This is the foundation for the in-app configuration menu and overlay widgets.
7. The GUI startup path lives under Graphics/Start Up/. Init.* and GUI.* suggest a dedicated initialization sequence for graphics context creation, overlay setup, and menu wiring before the main feature loop begins.
8. Configuration is its own subsystem under Config/. There are feature-specific config types for aimbot, overlay, players, bosses, supplies, traps, points of interest, and blood bonds. ConfigInstance.h and ConfigUtilities.* centralize load/save behavior so feature modules read settings through a shared configuration boundary.
9. Globals.h, Misc/Vector.*, and Misc/CheatFunction.* provide shared math, common runtime state, and cross-feature helper logic. These are the glue pieces that reduce duplication between ESP, aimbot, and rendering code.
10. Misc/Input.* and Memory/InputManager.* form the input boundary. One layer appears to read/normalize user input, while the other likely bridges that input into the cheat’s runtime decisions such as keybinds, toggles, or aim activation.
11. Graphics/Utility/ contains supporting visual and device-related helpers: fonts, color handling, animation, and Kmbox, which suggests optional integration with external mouse/keyboard hardware or input emulation. This is part of the presentation/input edge rather than the game-state core.
12. Security/XorStr.h is a lightweight string-obfuscation layer, typically used to avoid plain-text literals in the binary. It doesn’t change the main architecture, but it is a cross-cutting concern in a cheat codebase.
13. The main runtime data flow is: DMA memory read → SDK entities/world state → feature modules compute targets/labels/distances → graphics layer draws the ESP/menu → input/config layers control behavior and persistence. The main architectural boundary is between external game memory access and the rest of the application logic.
14. From a diagramming perspective, the important boxes are: external DMA hardware + VMM libraries, memory abstraction layer, Hunt SDK model layer, feature modules, graphics/UI subsystem, and configuration/persistence. The feature modules all depend on the SDK and config layers, while the UI depends on the graphics utilities and shared runtime state.
Main entry points: ConfigUtilities.cpp Config utils · Main.cpp Main · Memory.cpp Memory · Environment.cpp Environment
Components 23
Runtime core
Process entry, memory access, and shared runtime state.
- Main · Bootstraps runtime, memory access, UI, and the main loop.
HuntDMA/Main.cpp - Memory · Hardware-facing DMA read layer and core memory operations.
HuntDMA/Memory/Memory.cpp - Input mgr · Bridges user/device input into runtime decisions and bindings.
HuntDMA/Memory/InputManager.cpp - Registry · OS-level support and stored state helpers.
HuntDMA/Memory/Registry.cpp
Game model
Typed views over Hunt in-memory state.
- World entity · Typed representation of players, loot, bosses, and other world objects.
HuntDMA/SDK/WorldEntity.cpp - Camera · Camera and view-state model used by targeting and overlay math.
HuntDMA/SDK/Camera.cpp - Environment · World and scene-level game state used by feature logic.
HuntDMA/SDK/Environment.cpp
Cheat features
Gameplay logic built on SDK state and config.
- Player ESP · Draws player-specific ESP visuals and labels.
HuntDMA/Esp/PlayerEsp.cpp - Other ESP · Draws non-player world entities such as items and points of interest.
HuntDMA/Esp/OtherEsp.cpp - Aimbot · Selects targets and drives aim assistance behavior.
HuntDMA/Aimbot/Aimbot.cpp - Spectator alarm · Warns when the player is being observed.
HuntDMA/Misc/SpectatorAlarm.cpp - FPS · Displays frame-rate or runtime performance information.
HuntDMA/Misc/FPS.cpp
Graphics/UI
Overlay rendering and in-app menu controls.
- Drawing · Primitive drawing and overlay rendering helpers.
HuntDMA/Graphics/Drawing.cpp - GUI init · Initializes graphics context and wires the menu UI.
HuntDMA/Graphics/Start Up/Init.cpp - GUI · Top-level overlay/menu startup and coordination.
HuntDMA/Graphics/Start Up/GUI.cpp - Controls · Custom UI controls such as tabs, buttons, sliders, toggles, and inputs.
HuntDMA/Graphics/Entities/Entity.cpp - Graphics utils · Fonts, colors, animation, and Kmbox integration helpers.
HuntDMA/Graphics/Utility/Font.cpp
Configuration
Load/save boundary for feature settings.
- Config utils · Shared load/save and config-instance plumbing.
HuntDMA/Config/ConfigUtilities.cpp
Shared helpers
Cross-cutting utilities and common helpers.
- Globals · Common runtime state and cross-feature shared values.
HuntDMA/Globals.h - Cheat funcs · Common logic shared across ESP, aimbot, and rendering modules.
HuntDMA/Misc/CheatFunction.cpp - Vector math · Shared vector and geometry utilities.
HuntDMA/Misc/Vector.cpp - Input · Higher-level input handling used by features and UI.
HuntDMA/Misc/Input.cpp
Security
String obfuscation and related hardening.
- XorStr · String obfuscation helper for literals and identifiers.
HuntDMA/Security/XorStr.h
Connections 34
- Main → Memory: init/read · Bootstraps DMA-backed game access.
- Main → GUI init: startup · Starts the graphics and overlay path.
- Main → Config utils: load/save · Loads and persists feature settings.
- Main → Input mgr: binds · Initializes input handling and runtime controls.
- Main → Globals: runtime state · Uses shared state during the main loop.
- Memory → World entity: feeds · Provides raw state for entity decoding.
- Memory → Camera: feeds · Provides camera/view data.
- Memory → Environment: feeds · Provides world/environment data.
- World entity → Player ESP: consumed by · Player entity data drives ESP rendering.
- World entity → Other ESP: consumed by · World entities drive non-player ESP.
- Camera → Player ESP: math input · View data supports screen-space projection.
- Camera → Aimbot: math input · Camera state supports targeting calculations.
- Environment → Other ESP: consumed by · World state drives environmental overlays.
- Environment → Spectator alarm: consumed by · Environment/state is inspected for alerts.
- Environment → FPS: consumed by · Runtime state contributes to status display.
- Aimbot → Input mgr: aim control · Uses input/device control for activation and aim output.
- Player ESP → Drawing: renders via · ESP output is drawn through the rendering core.
- Other ESP → Drawing: renders via · World overlays are drawn through the rendering core.
- GUI init → GUI: wires · Initializes and presents the menu shell.
- GUI → Drawing: renders via · Menu and overlay widgets use drawing primitives.
- GUI → Controls: composes · The menu is built from custom controls.
- Controls → Graphics utils: uses · Widgets rely on fonts, colors, animation, and device helpers.
- Player ESP → Config utils: settings · Reads feature configuration.
- Other ESP → Config utils: settings · Reads feature configuration.
- Aimbot → Config utils: settings · Reads feature configuration.
- Spectator alarm → Config utils: settings · Reads feature configuration.
- FPS → Config utils: settings · Reads feature configuration.
- Config utils → Registry: persist · Can store settings through OS-backed support.
- Cheat funcs → Vector math: math · Shares geometry and vector helpers.
- Cheat funcs → Globals: state · Uses common runtime values.
- Input → Input mgr: bridges · Higher-level input processing connects to device input.
- Input → Cheat funcs: controls · Input decisions feed shared feature logic.
- XorStr → Main: obfuscates · String hiding applies cross-cuttingly.
- XorStr → GUI: obfuscates · String hiding applies cross-cuttingly.