How clareow/external_pubg works
This is an external PUBG memory-reading and aiming/overlay tool, described only as an educational project. Its visible workflow reads game state through a Windows device-I/O driver, resolves encrypted pointers and actor data, transforms camera and bone coordinates, then draws skeleton lines or sends mouse movement. The README documents no broader feature set, and Main.cpp is unsampled, so its orchestration and any additional UI or actor-selection stages cannot be confirmed; edges below follow only visible calls.
Main entry points: SDK.h State and rendering SDK · driver.h Memory I/O API · Aimbot.h Mouse aiming · GNames.h Name lookup
Components 13
Game memory access
- Driver client
driver.cpp - Memory I/O API
driver.h
Game state decoding
- State and rendering SDK
SDK.h - Name lookup
GNames.h - Game offsets
Address.h - Pointer decryption
XeDecrypt.h
Aim and overlay
- 3D projection
Vector.h - Mouse aiming
Aimbot.h - Direct3D output
SDK.h
Other components
- Operator
- PUBG process
- NMH1313 device
- Windows input
Connections 13
- Driver client → NMH1313 device: opens device
- Memory I/O API → NMH1313 device: issues I/O
- NMH1313 device → PUBG process: reads process memory
- State and rendering SDK → Memory I/O API: reads game state
- State and rendering SDK → Pointer decryption: decrypts pointers
- State and rendering SDK → 3D projection: projects world positions
- State and rendering SDK → Direct3D output: draws skeleton lines
- State and rendering SDK → Memory I/O API: reads bone and camera data
- Name lookup → Memory I/O API: reads name table
- Name lookup → Pointer decryption: decrypts name pointers
- State and rendering SDK → Mouse aiming: not shown
- Mouse aiming → Windows input: sends mouse movement
- Operator → Mouse aiming: initiates