How the Apex Legends DMA cheat works: aimbot, ESP, Skynade and EAC
The Apex Legends DMA cheat never runs on the PC that plays Apex. A DMA card in that machine copies the game's memory to a second PC, the second PC works out where everyone is and what they are doing, and a MAKCU turns the aim decisions back into ordinary mouse movement. This guide follows that loop from the first memory read to the last mouse tick: what the second PC actually reads out of Apex, how the ESP, aimbot, TriggerBot and Skynade are built from it, how shield-aware targeting works, and why Easy Anti-Cheat has nothing to find. If DMA itself is new to you, read What is a DMA? first — this page assumes you know what the card, the firmware and the second PC are for.
The loop, in one picture
- ReadThe DMA card in the gaming PC copies Apex's memory over PCIe and streams it to the second PC over USB 3 — thousands of times a second, without the gaming PC's CPU or Windows being involved.
- DecodeFave DMA on the second PC finds the entity list, the local player and the camera, and turns raw bytes into positions, bones, health, shields, teams, weapons and visibility.
- DecideESP is projected onto the screen, the aimbot picks a target and computes the angle to its bone, the TriggerBot checks whether your crosshair is on a hitbox, Skynade solves a grenade arc.
- ActThe overlay is drawn on the second monitor or, through a Fuser, on your main one. Aim and fire commands go to the MAKCU, which delivers them to the gaming PC as genuine mouse input.
- RepeatEvery tick. Apex only ever sees a PC playing Apex and a mouse moving.
What the second PC reads out of Apex
Apex keeps everything about the current match in memory in a predictable layout: an entity list with one entry per player, bot, dummy, item and projectile, a local player entry for you, and a view matrix describing where your camera is and where it points. Each player entry carries far more than a position:
| Read from memory | What the cheat builds from it |
|---|---|
| World position | Boxes, distance, snaplines, both radars, aimbot target selection |
| Bone positions | Skeleton ESP, head circles, the head / body aim point, per-bone visibility |
| Health and shield values | Health and armor bars, shield-tier colour, "lowest health" priority |
| Team, name, bot flag | Team filtering, name tags, separate toggles for bots and teammates |
| Held weapon and ammo | Weapon icons on ESP, per-weapon aimbot and recoil profiles |
| Visibility and alive state | Visible / hidden colours, dead-body markers, "only aim at what is in view" |
| Item entities and rarity | Loot ESP tiered grey to red, weapon and ammo filters |
| Deployed shield entities | Shield-aware targeting for Newcastle, Rampart, Lifeline and Gibraltar |
| Your camera (view matrix) | Projects every 3D point above onto your 2D screen, and gives the aimbot your current angles |
Every one of those is a read. Fave DMA never writes a value back into Apex — no changed health, no teleported entity, no modified angle in memory. That read-only rule is the single most important safety property of the whole design, and it is why the aimbot needs a MAKCU instead of simply overwriting your view angles.
ESP: projecting the world onto your screen
Once the second PC has a player's position, the view matrix lets it convert that 3D world coordinate into a 2D pixel on your screen. Repeat for every bone and you have a skeleton; for the top and bottom of the model and you have a box; for you and the target and you have a snapline. The overlay is drawn with a normal graphics window on the second PC, which is why it can show anything — names, distance, health and armor bars, weapon icons, dead-body markers, glow-style highlighted models with an optional rainbow mode — without a single pixel being drawn by Apex itself.
By default you watch that overlay on the second PC's monitor. A Fuser merges it into your main display so you play on one screen; it is optional, and covered in the Fuser setup guide. Visibility checks colour targets differently depending on whether a line from your camera to their bones is blocked, and the loot ESP filters item entities by rarity, weapon and ammo type so you only see what you are looking for.
The MAKCU aimbot
An aimbot is an angle problem. Given your camera position and angles, and a target bone's position, there is exactly one yaw and pitch that puts the crosshair on it. The cheat computes that, subtracts your current angles, and gets a delta — "turn 3.2° left and 0.8° down". Turning that delta into movement is where DMA aimbots differ from injected ones, and it is why the Apex cheat requires a MAKCU.
Why a MAKCU, and what it does
The MAKCU sits between your real mouse and the gaming PC. Your mouse plugs into it, it plugs into the gaming PC, and to Windows and EAC it is your mouse — same descriptors, same identity. Your real movements pass straight through. When the second PC wants to add an aim correction it sends the mouse delta to the MAKCU over a separate cable, and the MAKCU emits it as ordinary HID mouse reports, merged with your own input. Apex receives mouse movement from a mouse; there is no software input, no simulated event, nothing on the gaming PC generating it. There is deliberately no other aim mode — every correction goes through the MAKCU, so the gaming PC only ever sees a mouse.
Making it look like a hand
- Smoothing splits the delta into many small steps over several ticks instead of one snap, with separate values for hip-fire and ADS — the two have different sensitivities in Apex, so they need different tuning.
- FOV is the circle around your crosshair inside which targets are considered. Keep it small and the aimbot only finishes flicks you started yourself.
- Bone priority can be locked to head or body, or left on auto, which picks the bone that is visible and closest to your crosshair.
- Recoil compensation reads which weapon you hold and adds a counter-delta on both axes to your movement while you fire, following that weapon's pattern. It is applied through the MAKCU like everything else, so it looks like you pulling down.
TriggerBot
The TriggerBot answers a simpler question: is my crosshair on an enemy hitbox right now? The second PC casts a ray from your camera along your view direction and tests it against every enemy's hitboxes. When it hits — or, in the second mode, the moment the aimbot has locked on — it sends a click to the MAKCU. Three settings shape it: a delay so the shot does not land the same tick the crosshair arrives, a hitbox size that decides how generous the test is, and prediction that accounts for the time between the read and the shot. Point-blank fights get extra padding, because at two metres a strafing Octane crosses a hitbox in a single tick.
Skynade: solving the grenade
Skynade is a physics solver. When you hold a throwable, the cheat reads the grenade type — standard frag, arc star or Fuse's Grenadier ordnance, each with its own launch speed and gravity — and the target's position, then works out the launch angle that lands the projectile there. Most throws have two solutions: a flat, direct one and a high, lobbed one, and Skynade shows both so you pick the arc that clears cover. The result is drawn on the overlay as an aim indicator; you line up, throw normally, and the grenade lands where the marker said it would.
Shield-aware targeting
Four legends can put a shield between you and a target: Newcastle's mobile shield, Rampart's Amped Cover, Lifeline's shield and Gibraltar's dome. Those shields are entities too, and the cheat reads them. Before the aimbot commits and before the TriggerBot fires, it checks whether the line from your camera to the target's bone crosses a deployed shield, and if it does, it holds. That saves the ammo, and it avoids the very obvious tell of firing into a Gibraltar dome the instant it drops.
Two radars
The overlay radar (toggle with F10) draws a top-down map around you from the same positions the ESP uses — every player as a dot, colour-coded by team and distance. The Web Radar is the same picture served by the second PC as a web page on your LAN, so you can open it on a phone or tablet next to the keyboard, or on a second screen, without giving up any of your game view. Nothing on the gaming PC is involved in either.
Why EAC does not see it
Easy Anti-Cheat runs as a kernel driver on the gaming PC. It scans processes, loaded drivers, handles to the game, memory reads from other programs, and hooks inside Apex. Every one of those checks is looking for something on the gaming PC. With a DMA setup:
- There is no cheat process on the gaming PC — the software runs on the second machine.
- Nothing is injected and nothing hooks Apex; the game's code is untouched.
- Memory is read by the DMA card over PCIe, not by any program EAC can enumerate.
- Aim arrives from a device that identifies as your mouse.
What EAC can inspect is the hardware itself: the identity your DMA card reports on the PCIe bus. That is why firmware matters. Stock firmware announces the card for what it is and is blacklisted; 1:1 emulated firmware answers every probe exactly as a harmless real device would. The card is the only part of this setup that can be seen at all, so it is the only part you need to get right.
The two ways people still get banned. Flagged firmware — running an old or public build that EAC has learned — and blatant play. Instant flicks, huge FOV, firing through smoke at skeletons and pre-aiming everyone behind walls will get you reported, and reports get you reviewed. Keep the firmware current and the settings believable and you have removed almost all of the risk.
Supported hardware
The cheat runs on every mainstream DMA board: CaptainDMA 35T and 75T, LeetDMA, Squirrel, Raptor, ScreamerM.2, Enigma-X1 and PCILeech-based FT2232H and FT601 / USB3 cards, on stock PCILeech firmware or an emulated build. For the full shopping list — two Windows 10/11 PCs, a DMA card with undetected firmware, a MAKCU for aim, an optional Fuser — see the product page, and for what each part does, What is a DMA?.
Configs, themes and languages
Every setting above lives in a JSON config. Save as many as you like — an aggressive one for pubs, a quiet one for ranked — and set a default that loads with the cheat. The menu comes in several themes and in English, Simplified Chinese, Traditional Chinese and Japanese.
Setting it up
This page explains the how; the setup guides cover the do. In order: prepare the second PC, connect the MAKCU (quick-start pinned in Discord), optionally flash a Fuser for single-monitor play, and keep the troubleshooting page handy for the first launch. A memory map is only needed if reads drop out.
Frequently asked questions
Is the Apex Legends DMA cheat undetected?
Nothing runs inside Apex or on the gaming PC: the second PC reads memory through the DMA card and the MAKCU delivers aim as real mouse input, so EAC only ever sees ordinary hardware. The one component it can inspect is the card's firmware identity, which is why you run an emulated build and keep it current. No setup is bulletproof — bans trace back to flagged firmware or reckless play.
Do I need a MAKCU for the Apex cheat?
For the aimbot and TriggerBot, yes — it is what turns aim decisions into physical mouse input on the gaming PC. ESP, both radars, Skynade and loot ESP work with the DMA card alone.
Does the Apex DMA cheat write to memory?
No. Every feature is built from reads: positions, bones, health, shields, weapons, items and your camera. Nothing is changed in the game, which is why the aimbot goes through a MAKCU rather than overwriting your view angles.
How does the aimbot handle Newcastle and Gibraltar shields?
Deployed shields are entities the cheat can read. Before the aimbot commits and before the TriggerBot fires, it checks whether a shield sits on the line to the target's bone and holds fire until the target is genuinely exposed.
Which DMA cards work with the Apex cheat?
CaptainDMA 35T/75T, LeetDMA, Squirrel, Raptor, ScreamerM.2, Enigma-X1 and PCILeech FT2232H / FT601 boards, on stock or emulated firmware.
Can I try it before buying?
Yes. Open a ticket on Discord for a one-day trial key with every feature unlocked — no card details, no commitment. Plans after that are €9.99 a week, €19.99 a month or €124.99 for lifetime.