I recently installed Minecraft java edition after a year or 2 witout playing and i didn't had my skin on so i got a new one from NameMC when i joined single player i noticed that i still had steve skin and so i thought that it might be a bug so i made my research on what i could do to fix the bug, turns out i am here so... nothing worked yea '-' i still got my steve skin so i joined a server that i used to play long time ago LoverFella's Server and i asked around if someone could see my skin or if i was a steve turns out they can see my skin but i can't see other people skins and my own i don't know what to do a guy said for me to unistall "Premier Opinion" and another Program starting with the Letter R cause he said that both that programs mess up with the skins but i don't have any of those on my Pc.
P.S- Everytime i create a new world in any version a new skin folder is made in the skin folder that only creates another steve skin even if i select alex on my game i become a steve.
Linked issues
duplicates 1
Attachments
Comments
Avoma
That most be the problem i have installed one of the software on the list i will see what i can do to fix it thank you
Arisa Bot
Thank you for your report!
We're tracking this issue in MC-101579, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicate of MC-101579, which was later resolved as invalid. The reason for this is because this issue is most likely caused by malware or other software that is interfering with Minecraft. Please see the Moderator Note attached to the parent ticket to potentially fix this issue.