Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
VRChat's API will stop providing username to users soon
See original GitHub issueThe VRChat API will stop providing the username field to API users soon. We expect this change to happen within the next 1-2 weeks.
Please ensure VRCX is not using the username field for anything vital, such as keying. Instead, you should utilize id as the primary user key, as it is guaranteed to be unique and always point at the same user, no matter what they’re named.
I have not looked at VRCX’s code or how it handles this data. There may be no action required.
Issue Analytics
- State:
- Created a year ago
- Reactions:54
- Comments:32 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Some clarifications as requested:
Users will still be able to see their own usernames, for now. I wouldn’t rely on this being present forever.
The
users/{username}/nameendpoint will be going away, yes.This is being deployed right now.