💡Future Updates
Our Values
What still needs to be implemented in the plugin
🚀 Updates #1
Outfits, (save-load) with GUI integration to save them on a GUI and load the active overlays of that outfit, clearing the previous/clothes overlays completely before applying the outfit. (Added the basic integration for this without the GUIs)
Character-Creating Session (not-so-important right now), but it basically lets the player customize their full character through a GUI (Skin-colour, eye-color, hair-color, eyebrow-color, default clothes), whilst the generic GUIs, aka the ones they usually will be using, will not let them change their hair, eyes, eyebrows or skin-color unless they have a token to change their base-character.
GUIs overall… I think that using CommandsPanelAPI would be better due to its extended web editor and more. It has pretty much most basics on it and integrating a compatibility/dependency on it would be better than building a full new GUI system for everything.
🚀 Updates #2
Needed GUIs #1 :
Base-Character (Skin-Colour, Eyes, Eyebrows, Hair, Tattoos, Scars, Mouth), 2. Clothes (Shoes, Accessories, Shirts, Jackets, Pants), 3. Misc (Beards)
🚀 Updates #3
Needed GUIs #2:
[Owned Overlays] (Displays the overlays they have permissions to and let’s them add them through right click onto their current skin),
[Currently Wearing] (Shows their current active overlays, letting them remove through right click.),
[Online-Shops] (Shows all the overlays they don’t own and sets up a default price, and let’s the plugin users define the pricing through shop-gui config.),
[Outfits] (Let’s them save and load outfits, loading by left click, and saving from right click when an empty slot is clicked, and right clicking on existing outfits delete the existing outfit, it should save the overlays list of the YAML file, and upload them back on so the player can remove/add onto their current overlays after loading the outfit)
Last updated