next »

[fistfight]

Just thinking out loud here.

What if a player connects to a server for the very first time and his pbguid gets recorded as a 32 digit number. Then he connects again but his pbguid is only 31 digits long.

Normaly this would cause a dual entry for this player. But what if there was an xlr_pbalias table and when this person connected the second time there was a check to see what the closest match to his pbguid was and if one was found that was no more than 1 digit off the new pbguid was registered as an alias to his first one.

This could work both ways. Say he connects the very first time and his pbguid is only 31 digits long. A check could be done to find a pbguid that was no more than 1 digit off and then aliased the same way.

I know the pbguid is used as the unique identifier on B3 so the first pbguid that was recorded (even if its only 31 digits long) could be used as the unique identifier and all subsequent connections whether 32 or 31 digits long would be the aliases

Could something like this be done to fix this issue?

If so is there anyone here that is willing to look into doing it. I dont have the skills to create this check. But I'd be willing to help out how I can.

[Bakes]

That would be quite clever.
I see you're already suggesting that xlr8or should do it

[fistfight]

You caught that table name huh?


to be honest I've just been working with xlrstats a lot lately and guess it was just a slip.