[CONCEPT] feature: adding support for --static param when using /npc skin #137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
THIS IS MAINLY FOR DISCUSSION TO FIND BEST SOLUTION
📋 Description
Please include a summary of the changes and the related issue(s).
What is this PR solving? Why is it needed?
This isn't so much a need but could be considered a big QOL update. The drafted code is far from the final code I'd think would be viable but this build opens up conversation to be had.
✅ Checklist
Fixes #issue_numberorCloses #issue_numbermainbranch🔍 Changes
Please provide a brief summary of the changes made in this PR.
The end goal of this PR is to find a good and viable solution for static skins to be applied to NPC's without the need to have to manually download skins from websites such as namemc. Using the native Mojang and MineSkin handlers found in FancyNPCs, I am downloading the skin of the user and applying there skin from the local file to provide a static enviroment.
🧪 How to Test
Please describe how to manually test the changes made in this PR.
/npc skin <npc> <name> --static