You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this plugin, adds the ability to change the skin directly on the server, but with this mod skin remains the same as it was, in the CustomSkinLoader log when changing the skin through the plugin, it says that he is looking for a skin on my usual nickname, although I entered in the plugin another, you need to make CustomSkinLoader to get the skin on the nickname, which gives the plugin SkinsRestorer
Before submitting a suggestion
This feature doesn't already exist in the client. (I have checked every module and their settings on the latest dev build)
This wasn't already suggested. (I have searched suggestions on GitHub and read the FAQ)
The text was updated successfully, but these errors were encountered:
Parsing the skin texture information sent from the server is a MojangAPI task, so if you want to parse the skins set by the SkinRestorer plugin, you should elevate MojangAPI to the first place in the configuration file.
Parsing the skin texture information sent from the server is a MojangAPI task, so if you want to parse the skins set by the SkinRestorer plugin, you should elevate MojangAPI to the first place in the configuration file.
Describe the feature
this plugin, adds the ability to change the skin directly on the server, but with this mod skin remains the same as it was, in the CustomSkinLoader log when changing the skin through the plugin, it says that he is looking for a skin on my usual nickname, although I entered in the plugin another, you need to make CustomSkinLoader to get the skin on the nickname, which gives the plugin SkinsRestorer
Before submitting a suggestion
This feature doesn't already exist in the client. (I have checked every module and their settings on the latest dev build)
This wasn't already suggested. (I have searched suggestions on GitHub and read the FAQ)
The text was updated successfully, but these errors were encountered: