Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for MineSkin-Skins
See original GitHub issueIs your feature request related to a problem? Please describe. I think having the possibility to set a skin from MineSkin using the built-in commands would be a great addition
Describe the solution you’d like It could be achieved with an additional command accepting a Skin-ID (URL too?) to automatically fetch the required texture data.
Allowing for the existing skin-command might be achieved using a prefix like ms: or mineskin: (e.g. /skin mineskin:1778270885 Sprax2013). But this might need a way to escape the prefix in case somebody wants to call themselves that way (I think NickNamer does not validate for valid username?)
Describe alternatives you’ve considered The current alternative is creating an own plugin with its own command.
Additional context
This is a feature that I thought of after MrMaurice211#2546 and Mus#8007 on your Discord asked a related question where this feature could have helped them.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It’s an idea and still relevant 😦
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.