-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to a different ID format #272
Comments
If it was a new addon, it'd make sense, however, since it's been this way since it was created, doing this would result in mass data loss for those who upgrade. |
Probably an easy way to maintain backwards compatibility, pretty good
suggestion - I'll accept any PR that adds it with good backwards
compatibility.
…On 18 Feb 2017 1:28 pm, "Michael" ***@***.***> wrote:
If it was a new addon, it'd make sense, however, since it's been this way
since it was created, doing this would result in mass data loss for those
who upgrade.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#272 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUu69-_y6pxKVyMjIubVa0MFS51qVnPks5rdvH2gaJpZM4MFBge>
.
|
Once I get some time, I'll modify the storage methods to support SteamID, as well as be backwards compatable with UniqueID. |
If any of you guys have a server you can help test on, I've got a version that should work. Just add me on Steam. |
There is also account id, which is 32bit size. http://wiki.garrysmod.com/page/Player/AccountID |
Gmod's documentation recommends that you do not use Player:UniqueID(), as it may possibly cause collisions between players and therefore break the addon. While this is extremely rare, it is probably best practice to migrate to something safer like Player:SteamID64().
The text was updated successfully, but these errors were encountered: