Hello forum,
This is part of my project, which is connected with Poor DMA, while the main objective of this project is to be used with the thread in question:
There is a fully free and working DMA/Poor DMA cheat for Wardogs.
Of course, in the case of any game update, there is a need to update the offsets. In that case, this dumper needs to be used. It can additionally be used to make your own cheat. It is also called an agentic dumper, since creating a dumper that will always dump correct offsets without any changes to the code is difficult and is often seen as an unreasonable approach. Thus, there is always some need for manual reversing, which can take some time. My idea was to create all the necessary tools and prompts so that everything could be done by AI.
If you wish to use AI for dumping, just tell it to follow the instructions in the UPDATE.md file. Of course, you still have to read the process memory. Everything is below!
Link:
• Poor DMA (-lan, default): Remotely over TCP port 39172 via Poor DMA server on game PC.
• FPGA DMA (-dma): Direct hardware PCIe DMA (For that you need PCILeech DLLs (vmm.dll, leechcore.dll, FTD3XX.dll, and dbghelp.dll)).
What It Dumps:
• Core Statics: GWorld, GObjects, GNames (found by shape in memory, zero brittle byte signatures).
• Reflection SDK: All UE5 classes, structs, properties, and offsets (sdk-dump.tsv, classes.tsv) — auto-resolves Wardogs' ~52k scrambled property names by shape and original length.
• String Pool & Enums: Full FName pool and declaration-ordered UEnum lists.
• Unreflected Engine Offsets: ULevel::Actors, USceneComponent::Bounds, skeletal bone arrays, and head bone indices.
• Live Replication: Player states, pawns, weapons, vehicles, and deployables.
Step-by-Step Usage Guide
1. Prerequisites
• Wardogs running in a live match deployed on foot (not main menu).
• Poor DMA server running on the game PC if you use it, if DMA only game must be running on the first computer
• Installed Rust and Cargo to compile code on second computer
2. Build
3. Dump Sequence (Run in order)
You can do it manually or just ask AI to read file UPDATE.md, it will do everything for you!
4. Verify Live
5. Apply
• Copy generated offsets from the sdk output and docs\wd\statics.txt into offsets.toml.
• Change verified = true once probe passes.
This is part of my project, which is connected with Poor DMA, while the main objective of this project is to be used with the thread in question:
Hello my people!
Today I would like to share one of my cheats that I vibe coded (there will be more
), at first I would like to clarify that this is DMA cheat, but it can be also used as External cheat if we were to use my technology that I called Poor DMA, everything what you need to know regarding this approach is located under this link:
While important things is that, there is no possibility to use write with Poor DMA, thus you can have...
Today I would like to share one of my cheats that I vibe coded (there will be more
While important things is that, there is no possibility to use write with Poor DMA, thus you can have...
- Plisskien
- Replies: 21
- Forum: DMA Cheats/Software
Of course, in the case of any game update, there is a need to update the offsets. In that case, this dumper needs to be used. It can additionally be used to make your own cheat. It is also called an agentic dumper, since creating a dumper that will always dump correct offsets without any changes to the code is difficult and is often seen as an unreasonable approach. Thus, there is always some need for manual reversing, which can take some time. My idea was to create all the necessary tools and prompts so that everything could be done by AI.
If you wish to use AI for dumping, just tell it to follow the instructions in the UPDATE.md file. Of course, you still have to read the process memory. Everything is below!
Link:
• Poor DMA (-lan, default): Remotely over TCP port 39172 via Poor DMA server on game PC.
• FPGA DMA (-dma): Direct hardware PCIe DMA (For that you need PCILeech DLLs (vmm.dll, leechcore.dll, FTD3XX.dll, and dbghelp.dll)).
What It Dumps:
• Core Statics: GWorld, GObjects, GNames (found by shape in memory, zero brittle byte signatures).
• Reflection SDK: All UE5 classes, structs, properties, and offsets (sdk-dump.tsv, classes.tsv) — auto-resolves Wardogs' ~52k scrambled property names by shape and original length.
• String Pool & Enums: Full FName pool and declaration-ordered UEnum lists.
• Unreflected Engine Offsets: ULevel::Actors, USceneComponent::Bounds, skeletal bone arrays, and head bone indices.
• Live Replication: Player states, pawns, weapons, vehicles, and deployables.
Step-by-Step Usage Guide
1. Prerequisites
• Wardogs running in a live match deployed on foot (not main menu).
• Poor DMA server running on the game PC if you use it, if DMA only game must be running on the first computer
• Installed Rust and Cargo to compile code on second computer
2. Build
Code:
cd "poor dma\wardogs\dumper"
cargo build --release
3. Dump Sequence (Run in order)
You can do it manually or just ask AI to read file UPDATE.md, it will do everything for you!
Code:
# 1. Capture module image (~200MB)
cargo run --release -- image wd
# 2. Locate GObjects & GNames
cargo run --release -- find wd
# 3. Dump FName pool
cargo run --release -- names wd
# 4. Walk UObjects
cargo run --release -- objects wd
# 5. Core dump: classes & properties (prints ready offsets.toml values)
cargo run --release -- sdk wd
# 6. Locate live GWorld
cargo run --release -- gworld wd
# 7. Dump enums & level actors
cargo run --release -- enums wd
cargo run --release -- levels wd
4. Verify Live
Code:
# Validate reading players and camera
cargo run --release -- probe wd
# Verify view-projection matrix
cargo run --release -- canvas wd
# Discover bone array and head bone
cargo run --release -- bones wd
5. Apply
• Copy generated offsets from the sdk output and docs\wd\statics.txt into offsets.toml.
• Change verified = true once probe passes.
