Server authority reduces what client information buys you
When destruction, physics and world state are simulated server-side, the client holds less authoritative information than in a traditional shooter. That does not eliminate information advantage, but it does reduce the return on extracting client memory.
01
EAC in The Finals
EAC validates the client, monitors for injected code and unsigned drivers, and can enumerate hardware. It reports detection events to Embark for enforcement.
Because Embark runs a heavily server-side simulation, many of the values a client-side cheat would traditionally read are either not present locally or are non-authoritative predictions.
02
What server authority changes
In a client-authoritative shooter, the client knows more than it displays: full player positions, inventory, sometimes line-of-sight state. In a server-authoritative game with heavy destruction simulation, the client holds a prediction of world state that the server can correct at any time.
The practical result is that extracting client memory yields less reliable information. What remains valuable is anything replicated to the client — visible player positions, and the network stream itself. That is a narrower surface than in older shooters.
| Architecture | Client knows | Information value |
|---|---|---|
| Client-authoritative | Full state | High |
| Hybrid | Most state | Medium |
| Server-authoritative + destruction | Predictions + replicated entities | Lower, but not zero |
03
DMA in a server-authoritative title
A DMA device reads host memory. If the host memory does not contain authoritative world state, the device returns less useful data — which is a technical limitation of the approach in this specific architecture rather than a detection property.
Detection works the same way as elsewhere: PCIe enumeration, driver inspection and behavioural analysis of match outcomes. EAC handles the first two, Embark handles the third.
04
What Embark's terms prohibit
Embark prohibits cheating, unauthorised modification and third-party tools providing an advantage. No approved-hardware list exists. Hardware-level enforcement is applied for severe cases, and ban evasion through new accounts is a separate violation.
05
Practical guidance
Standard separation applies for research: separate machines, no shared images, no reused identifiers. In a game with this architecture, the interesting research question is not device visibility but what information the client actually holds — a question answerable from public engine documentation and packet captures on your own machine.
FAQ
Frequently asked questions
01Does The Finals use Easy Anti-Cheat?
Yes. The Finals uses Easy Anti-Cheat, owned and operated by Epic Games.
02What does server-authoritative mean for information advantage?
It means the client holds predictions rather than authoritative world state, so extracting client memory returns less reliable information than in a client-authoritative shooter.
03Does Embark hardware ban accounts?
Hardware-level enforcement is applied for severe cases. The identifier set is not published.
04Is DMA still effective in The Finals?
Replicated entity data — visible player positions and the network stream — remains accessible. The reduction is in authoritative world state, not in everything.
05Does server authority make client-side hardware useless?
No. Replicated entity state — visible player positions and the network stream itself — still reaches the client. What shrinks is authoritative world state: destruction, physics and container contents that the server holds and the client only predicts.
06Why do older shooters give hardware more to read?
Because a client-authoritative design keeps full state locally. The client knows more than it displays, so reading its memory returns information the player was never meant to see. Server-authoritative designs deliberately remove that.
SOURCES
