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 Fortnite.
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 and code xrefs, zero brittle byte signatures).
• Reflection SDK: All UE5 classes, structs, properties, and offsets (sdk-dump.tsv, classes.txt) - encrypted property offsets solved from one live anchor (RootComponent).
• String Pool & Enums: Full FName pool and declaration-ordered UEnum lists.
• Unreflected Engine Offsets: ULevel::Actors, SceneComponent::ComponentToWorld, skeletal bone arrays, and head bone indices.
• Live Replication: Player states, pawns, weapons, chests, and loot.
Step-by-Step Usage Guide
1. Prerequisites
• Fortnite 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
Here we can stop, and AI can do everything for you just ask AI to read file UPDATE.md, it will do everything for you!
Or follow instruction below, but remember due to game update there might be a need to update source code!
2. Build
3. Dump Sequence (Run in order)
4. Verify Live
5. Apply
• Copy generated offsets from the dump/sdk output and docs\fn\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 again!
Today I'm release another DMA/Poor DMA cheat, but this time we are talking about Fortnite. But 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 on the same computer, but in such case there is risk of getting ban due to overlay on the game, everything what you need to know regarding this approach is located under this link, a lot of reading but worth it, thus below link is about Poor DMA, for people without DMA cards...
Today I'm release another DMA/Poor DMA cheat, but this time we are talking about Fortnite. But 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 on the same computer, but in such case there is risk of getting ban due to overlay on the game, everything what you need to know regarding this approach is located under this link, a lot of reading but worth it, thus below link is about Poor DMA, for people without DMA cards...
- Plisskien
- Replies: 28
- 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 and code xrefs, zero brittle byte signatures).
• Reflection SDK: All UE5 classes, structs, properties, and offsets (sdk-dump.tsv, classes.txt) - encrypted property offsets solved from one live anchor (RootComponent).
• String Pool & Enums: Full FName pool and declaration-ordered UEnum lists.
• Unreflected Engine Offsets: ULevel::Actors, SceneComponent::ComponentToWorld, skeletal bone arrays, and head bone indices.
• Live Replication: Player states, pawns, weapons, chests, and loot.
Step-by-Step Usage Guide
1. Prerequisites
• Fortnite 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
Here we can stop, and AI can do everything for you just ask AI to read file UPDATE.md, it will do everything for you!
Or follow instruction below, but remember due to game update there might be a need to update source code!
2. Build
Code:
cd "poor dma\fortnite\dumper"
cargo build --release
3. Dump Sequence (Run in order)
Code:
# 1. Capture module image (~462MB, incl. code)
cargo run --release -- image fn code
# 2. Locate GObjects & GNames (encrypted: read off the code)
cargo run --release -- constants fn
cargo run --release -- xref fn imm:<world_mul>
cargo run --release -- namexref fn
cargo run --release -- gnames fn
# 3. Dump FName pool
cargo run --release -- names fn
# 4. Measure UObject header & walk UObjects
cargo run --release -- layout fn
cargo run --release -- objects fn
# 5. Core dump: classes & properties (prints ready offsets.toml values)
cargo run --release -- dump fn
cargo run --release -- sdk fn
# 6. Locate live GWorld
cargo run --release -- gworld fn
# 7. Dump enums
cargo run --release -- enums fn
4. Verify Live
Code:
# Validate reading players and camera
cargo run --release -- probe fn
# Verify view-projection matrix
cargo run --release -- canvas fn
# Discover bone array and head bone
cargo run --release -- bones fn
5. Apply
• Copy generated offsets from the dump/sdk output and docs\fn\statics.txt into offsets.toml.
• Change verified = true once probe passes.
