Xash3D

[GLoOoccK]

Players using Xash3D are currently being identified by the module as NextClient-compatible users.

L 05/29/2026 - 07:56:49: [nclapi] NextClient compatible user [Xash3D]kuroshi hoshiro has joined the game (2.4.0)!
L 05/29/2026 - 09:07:03: [nclapi] NextClient compatible user [Xash3D]cs1.6android has joined the game (2.4.0)!
L 05/29/2026 - 09:50:58: [nclapi] NextClient compatible user [Xash3D]androidoyunclub has joined the game (2.4.0)!
L 05/29/2026 - 10:08:32: [nclapi] NextClient compatible user [Xash3D]?? has joined the game (2.4.0)!

[Polarhigh]

In which version of the module does this occur?

[Polarhigh]

I’m looking at the code, and it’s hard to believe this is some kind of bug rather than a certain build or something, that sends a request saying it’s a NextClient compatible user

[GLoOoccK]

In which version of the module does this occur?

v1.5.1

[Polarhigh]

Overall, this does not look like a module issue. There are two possible explanations:

1. These are not Xash3D players, but for some reason their nicknames use the [Xash3D] prefix.
2. Someone modified Xash and added NextClient compatible authentication to their build. "NextClient compatible user" specifically means that the player does not necessarily use NextClient. It is also a declaration that the client supports the features of the version it reports

[GLoOoccK]

I'm on a clean installation, and it keeps trying to send data from NextClientServerApi to Xash3D. I'm not sure why this is happening.

[Polarhigh]

Got it, thanks for the info. I'll check what's causing it