Offline
When players join servers, the server side will receive a string(value maybe) said to be clientdata.
My questions is: is it possible to fetch this string?
Forum
CS2D
Scripts Clientdata String
Clientdata String
16 replies
1 
When players join servers, the server side will receive a string(value maybe) said to be clientdata.
My questions is: is it possible to fetch this string?
Additional Parameter 'HASH' to Player() (8) 
Evaldas: It's basically a hash of the binary (exe). It was implemented a long time ago to detected manipulated binaries. Everybody who uses cheats and hacks is commonly a clueless stupid Windows user (no offense. I like Windows users. I just hate little cheating idiots) so there is no need to care about Linux clients at all.Actually I think on Linux it failed because it couldn't access the binary while it's running or something like that. I don't remember but I also don't care because of what I just explained.
@
Talented Doge: This value isn't saved anywhere. It is received once and printed out. That's it. So yes, the easiest/best way is to get it from the logs I guess. I really wonder for what you need this value anyway? DC: If this string can be used to distinguish an unique client, I will probably use it for advanced banning. Now I know that this string can be fetched through logs, is this string generated for a client permanently or generated randomly per start/join? Talented Doge Talented Doge: No it can't be used this way. It's the same for each Windows client with the latest version. So it's a very bad idea to use it for perm bans... 
Talented Doge: This stuff can be manipulated very easily. Guess why there is the U.S.G.N. account system? Use it. There is no doubt that it is the most reliable and secure approach to identify players available in CS2D. DC: You said that it's basically a hash of the binary but after a change some strings in *.exe (md5 hash has been changed) this hash is same huh?Anyways I'm a little bit shocked cuz in logs are three types of this kind of hash:
|Storm_PL| ~Hajt clientdata: WIN {28cefe3ac30ab30ab5268978955263db2916352}
eXXaLTeD ' Tonic clientdata: WIN {28cefe3ac30ab30ab5268978955263db-1}
Cr++ * PtSw @mp3 clientdata: WIN {28cefe3ac30ab30ab5268978955263db2990080}
Hajt has writtenAnyways I'm a little bit shocked cuz in logs are three types of this kind of hash:
|Storm_PL| ~Hajt clientdata: WIN {28cefe3ac30ab30ab5268978955263db2916352}
eXXaLTeD ' Tonic clientdata: WIN {28cefe3ac30ab30ab5268978955263db-1}
Cr++ * PtSw @mp3 clientdata: WIN {28cefe3ac30ab30ab5268978955263db2990080}
|Storm_PL| ~Hajt clientdata: WIN {28cefe3ac30ab30ab5268978955263db2916352}
eXXaLTeD ' Tonic clientdata: WIN {28cefe3ac30ab30ab5268978955263db-1}
Cr++ * PtSw @mp3 clientdata: WIN {28cefe3ac30ab30ab5268978955263db2990080}
So, there are 3 cases.
1. |Storm_PL| ~Hajt clientdata: WIN {28cefe3ac30ab30ab5268978955263db2916352}
2. eXXaLTeD ' Tonic clientdata: WIN {28cefe3ac30ab30ab5268978955263db-1}
3. Cr++ * PtSw @mp3 clientdata: WIN {28cefe3ac30ab30ab5268978955263db2990080}
Notice the bolded hash. There's only 1 hash in there.
28 ce fe 3a c3 0a b3 0a b5 26 89 78 95 52 63 db
The next value looks like a random number (case 1 and 3), but maybe -1 for people that doesn't logged in (case 2).
MikuAuahDark: Thank you for answer. It's not a random number hmm have a look at this.@
DC: Can you explain more detail about clientdata? What's mean these not bolded values? I should ban players who used the suspect clientdata? From what I see it's an entirely useless and unreliable value (at least in the latest versions). It's a very bad idea to use this value for anything. I highly recommend to fully ignore it.
1