# Season 30

<table border="1" id="bkmrk-captured-at-game-bui" style="border-collapse: collapse; width: 113.452%; height: 136px;"><colgroup><col style="width: 12.5119%;"></col><col style="width: 12.5119%;"></col><col style="width: 17.755%;"></col><col style="width: 16.6826%;"></col><col style="width: 18.3601%;"></col><col style="width: 22.2738%;"></col></colgroup><tbody><tr style="height: 29.7875px;"><td style="height: 29.7875px;">**Type**</td><td style="height: 29.7875px;">**captured at**</td><td style="height: 29.7875px;">**game build**  
</td><td style="height: 29.7875px;">**memory dump completeness**</td><td style="height: 29.7875px;">**links**  
</td><td style="height: 29.7875px;">**Comment**</td></tr><tr style="height: 96.8px;"><td style="height: 96.8px;">Generic</td><td style="height: 96.8px;">16.10.2026</td><td style="height: 96.8px;">R5pc\_r5-301\_J65\_CL11630615\_FSv30\_1\_2026\_10\_02\_09\_54</td><td style="height: 96.8px;">N/A</td><td style="height: 96.8px;">**No IDB Present**

</td><td style="height: 96.8px;"></td></tr></tbody></table>

<p class="callout warning">**AC Migration:** The game is now protected by EA Javelin instead of EAC. Alongside it, you will find R5AC still being deployed and doing similar stuff that we uncovered back in the day. Additionally, client-side code is present for an integration of Anybrain, a solution advertised as an AI-based cheat detection. Although it should be mentioned that it wasn't active within my own limited tests.</p>

<p class="callout danger">**Packer Removal (partly):** It seems like respawn is no longer applying dynamic memory protection onto the primary game executable, r5apex\_dx12.exe. I'm unable to claim that everything related to their old Theia implementation is gone, as it was doing much more than just packing, for example it also hard stuff for hardware identification and broader anti-tamper functionality. This means you will be able to obtain a full memory dump without having to defeat a packer that periodically re-encodes stale pages.</p>

### Useful Codesites and Globals

#### Experiments System

<table border="1" id="bkmrk-name-address-comment" style="border-collapse: collapse; width: 100%; height: 294.547px;"><colgroup><col style="width: 30.5239%;"></col><col style="width: 44.5476%;"></col><col style="width: 25.0238%;"></col></colgroup><tbody><tr style="height: 29.7969px;"><td style="height: 29.7969px;">**Name**  
</td><td style="height: 29.7969px;">**Address**</td><td style="height: 29.7969px;">**Comment**</td></tr><tr style="height: 147.375px;"><td style="height: 147.375px;">R5::FetchExperimentsForProfile</td><td style="height: 147.375px;">%DUMP\_BASE%+0x1AC7A10</td><td style="height: 147.375px;">Sends an HTTP/S request towards an endpoint URL "experimentation/v1/fetch-experiment-grouping". It attaches various parameters including Player/Nucleus-ID, and then receives a list of experiments and their individual states.</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px;">R5::ParseExperiments</td><td style="height: 35.3906px;">%DUMP\_BASE%+0x1AC8430</td><td style="height: 35.3906px;">Parses the experiment list that was previously received with the previous function. It has a special handling case for "8-1-anyb-rollout", which if the experiment is determined as active and you're within the active treatment group, a ConVar named raw\_input\_client\_send\_enable is enabled.

</td></tr></tbody></table>


#### Input Telemetry (Anybrain)

<table border="1" id="bkmrk-r5%3A%3Aprocessinputtele" style="border-collapse: collapse; width: 100%; height: 294.547px;"><colgroup><col style="width: 30.5125%;"></col><col style="width: 44.4577%;"></col><col style="width: 25.0298%;"></col></colgroup><tbody><tr style="height: 46.5938px;"><td style="height: 46.5938px;">R5::ProcessInputTelemetry\_Opaque\_1</td><td style="height: 46.5938px;">%DUMP\_BASE%+0x1CBDD60</td><td style="height: 46.5938px;">Processes some input telemetry related data, and conditionally writes it to a global ring buffer.</td></tr><tr><td>R5::ProcessInputTelemetry\_Opaque\_2</td><td>%DUMP\_BASE%+0x1D830B0</td><td>  
</td></tr><tr><td>R5::InputTelemetrySender::1</td><td>%DUMP\_BASE%+0x1D834D0</td><td>Used to send player input telemetry using standard CNetChan facilities. (SendNetMsg+SendDatagram)</td></tr><tr><td>R5::InputTelemetrySender::2</td><td>%DUMP\_BASE%+0x1D82E00

</td><td>Uses sub\_1A36B90 to indirectly invoke R5::InputTelemetryDispatcher::1</td></tr><tr><td>R5::InputTelemetryDispatcher::1</td><td>%DUMP\_BASE%+0x1D832A0</td><td>Used to send player input telemetry using standard CNetChan facilities. (SendNetMsg+SendDatagram)</td></tr></tbody></table>

#### Game Engine

<table border="1" id="bkmrk-cl_move-%25dump_base%25%2B" style="border-collapse: collapse; width: 100%; height: 294.547px;"><colgroup><col style="width: 30.5239%;"></col><col style="width: 44.5476%;"></col><col style="width: 25.0238%;"></col></colgroup><tbody><tr style="height: 46.5938px;"><td style="height: 46.5938px;">CL\_Move</td><td style="height: 46.5938px;">%DUMP\_BASE%+0x1AF4C30</td><td style="height: 46.5938px;">  
</td></tr><tr><td>CL\_SendMove</td><td>%DUMP\_BASE%+0x1AF49E0</td><td>  
</td></tr><tr><td>C\_ClientRenderable::SetupBones</td><td>%DUMP\_BASE%+0x1FE6950</td><td>  
</td></tr></tbody></table>

#### R5AC

<table border="1" id="bkmrk-enqueueviolation-%25du" style="border-collapse: collapse; width: 100%; height: 122.984px;"><colgroup><col style="width: 30.5239%;"></col><col style="width: 44.5476%;"></col><col style="width: 25.0238%;"></col></colgroup><tbody><tr style="height: 46.5938px;"><td style="height: 46.5938px;">EnqueueViolation</td><td style="height: 46.5938px;">%DUMP\_BASE%+0x1D85A90</td><td style="height: 46.5938px;">Appends a new anti-cheat telemetry message into the global queue, in many cases for a violation of some sort, but it hasn't been proved that it is only used for violations.

</td></tr><tr style="height: 29.7969px;"><td style="height: 29.7969px;">EnqueueOrSendViolationDirectly</td><td style="height: 29.7969px;">%DUMP\_BASE%+0x1D85BF0</td><td style="height: 29.7969px;">Essentially something similar as the above EnqueueViolation function, with one difference being that it has a fast path: If your game client has an active network channel to a game server, it will attempt to send the anti-cheat telemetry message directly using engine API's like C\_NetChan::SendNetMsg and C\_NetChan::SendDatagram.). Otherwise it just calls into EnqueueViolation to do the usual queueing.</td></tr><tr style="height: 46.5938px;"><td style="height: 46.5938px;">InitializeStackWalker</td><td style="height: 46.5938px;">%DUMP\_BASE%+0x1D83E40</td><td style="height: 46.5938px;">Responsible for various things:

- Initialization of imports for R5AC stack walker / control flow inspection
- Initialization of the code execution whitelist. Its exact format is to be studied.
- Sets a global variable of type u8 to 1 when initialization succeeds. The inlined stack walker code in game &amp; engine functions then checks this alongside their other calculations for determining whether the stack walker should run.

My understanding of this list is that it also is very likely a region-based whitelist and not per module, like you would initially think. So they kept that design choice and just switched it with a hash map.

There seems to be some other changes too, including how the whitelist is built. In one occasion, it searches for a specific module in the LDR, loops through its regions and adds any section that is executable, non-discardable to its whitelist structure.

</td></tr></tbody></table>

#### Useful Patches

Below is a list of convenient patches that you can apply, to enhance your experience within Apex. The best part is you're not introducing anything artifical into the mix. If you're a controller player and already used to the feeling of aim assist, for example, you can just buff it directly. Note that this is probably no longer a golden ticket with the rise of Artifical Intelligence in EA's playbook.

Another positive aspect is that you don't necessarily need to patch anything to achieve much of these. For example, with the name hider, you can just manipulate a couple of global variables within Apex to make the lookup fail. For the aim assist stuff, you could reverse engineer their playlist variable system more deeply, and then figure out how to do it more stealthily.

Same thing applies for the deadzone check. Basically, inside a mouse related processing function at r5apex\_dx12.exe, it just sets some global u64 which represents the last time your mouse has moved. You can log the values, see when they change, improve your model of the surrounding code and then find a way to achieve it in a much more subtle way. My approach saved me a lot of time, because for the most time I could afford changing whatever I wanted. This is subject to change but even if that's no longer sustainable, it's still valuable for things like narrowing down the amount of code you need to reverse engineer.

<table id="bkmrk-patch-name-address-%2F" style="width: 88.8095%; height: 447.358px;"><tbody><tr style="height: 29.7017px;"><th style="width: 30.6005%; height: 29.7017px;">Patch Name

</th><th style="width: 15.7029%; height: 29.7017px;">Address / Offset

</th><th style="width: 53.6851%; height: 29.7017px;">Patch Bytes

</th></tr><tr style="height: 66.1222px;"><td style="width: 30.6005%; height: 66.1222px;">Gamepad Assist Strength Changer

</td><td style="width: 15.7029%; height: 66.1222px;">`0x20A83F0`

</td><td style="width: 53.6851%; height: 66.1222px;">`48 31 C0 0F 57 C0 48 C7 C0 CD CC 4C 3F 66 0F 6E C0 C3`

`moves 0.8f in hexadecimal representation into XMM0`

</td></tr><tr style="height: 48.3807px;"><td style="width: 30.6005%; height: 48.3807px;">Mouse Inactivity Check

</td><td style="width: 15.7029%; height: 48.3807px;">`0x20A7022`

</td><td style="width: 53.6851%; height: 48.3807px;">`90 90 90 90 90 90`

`just a bunchof NOPs`

</td></tr><tr style="height: 30.6392px;"><td style="width: 30.6005%; height: 30.6392px;">Deadzone Check

</td><td style="width: 15.7029%; height: 30.6392px;">`0x20A8753`

</td><td style="width: 53.6851%; height: 30.6392px;">`EB`

</td></tr><tr style="height: 30.6392px;"><td style="width: 30.6005%; height: 30.6392px;">Should Enable Aim Assist

</td><td style="width: 15.7029%; height: 30.6392px;">`0x20A6FE0`

</td><td style="width: 53.6851%; height: 30.6392px;">`B0 01 C3`

</td></tr><tr style="height: 30.6392px;"><td style="width: 30.6005%; height: 30.6392px;">Input Enforcer 1

</td><td style="width: 15.7029%; height: 30.6392px;">`0x21B1380`

</td><td style="width: 53.6851%; height: 30.6392px;">`B0 01 C3`

</td></tr><tr style="height: 83.8636px;"><td style="width: 30.6005%; height: 83.8636px;">Input Enforcer 2

</td><td style="width: 15.7029%; height: 83.8636px;">`0x21B12E0`

</td><td style="width: 53.6851%; height: 83.8636px;">`B0 01 C3`

`when patching this and the first one, aim assist will work on mouse and keyboard. a controller needs to be attached nonetheless even if you can just play on MnK afterwards.`

</td></tr><tr style="height: 66.1222px;"><td style="width: 30.6005%; height: 66.1222px;">Name Hider

</td><td style="width: 15.7029%; height: 66.1222px;">`0x1A40391`

</td><td style="width: 53.6851%; height: 66.1222px;">`E9 B2 00 00 00 90`

`when patched, player names in your hud and world text will appear as Unknown:Unknown `

</td></tr></tbody></table>

<p class="callout danger">EA's kernel driver is currently performing reads on various addresses within the game's code section. Whether that is for prevention or detection, i can't tell. But it would make sense for both use cases. During a short test session, it was most prominently a couple routines inside eaanticheat.sys accessing my target pages. Once I'm able to answer some of my open questions regarding this mechanism, I will update this book to reflect any new insights. You should expect them to have multiple integrity checks for something this obvious, but let's not overstate it too early. </p>