The First Descendant’s developers have posted an enforcement summary covering 7–13 August 2026 (PDT). Reports like this are the most reliable public window into how the game actually catches rule-breakers. This time the split between hard and soft punishments is the story.
The numbers
- Creating, distributing or using unauthorized programs — permanent account ban, 2 players.
- Abusing Open Store processes — permanent ban, 9 players, for unfair gains obtained through the store payment flow.
- Abnormal transactions — 7-day trading restriction, 2 players.
- Unusual gameplay activity / uncooperative play — separate matchmaking penalty applied to 273 accounts.
The announcement also repeats the standard reminder to use the in-game report tool when something looks off.
Reading the ratio
The list of masked nicknames matters less than the proportions behind it. Two accounts closed for third-party programs against 273 hit with a matchmaking penalty is not, on its own, proof of anything — but it reads more like enforcement driven by player reports and match telemetry than like a broad signature sweep.
The matchmaking penalty is also the vaguest line in the report. The announcement does not spell out what it actually changes for an account; it only says the measure follows operational policy and was applied for unusual activity and records of uncooperative play. That wording is broad enough to cover idling through group content as well as behaviour that raised suspicion without being confirmed as software use. For a player, the practical value is as a warning sign: if your lobby quality and the people you get grouped with change abruptly, a flag may already be sitting on the account.
Worth noting too that the largest permanent-ban bucket has nothing to do with cheats. Nine accounts were wiped for exploiting the Open Store payment process, which suggests the publisher treats monetisation abuse far more aggressively than gameplay infractions.
What this means for players using software
Nothing in this announcement touches the client. It is a report, not a build, so offsets, structures and existing builds are unaffected — there is no reason to reinstall or wait for a rebuild off the back of it. Checking the current state of your build before a session is still sensible: current statuses live on the software update statuses page, and the builds we carry for this title are listed on the The First Descendant page.
The more useful takeaway concerns behaviour. In this title, visibility looks like the bigger risk factor than detection. Two software-related entries against 273 behavioural flags in a single week describes a system that leans heavily on reports and match statistics. That translates into practical discipline: keep public runs boring, avoid inhuman flick patterns, do not walk obvious ESP lines through empty rooms, and stay away from clear times and damage numbers that beg for a review. Tuning your configuration per activity beats running a maxed-out preset everywhere.
For unauthorized programs the report lists a permanent account ban, and it says nothing about routes to reversal — so it makes sense to size your exposure by whatever time and money the account holds. If you rotate spare profiles, isolate them properly: a clean hardware fingerprint and an HWID spoofer reduce the odds of one flagged account dragging the rest down with it. Finally, these summaries cover a period that has already closed, so penalties land after the fact and a week of trouble-free play proves nothing about whether you were logged.
Dominate The First Descendant with our software
Verified cheats and software — updates within 12–48 hours after major patches, with guarantees and 24/7 support.