The game client has changed
Update 2.2 reaches far beyond one balance value. It includes adjustments to grappling and climbing, weapon animations, audio, ARC enemy behavior, quests, UI, maps, memory use, and frigate stability. Hydra also received behavior fixes for target selection and close-range attacks, alongside an increase to its base damage.
The PvE toggle has now finished beta testing as well. The developers are collecting player feedback on its effect on regular PvPvE sessions, and some players are due to receive a survey from October 22. That feedback process is about the mode’s future; it is not a statement that third-party software is accepted or lower-risk in PvE.
What this means for cheat users
A game update changes the client that cheat software has to interact with. That can require a provider to validate or update its build. An older version may stop working properly, fail to launch, or no longer have a current status after the patch.
There is no anti-cheat update, detection notice, ban wave, or named cheat mentioned in the supplied report. It would be wrong to present Update 2.2 as confirmed detection. It would be equally wrong to assume that software remains compatible merely because the patch notes do not mention anti-cheat.
If you use or plan to buy BTG for ARC Raiders or Blanklabs Raiders, check the current status on the relevant product page and through its support channel. Do not rely on reports made before the game update. Without a provider’s current compatibility confirmation, waiting is the sensible option.
PvE does not establish compatibility
The PvE test may change how players approach a match, but it does not establish that any external tool is ready for the new client. Mode rules can evolve, while the software still needs to be checked against the live game build.
The same applies to DH Wallhack for ARC Raiders. A tool’s feature type does not confirm its status after a patch. Playing only in PvE is not a substitute for an up-to-date compatibility notice.
What to do now
- Check the status of the exact product you intend to use after Update 2.2.
- If that status has not been updated or confirmed, do not run an old build with the new game client.
- Do not treat the lack of reported bans as a safety guarantee; using third-party software always carries risk.
- Review how cheat detection and ban waves work before deciding whether to wait or proceed.
Bottom line: Update 2.2 does not confirm a ban wave, a detection event, or working status for any cheat. The only meaningful signal is a current confirmation from the provider of the specific product.
Original source developer announcement