📎 More information, examples, and scripts — here
DMA (Direct Memory Access) is a technology that allows reading or writing data directly into a computer’s memory bypassing both the CPU and operating system. This makes it possible to access the memory of any process, even if it is protected by anti-cheat systems or mechanisms like:
EyeAuras uses LeechCore — an open-source library by Ulf Frisk, widely recognized as the standard for working with PCIe/Thunderbolt/FPGA DMA devices. It powers popular projects like PCILeech and is frequently used in debuggers, forensic tools, automation, and low-level memory inspection utilities.
With DMA, you gain:
ReadProcessMemory, while under the hood everything goes through a physical PCIe bus.All this is now available through standard EyeAuras scripting — no need to learn HDL, PCIe internals, virtualization, or write your own drivers.
This is the primary and most secure setup. The game and the bot run on different computers, connected via a DMA device.
This setup is very difficult to detect and is generally used in security research and bot development targeting high-security environments.
This setup is less secure:
However — in many real-world cases, DMA is so far outside the detection surface of the game/anti-cheat that no one even checks for it. In those cases, this setup becomes completely viable and much easier to configure.
From a scripting perspective, nothing changes. You use the same IMemory interface:
var playerHp = CoreMem.Read<int>(playerBase + 0x1C4);
if (playerHp < 30)
{
Log.Warn($"Low HP: {playerHp}");
}
CoreMem can now point to a DMA-backed memory interface.playerBase might be a virtual or physical address — you don’t have to worry about it.To use DMA, you’ll need a LeechCore-compatible FPGA board.
The good news: as of 2025, 99% of common FPGA boards are compatible. Just flash the right firmware and connect.
Popular options:
DMA integration is built on a backend layer called IMemoryBackend, which supports:
ReadProcessMemory at runtime — great for debugging or fallback scenarios