What the announcement changes
The post schedules a no-downtime update at 8:00 UTC+0. Once it has been deployed, players are required to update their game client through their platform’s store.
The listed changes cover season-task requirements, stacking behaviour for items in Pip’s Pouch, class and combat balance, tactical items, gem affixes, terrain collision, and task tracking. Several skill-related issues are also addressed in the supplied text.
Network handling is a major part of this update. The developer describes fixes for client/server disagreement around breakaway and recovery animations, added tolerance for certain dodge-follow-up attacks under unstable connections, and improved dodge-direction synchronization. AWS server storage is also moved from EFS to EBS to address rare long hitches attributed to log I/O write bottlenecks.
What it says about third-party software
The source does not identify the game by name. It addresses “Gyldhunters,” but the supplied announcement does not provide a game title. That means this post alone cannot be verified as an update for any specifically named game.
It contains no reference to an anti-cheat, detections, ban actions, account penalties, hardware-ID penalties, or checks for third-party tools. It also does not announce a changed protection component. Nothing in this announcement confirms either detection or non-detection of any software.
No product names, builds, release notes, or compatibility statements appear in the post. A patch note cannot establish whether a particular tool is updated for the new client build.
Run now or wait?
Update the client first, because the announcement explicitly requires it. After that, use the status and release information supplied by the developer of the tool you use. If there is no status for the new build, this announcement is not a substitute for one.
For checking product status, update policy, support, and requirements, see the cheat selection checklist. Before launching anything, review the safe launch checklist. It does not promise immunity from penalties; it is meant to help avoid basic user-side mistakes.
What is not in the post
There is no announced ban wave, no claim about enforcement against third-party software, and no anti-cheat update in the provided text. The balance changes, networking work, and storage migration are not described as affecting external software.
Likewise, a client error, crash, or version mismatch after the update should not be presented as evidence of a detection event: the source gives no such explanation. If a penalty has already occurred, use the separate what to do after a ban guide for practical next steps.
Original source developer announcement