Saving players info by steam id in Xash3D FWGS new engine.

[MWiyPower]

A serious problem with the engine is this: In mod servers, user information (such as ammopack, lvl) is stored using the setam id, but it is not stored in xash3d. I think the problem is the continuous change of steam id in the engine. Please follow up as soon as possible. Thanks to the developer.

[MWiyPower]

This problem happend to me in dp server

[MWiyPower]

Is not fixed yet

[a1batross]

Can you provide some examples?

Preferably, the IP addresses of the servers and the platform you're playing on.

[MWiyPower]

Can you provide some examples?

Preferably, the IP addresses of the servers and the platform you're playing on.

Of course
Ip: 213.238.173.68:27015 (zombie plague 4.3(ZE edition)

Android 12 SMA21s

[MWiyPower]

Can you provide some examples?

Preferably, the IP addresses of the servers and the platform you're playing on.

Of curse
Ip: 213.238.173.68:27015 (zombie plague 4.3(ZE edition)

Android 12 SMA21s

In this server
Level, XP, cp(ammopack) or any infos must save
But it not

[anzz1]

The way id generation is handled in Xash is atrocious. You are supposed to send a ticket with just zeroes or other random content so the server on the other side knows you do not have unique ID and to assign you ID by IP (or block from joining if the server owner so wishes), but Xash pretends to have unique ID while in reality making a randomized one, breaking the integrity of the whole system.
I cannot fathom how somebody ever thought it was okay to do it like this. Yes of course you could argue that it was dumb to create such auth system based on trust that no one would destroy it, and something like this was ultimately inevitable.
But still a project that I think at least presents itself as force of good, doing such thing, is very unfortunate.

[a1batross]

I don't really care what pirates think.

[MWiyPower]

The way id generation is handled in Xash is atrocious. You are supposed to send a ticket with just zeroes or other random content so the server on the other side knows you do not have unique ID and to assign you ID by IP (or block from joining if the server owner so wishes), but Xash pretends to have unique ID while in reality making a randomized one, breaking the integrity of the whole system.
I cannot fathom how somebody ever thought it was okay to do it like this. Yes of course you could argue that it was dumb to create such auth system based on trust that no one would destroy it, and something like this was ultimately inevitable.
But still a project that I think at least presents itself as force of good, doing such thing, is very unfortunate.

Why don't they fix it?

[MWiyPower]

I don't really care what pirates think.

So what's the problem? You must have tested it. You saw for yourself that there's a problem. Why don't you fix it?

[a1batross]

@MWiyPower that wasn't a reply to you.

[MWiyPower]

@MWiyPower that wasn't a reply to you.

That answer doesn't apply to me. I asked my own question.