If someone has a badge awarded for winning the MMC their badge will be named something along the lines of 1st place (including the space bar at the beginning). Additionally if someone has two mmc badges with the same rank, the 2nd badge will be called something along the lines of 1st place 1st place(2).
To Reproduce
Find someone with two MMC badges of the same "rank" (hard part)
Inspect their badges and look at the names
Expected behavior
The badges should be called something along the lines of MMC World 1st place, and having multiple should correctly add the (2) at the end, instead of repeating the rank again.
Screenshots
I have a mod that generates a few mmc badges to demonstrate this bug.
Resonite Version Number
2023.10.20.831
What Platforms does this occur on?
Windows, Linux, Android / Quest
What headset if any do you use?
No response
Log Files
I can't really replicate the issue without a mod right now, because I can't find anyone online who has two mmc winner badges, but it's a logic bug rather than some kind of unhandled exception so it won't really generate anything useful inside the log.
Describe the bug?
If someone has a badge awarded for winning the MMC their badge will be named something along the lines of
1st place
(including the space bar at the beginning). Additionally if someone has two mmc badges with the same rank, the 2nd badge will be called something along the lines of1st place 1st place(2)
.To Reproduce
Expected behavior
The badges should be called something along the lines of
MMC World 1st place
, and having multiple should correctly add the (2) at the end, instead of repeating the rank again.Screenshots
I have a mod that generates a few mmc badges to demonstrate this bug.
Resonite Version Number
2023.10.20.831
What Platforms does this occur on?
Windows, Linux, Android / Quest
What headset if any do you use?
No response
Log Files
I can't really replicate the issue without a mod right now, because I can't find anyone online who has two mmc winner badges, but it's a logic bug rather than some kind of unhandled exception so it won't really generate anything useful inside the log.
Additional Context
No response
Reporters
No response