UCL improvements #99
Open
UCL improvements #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A couple uses of UniqueID in functions have been kept for backwards compatibility, but honestly I'm not sure if those need to remain either
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: This change also requires the matching ULX pull request to avoid breakage: TeamUlysses/ulx#226
This PR has two main changes that impact UCL:
ucl.updateClientUCLPlayer( id, data )anducl.updateClientUCLGroup( name, data )ucl.authednow uses SteamID64 internally instead of UniqueIDTested both in a local server and on a public server for a couple weeks now with no regressions found.