People ask us all the time whether our Wardogs build is external or internal, usually because a friend told them one is safer or one has better aimbot. Both parts are half-right. Here is how the two modes actually work against EAC, what we ship by default, and the narrow situation where we would change our mind.
What external and internal actually mean
An external cheat is a separate program running next to Wardogs. It reads the game’s memory from the outside, does the math for ESP boxes or aim corrections, and draws overlays or feeds mouse input back in. Wardogs never loads a single byte of our code. To EAC, the game process looks clean — because it is. The tradeoff is that some features are harder to build well from the outside, especially true silent aim, weapon-recoil edits, and anything that has to change how the game handles a bullet at the engine level.
An internal cheat lives inside the Wardogs process itself. Our code sits in the same memory space as the game, which means it can hook functions directly, rewrite recoil, run genuine silent aim, and touch weapon behaviour at the source. The cost is scrutiny. EAC runs in kernel mode and spends most of its budget scanning what is inside protected game processes. An internal build has to hide a lot more surface area, and if any part of it slips, the ban wave hits harder and sooner.
What we ship on Wardogs by default
Our default Wardogs build is external. Given that EAC on this title is kernel-mode and BULKHEAD is actively watching a 100-player, three-team map during Early Access, keeping our code out of the game process is the honest call. It gives us the ESP, radar, aim assistance, and information features most players actually use, without putting our whole runtime under EAC’s microscope every time you load in.
The features you lose by going external are the ones we would not recommend anyway on a public server: instant-lock silent aim, no-recoil weapon rewrites, one-shot-kill hacks. Those are the fastest way to end up on a report queue, and they are the exact class of feature that pulls kernel anticheats into a fight you cannot win on a Tuesday afternoon.
The panel does not have an external-or-internal switch, and it never will. The ops desk ships whichever build is safer that day. If EAC pushes an update that makes the external path shaky, we pause the loader and rebuild before we let anyone in, even if it costs a day of uptime.
When we would flip to internal
There is one honest reason to ever ship an internal build on Wardogs: a game or engine update that breaks external reads to the point that features become unreliable or dangerous. If BULKHEAD reworks how the UE5 build serialises player transforms, or moves core state behind an encrypted layer that we cannot read cleanly from outside, the external version stops being the safer path. At that point an internal build, done right, is honestly less risky than a broken external one guessing at positions.
If that day ever comes, you will not have to guess. We post the change on /status/, explain what moved and why, and only reopen sales once the new build has held for a full patch cycle. Until then, you can read more about how we think about detection on is it safe, and how the current external build handles targeting on the aimbot settings page.