Legendary User rank issues and a possible suggestion #1347

New Issue

MrUnknownDE · 2026-04-05T17:27:12+02:00

MrUnknownDE commented

2026-04-05 17:27:12 +02:00

Originally created by @affectioned on 6/29/2021

The Issue

I've recently noticed that vrcx can show some people who haven't even reached "system_trust_legend" or a "Veteran User" rank for short as a "Legendary User" since I assume you only check for a string "system_legend" in tags[] array to determine if a user is "legendary".

This finding came to me when I've used in game boolean to determine if user has a legendary rank (Veteran User) + "system_legend" tag and noticed that one of my friends doesn't meet this criteria,

but they're being shown as a legendary user on VRCX.

The Suggestion

Making the requirements for "Legendary User" more stricter like in this case above, checking for other tags for example like this:

if (user.tags.Contains("system_legend") && user.tags.Contains("system_trust_legend") && user.tags.Contains("system_trust_trusted"))
{
    return TrustRanks.Legendary;
}

I know this issue is little bit over too top since the game itself doesn't use "system_legend" at all and it's not even broadcasted through the APIUser class in game (meaning unless you manually fetch the user in game, you can't even see the tag). But since they still haven't removed these tags from people's accounts, probably because they were auto assigned to people when trust system was in development by the API itself. I think this would be quite the nice addition to it in overall.

*Originally created by @affectioned on 6/29/2021* ### <p align="center">The Issue</p> I've recently noticed that vrcx can show some people who haven't even reached "system_trust_legend" or a "Veteran User" rank for short as a "Legendary User" since I assume you only check for a string "system_legend" in tags[] array to determine if a user is "legendary". ![image](https://user-images.githubusercontent.com/61197745/123841831-55602300-d910-11eb-98d9-747f330cd760.png) This finding came to me when I've used in game boolean to determine if user has a legendary rank (Veteran User) + "system_legend" tag and noticed that one of my friends doesn't meet this criteria, ![image](https://user-images.githubusercontent.com/61197745/123841969-80e30d80-d910-11eb-866d-f17ec71bcea6.png) but they're being shown as a legendary user on VRCX. ![image](https://user-images.githubusercontent.com/61197745/123841999-88a2b200-d910-11eb-9bda-ea12dc1e1016.png) ### <p align="center">The Suggestion</p> Making the requirements for "Legendary User" more stricter like in this case above, checking for other tags for example like this: ```csharp if (user.tags.Contains("system_legend") && user.tags.Contains("system_trust_legend") && user.tags.Contains("system_trust_trusted")) { return TrustRanks.Legendary; } ``` > I know this issue is little bit over too top since the game itself doesn't use "system_legend" at all and it's not even broadcasted through the APIUser class in game (meaning unless you manually fetch the user in game, you can't even see the tag). But since they still haven't removed these tags from people's accounts, probably because they were auto assigned to people when trust system was in development by the API itself. I think this would be quite the nice addition to it in overall.

MrUnknownDE closed this issue

2026-04-05 17:27:12 +02:00

Sign in to join this conversation.

No Label Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done Done

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#1347