skins.minecraft.net/MinecraftSkins redirects to cape when no skin exists
This isn't a "New Feature" request, but I can't select anything else - sorry for that.
Description:
Whenever a user has no skin but does have a cape,
http://skins.minecraft.net/MinecraftSkins/<username>
redirects to the cape instead of returning a 404.
For users with no skin and no cape, a 404 is returned.
For users with a skin, it redirects to the proper skin texture.
Reproducing
Find a player that has no skin but still has a cape.
Details
I know that I can get the proper skin (i.e. no skin) when I know the UUID, but we're using skins.minecraft.net to avoid additional HTTP requests
I also posted some details and a possible explanation of the bug here: https://github.com/Jake0oo0/crafatar/issues/44
Created Issue:
MCAPI-1105
skins.minecraft.net/MinecraftSkins redirects to cape when no skin exists
This isn't a "New Feature" request, but I can't select anything else - sorry for that.
Description:
Whenever a user has no skin but does have a cape,
http://skins.minecraft.net/MinecraftSkins/<username>redirects to the cape instead of returning a 404.
For users with no skin and no cape, a 404 is returned.
For users with a skin, it redirects to the proper skin texture.Reproducing
Try any of these usernames:
- Mr_Diomond_Gold
- WKM1
- BLWON
- matt4creeper
- Ophyte
Details
I know that I can get the proper skin (i.e. no skin) when I know the UUID, but we're using skins.minecraft.net to avoid additional HTTP requests
I also posted some details and a possible explanation of the bug here: https://github.com/Jake0oo0/crafatar/issues/44
NormalThis isn't a "New Feature" request, but I can't select anything else - sorry for that.
Description:
Whenever a user has no skin but does have a cape,
http://skins.minecraft.net/MinecraftSkins/<username>redirects to the cape instead of returning a 404.
For users with no skin and no cape, a 404 is returned.
For users with a skin, it redirects to the proper skin texture.Reproducing
Try any of these usernames:
- Mr_Diomond_Gold
- WKM1
- BLWON
- matt4creeper
- Ophyte
Details
I know that I can get the proper skin (i.e. no skin) when I know the UUID, but we're using skins.minecraft.net to avoid additional HTTP requests
I also posted some details and a possible explanation of the bug here: https://github.com/Jake0oo0/crafatar/issues/44
This isn't a "New Feature" request, but I can't select anything else - sorry for that.
Description:
Whenever a user has no skin but does have a cape,
http://skins.minecraft.net/MinecraftSkins/<username>redirects to the cape instead of returning a 404.
For users with no skin and no cape, a 404 is returned.
For users with a skin, it redirects to the proper skin texture.Reproducing
Find a player that has no skin but still has a cape.
Details
I know that I can get the proper skin (i.e. no skin) when I know the UUID, but we're using skins.minecraft.net to avoid additional HTTP requests
I also posted some details and a possible explanation of the bug here: https://github.com/Jake0oo0/crafatar/issues/44
MCAPI-1105 → 
MC-75346![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
MC-75346 → 
WEB-14![[Mojang] Web Team](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Web Team
Please note that the usernames mentioned above can no longer be used to reproduce the bug. They only had a cape due to the scrolls launch.
You'll need to find a player that has no skin but still has a cape to reproduce.
@mustek are you a developer? Do you have confirmation from Mojang that this has been fixed?
Edit: didn't see the "invalid" - why is this invalid?
Okay, ezekiel explained that this bug was related only to the temporary scrolls-launch capes and other capes are not affected.
That doesn't explain why this is marked as invalid though.
Thanks for moving @kumasasa.
I'm not sure if this should stay open or not.
The bug is gone by the fact that the scrolls-capes were only used for a day.
I wonder if this bug will re-appear when a similar event (maybe christmas capes?) comes.
Perhaps it's best to let someone from Mojang have a look?
Mojang is informed and aware about this issue.
Mojang confirmed it is fixed now.