[bottiger]

I never used that random Steam3 fix provided by that other person which is probably why you have 2 entries per player as it allows your hlstats to receive both Steam2 and Steam3 ids. My fix only allows you to receive Steam3 and requires you to convert everything to Steam3 in the database which prevents all possible problems that you see now.

We also don't use the hlstats sourcemod plugin which is probably sending Steam2. You probably need to edit the plugin to correct this. Please don't ask me for help with this though because we are never going to use it.

Also I was about to answer you on IRC but you left.

[Sarabveer]

Originally Posted by bottiger I never used that random Steam3 fix provided by that other person which is probably why you have 2 entries per player as it allows your hlstats to receive both Steam2 and Steam3 ids. My fix only allows you to receive Steam3 and requires you to convert everything to Steam3 in the database which prevents all possible problems that you see now. We also don't use the hlstats sourcemod plugin which is probably sending Steam2. You probably need to edit the plugin to correct this. Please don't ask me for help with this though because we are never going to use it. Also I was about to answer you on IRC but you left.

I'm talking about this one.

Originally Posted by bottiger You can update hlstats to use the new format internally by running this SQL command UPDATE hlstats_PlayerUniqueIds SET uniqueId=SUBSTR(uniqueId, 1, 1)+SUBSTR(uniqueId, 3)*2 WHERE uniqueId REGEXP('[01]:[0-9]+') And replacing the $uniqueid in hlstats.pl sub getPlayerInfo with this. $uniqueid =~ /^\[U:1:(\d+)\]/; $uniqueid = $1; There are few other cosmetic changes such as searching and player display which shouldn't be too difficult to figure out and I am sure the hlstats team will do.

EDIT: After re-install, and removing the superlogs plugin. It's fixed!

[delidolu1genc]

Persons experiencing the same problem. Try the files on the bottom.

[Sarabveer]

Originally Posted by delidolu1genc Persons experiencing the same problem. Try the files on the bottom.

Nice job, using the WRONG fix.

https://forums.alliedmods.net/showpo...2&postcount=17

Your supposed to use that one.

[FallenNT]

I run this script

UPDATE hlstats_PlayerUniqueIds SET uniqueId=SUBSTR(uniqueId, 1, 1)+SUBSTR(uniqueId, 3)*2 WHERE uniqueId REGEXP('[01]:[0-9]+')

Now all STEAM ID in the statistics of the players have become completely different, ie, in general, all the figures were replaced by ...

Can anybody help me to return everything back as it was standard or suggest what you can do everything in the script returns the standard values? Well, or cure it somehow.

[DarkDeviL]

Originally Posted by FallenNT I run this script UPDATE hlstats_PlayerUniqueIds SET uniqueId=SUBSTR(uniqueId, 1, 1)+SUBSTR(uniqueId, 3)*2 WHERE uniqueId REGEXP('[01]:[0-9]+') Now all STEAM ID in the statistics of the players have become completely different, ie, in general, all the figures were replaced by ... Can anybody help me to return everything back as it was standard or suggest what you can do everything in the script returns the standard values? Well, or cure it somehow.

"replaced by ..." doesn't really make any sense. Does the table show the new values as "..." or what exactly do you mean there?

Anyway -

Account ID: 4691
Steam ID : STEAM_0:1:2345
Steam 3 : [U:1:4691]
SteamID64 : 76561197960270419

Standard on my installation for STEAM_0:1:2345 is to have the uniqueId as "1:2345" in this specific example.

My installation seems return the account id "4691" with your query above, so assuming this is also what happened in your case - you should simply half all the values (without decimals), and then add "0:" in front of it for the full numbers, or "1:" if the it was a half number.

CONCAT(IF(((4691 / 2) % 1) > 0, 1, 0), ":", TRUNCATE((4691 / 2), 0))

returns "1:2345"

A query like this should return all the previous converted ones back to the standard of "1:2345" format:

UPDATE hlstats_PlayerUniqueIds SET uniqueId=CONCAT(IF(((uniqueId / 2) % 1) > 0, 1, 0), ":", TRUNCATE((uniqueId / 2), 0)) WHERE uniqueId REGEXP("^[0-9]{1,}$")

NOTE: This query doesn't take account for anything which happened to your database from the time you made the above query, and until the time this query is executed. So if you left your statistics running after this "mess up" was made, you may have some players which technically exists multiple times (one for the old format, one for the new).
In order to fix that, you will have to go manually through the bogus ones to remove them.

Without providing a guarantee - I still hope that this will help you to get most of it back to normal.

[FallenNT]

When I tried to run a query

UPDATE hlstats_PlayerUniqueIds SET uniqueId=CONCAT(IF(((4691 / 2) % 1) > 0, 1, 0), ":", TRUNCATE((4691 / 2), 0)) WHERE uniqueId REGEXP("^[0-9]{1,}$")

I received a response from the database

#1062 - Duplicate entry '1:2345-css' for key 'PRIMARY'

[DarkDeviL]

Originally Posted by arne1288 Anyway - Account ID: 4691 Steam ID : STEAM_0:1:2345 Steam 3 : [U:1:4691] SteamID64 : 76561197960270419 Standard on my installation for STEAM_0:1:2345 is to have the uniqueId as "1:2345" in this specific example. My installation seems return the account id "4691" with your query above, so assuming this is also what happened in your case - you should simply half all the values (without decimals), and then add "0:" in front of it for the full numbers, or "1:" if the it was a half number. CONCAT(IF(((4691 / 2) % 1) > 0, 1, 0), ":", TRUNCATE((4691 / 2), 0)) returns "1:2345"

Here you got an explanation on how things can be calculated with that specific "example Steam ID".

Originally Posted by arne1288 A query like this should return all the previous converted ones back to the standard of "1:2345" format: UPDATE hlstats_PlayerUniqueIds SET uniqueId=CONCAT(IF(((uniqueId / 2) % 1) > 0, 1, 0), ":", TRUNCATE((uniqueId / 2), 0)) WHERE uniqueId REGEXP("^[0-9]{1,}$") NOTE: [...]

There you were spoon-fed with the exact query to run.... A thing which is actually very rare on the Internet...

Originally Posted by FallenNT When I tried to run a query UPDATE hlstats_PlayerUniqueIds SET uniqueId=CONCAT(IF(((4691 / 2) % 1) > 0, 1, 0), ":", TRUNCATE((4691 / 2), 0)) WHERE uniqueId REGEXP("^[0-9]{1,}$") I received a response from the database #1062 - Duplicate entry '1:2345-css' for key 'PRIMARY'

You were spoon-fed with the exact query that would have adjusted everything for you at once, and still you choose to MODIFY the query before you run it. Why exactly can't you follow the statements exactly?

If you're unable to follow the exact statements you're given, no one will ever be able to help you.

Since you choose rewrote the query first, it caused the first row of the hlstats_PlayerUniqueIds table to be rewritten, thereby destroying the user on the first row (unless you have backup, or know what ID was there, ... etc).

[BatyaMedic]

SteamID`s in my stats looks like STEAM_0:[U:1:108244334]
What fix i should use?

[Horsedick]

Originally Posted by Sarabveer I'm talking about this one. EDIT: After re-install, and removing the superlogs plugin. It's fixed!

I do believe I have this same issue cept removing superlogs isn't something I can do mostly since I need superlogs to be present for HLSW to log properly so at this point I'm damned if I do and damned if I don't. Know of a fix that doesn't include removing superlogs to prevent the doubled up users in the DB?