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
I am writing to suggest a feature related to Cloaks. My suggestion is the following:
Feature Summary:
Introduce the ability to add custom cloak images to player renders, enhancing the visual customisation and engagement for users on platforms like Discord and Minecraft related websites. This feature would allow users to submit a custom image via a URL or a locally cached asset.
Feature Preferred Implementation:
POST /{mode}/{playerId}/cloak
Content-Type: multipart/form-data or Content-Type: application/json
{
"cloakUrl": "http://optifine.net/capes/{playerName}.png", // Preferred method
"cloakImage": (binary image data) // Used mainly for testing
}
The text was updated successfully, but these errors were encountered:
Hey there, thank you for reaching out with a feature request!
Although not documented yet as I've not had the time to do so, NMSR does support rendering with custom textures by doing a multipart/form-data POST form request to /{mode}.
For a custom skin, use skin or texture as the field name, and for the cloak use cape for the name. Both need to be binary data with a PNG image.
These custom POST requests support all the normal parameters, although instead of using them as query parameters, you instead need to send them along as multipart fields.
Please let me know if the existing functionality serves your purposes, or if something else needs to be implemented.
Hello,
I am writing to suggest a feature related to Cloaks. My suggestion is the following:
Feature Summary:
Introduce the ability to add custom cloak images to player renders, enhancing the visual customisation and engagement for users on platforms like Discord and Minecraft related websites. This feature would allow users to submit a custom image via a URL or a locally cached asset.
Feature Preferred Implementation:
The text was updated successfully, but these errors were encountered: