Summary

Since DayZ 1.29, community server logs no longer contain the persistent device identifier that was previously available. Instead, every player is now logged with a generic device type such as unknown, console or desktop. This removed the only reliable way for console community server owners to identify ban evasion through alternate accounts.

The previous implementation may have conflicted with platform requirements, and it is understandable that it had to be removed. However, no functional replacement currently exists, leaving console server administrators without an effective moderation mechanism.

Problem

Community servers on console have very limited administration capabilities compared to PC.

Server owners do not have access to:

• Steam IDs

• IP bans

• server-side scripting

• advanced admin APIs

• any other persistent player identifier

As a result, a player who is banned can simply create a new platform account and immediately return to the server. Username-based bans are therefore largely ineffective.

This has significantly increased the amount of ban evasion, repeat griefing and moderation workload on community servers.

Why a persistent identifier is needed

Server owners do not need access to real hardware identifiers or any personally identifiable information.

The requirement is simply a stable identifier that:

• remains constant for the same player/device combination,

• cannot be reversed into hardware information,

• cannot be used to identify the real device,

• complies with platform privacy requirements.

A one-way hashed or encrypted identifier generated by the platform would fully satisfy this requirement.

Suggested solution

Introduce a new persistent moderation identifier instead of exposing hardware information.

For example:

• an irreversible hashed token

• a platform-generated moderation ID

• any other stable anonymous identifier

The identifier should:

• remain identical for the same player/device combination

• be different for different devices

• not expose any hardware information

• not be reversible

• be available in server logs and/or administration interfaces

Benefits

This would allow community server owners to:

• enforce bans against repeat offenders

• detect alternate accounts

• improve moderation quality

• automate moderation tools

• protect communities without compromising player privacy

Conclusion

The removal of the previous identifier is understandable if it conflicted with platform policies.

However, console community servers still require some form of persistent anonymous identifier to perform basic moderation tasks.

Without such an identifier, effective moderation is currently impossible, as there is no reliable way to distinguish legitimate new players from users repeatedly circumventing bans through alternate accounts.

A privacy-compliant, irreversible moderation identifier would solve this problem while respecting platform requirements.

1. Start a community server.

2. Let a player join.

3. Check the server logs.

4. Observe that no persistent anonymous identifier is available for moderation purposes.

if possible, try the same with enabled MAM protection on a pre-1.29 server - you'll see the device id logging

Community servers should have access to a persistent, anonymous player identifier that remains stable for the same player/device, cannot be reversed into hardware information, and can be used for moderation purposes. Ideally, this identifier should be available in both the RPT and ADM log files.