Skip to content

2.1.0

Choose a tag to compare

View all tags
@wallenjos01 wallenjos01 released this 17 Aug 23:26
· 17 commits to master since this release
v2.1.0
8f79798

General:

  • The API has been refactored slightly to be more consistent
  • Internal changes have been made to work with MidnightCore beta 7
  • A Spanish translation has been added
    • Note: this is likely not 100% accurate
  • The plugin has been thoroughly tested on Spigot versions 1.8.8, 1.9.4, 1.10.2, 1.11.2, 1.12.2, 1.13.2, 1.14.4, 1.15.2, 1.16.5, and 1.17.1.
  • This version requires MidnightCore beta 7: https://github.com/M1dnightNinja/MidnightCore/releases/tag/v1.0.0-beta7

Configuration

  • New optional parameters can now be added to skin objects in the config, including:
    • name: The display name of the skin for the default GUI item, can be formatted as JSON or plaintext with color codes
    • item: If this is specified, the GUI will use this item instead of generating a head with the skin. Items are formatted as follows:
      • type: The material of the item
      • amount: The amount to have (optional, defaults to 1)
      • tag: The NBT tag to be added to the item, formatted as a config section. (optional)
      • name: The display name of the item. (optional, will use the NBT tag if not present)
      • lore: The lore give the item, formatted as a list. (optional, will use the NBT tag if not present)
    • groups: A list of strings representing which groups the skin belongs to
    • in_random: A boolean specifying whether or not the skin will appear in the /skin setrandom command. Defaults to true

Commands:

  • The /skin setrandom command has been added. This will give the targets specified a random skin
    • Optionally, you can specify a group as a parameter to this command in the format /skin setrandom <group>
    • If a group is specified, only skins which have that group will be selected
  • The /skin set command will now open a GUI of all the skins the player has access to if no skin is specified.
  • The /skin head command has been added, allowing you to generate a player head with the saved skin you specify and give it to players
    • Usage: /skin head <skin> <player>
  • The /skin edit command has been added, allowing saved skin metadata to be edited in-game
    • There are 4 subcommands: name, groups, item, and excludeInRandom
      • Using /skin edit <skin> name <name> will change the saved skin's display name in the GUI. RGB values, color codes, and raw JSON formatting are all supported.
      • Using /skin edit <skin> groups add <group> or /skin edit <skin> groups remove <group> will add or remove a group name from the skin, respectively.
      • Using /skin edit <skin> item save will save the item you are holding as the skin's display item for the GUI
      • Using /skin edit <skin> item clear will reset the item to being a head with the skin applied.
      • Using /skin edit <skin> excludeInRandom <true/false> will enable or disable the skin from showing up in /skin setrandom

Permissions

  • In order to use skins, players will now need permissions to access them.
    • Accessing a single skin: skinsetter.skin.{skin id}
    • Accessing a group of skins: skinsetter.group.{group name}
  • The permission skinsetter.command.set will now only let players access saved skins that they have been given permission to access.
  • The permission skinsetter.command.set.online is now required for players to access online skins
Assets 4
Loading