WaystonesPlus - [ 1.19.4 - 1.20.1 ] Featuring ✨BlockDisplays

Problem specified in title is now fixed.

Fixed some error messages, and fixed the issue, where any player could place a waystone on a (for example) world guard protected area

· Localization is now available to configure in localization.yml · /wsp reload command is now available · /wsp rename command is now available · /wsp setvisibility command is now available · Settings menu have been added: · Icon settings · Visibility settings · Explorers menu · Particle settings · Type settings · New, Explore mechanic had been added, public waystones can be unlocked by Exploring them manually · Titles for exploring, and placing down a new waystone have been added, as well as a sound effect · Some permissions now are enabled by default, for servers that does not have a permission manager · Storage have been migrated to SQLite instead of YAML · A countdown have been added when teleporting · A cooldown have been added to place waystone, and teleport, this is configurable is config.yml · New permissions: · waystonesplus.cooldown.teleport: · description: Remove the cooldown of teleporting to another waystone · default: false · waystonesplus.cooldown.placewaystone: · description: Remove the cooldown of placing another waystone · default: false · waystonesplus.countdown.teleport: · description: Remove the countdown before teleporting · default: false · waystonesplus.menu.visibility: · description: The player can now change the visibility settings · default: true · waystonesplus.menu.particle: · description: The player can now change the particle settings · default: true · waystonesplus.menu.explorers: · description: The player can now look at the explorers list · default: true · waystonesplus.menu.type: · description: The player can now change the type settings · default: true · waystonesplus.menu.icon: · description: The player can now change the icon settings · default: true · waystonesplus.menu.settings: · description: The player can now go into the waystone settings · default: true · waystonesplus.command.visibility: · description: Gives access to the /waystonesplus or /wsp visibility command · default: false · waystonesplus.command.rename: · description: Gives access to the /waystonesplus or /wsp rename command · default: false · waystonesplus.command.reload: · description: Gives access to the /waystonesplus or /wsp reload command · default: false Enjoy

Waystones.yml had a typo, I fixed it

Now if the server doesn't have a permission manager, the default permissions will apply Now there is a cooldown for waystone placement, and teleport, as well as a countdown for teleporting which can be cancelled on movement. New permissions: · waystonesplus.cooldown.teleport for bypassing the cooldown, default is 30 seconds · waystonesplus.countdown.teleport for bypassing the countdown on teleport · waystonesplus.cooldown.placewaystone for bypassing the cooldown, place waystone needs New config options: · # Sets how many seconds of countdown a player needs to wait before being teleported teleport-countdown: 3 · # Sets how frequently a player can put down a Waystone waystone-place-cooldown: 30 · # Sets how frequently a player can put down a Waystone teleport-cooldown: 30

Now the plugin will work for all players if the server doesn't have a permission manager, if it does however, the admin needs to set permissions.

Fixed some gui error messages

- Crafting can be made optional, by removing the "crafting:" block of a waystone type, or making it false - config.yml have been separated into config.yml for general configuration, and waystones.yml for waystone type configs - A little cleanup had been made by my friend TomTom - The config separation should go smoothly, and none of your settings should disappaer, but make a backup just in case. config.yml new options: # Chance of a Waystone item spawning in random chests loot-chance: 25 # Minimum distance between Waystones minimum-distance: 50 # Default visibility of a crafted waystone default-visibility: "PRIVATE" # Toggles whether Waystone crafting is enabled enable-crafting: true # Defines what the default Waystone spawn item/structure name default-waystone-name: "&6New Waystone" # Enables/Disables notification on Waystone placement new-waystone-notification: true # Sets Title when a new Waystone is placed new-waystone-title: "&7New Waystone:" # Sets Title when a new Waystone is placed new-waystone-subtitle: "&6%waystone_name%"

In the last update I forgot to rename one last thing, and it caused the plugin to completely dont recognise itself. Now it's fixed

Updated how some stuff were named, functionality stays the same in theory.

Event cancelling didnt refunded the spawn item, this is now fixed.

Fixed the issue where you couldn't open your own waystone if it's private, even if you have the permission to do so

Waystone visibility affects which player can teleport/interact/break what Waystone. Global, and Public is accessible for anyone, with the waystonesplus.interact and waystonesplus.teleport permissions, but only the owner of the Waystone, OP players, and players with the new permissions below may perform these actions on another player's Waystone Now a crafted Waystone is Private by default Waystone spawned by /wsp get <type> is GLOBAL (will add it as an option to change) New permissions: · waystonesplus.breakwaystone.private · waystonesplus.teleport.private · waystonesplus.interact.private Small bugfix: When a Waystone is broken, and right after the server shuts down, the Blockdisplays of those Waystones could stay there.

Title says everything.

Well, today I learned that storing a crafting recipe in the memory, actually never generates new uuid for example each time a player is crafting, but is storing the one I generated at the time of the save. Now thats fixed, should eliminate all errors caused by that like: · Waystone not saving · Waystones have the same id, causing it to not appaer on the menu · Faulty Waystone crafted with this recipe cannot be broken fully, and would produce an error message, telling the waystone doesnt exist · Placing a Waystone down from a stack of spawn items, would cause it to delete all of them from the main hand

Op checking was a little off, and some error handling was not implemented

Command(s) now have tab completion, and when you write /wsp get it tab complete the Waystone type name based on your Waystone config. Now OP's dont need permission, they are OP's and they are badasses.

Fixed the bug that caused some pesky error messages when the player was in another dimension and/or wanted to interact with a Waystone. If you had Waystones placed down before, please delete the config files, or add location.world: (world name here) into each Waystone's config file for it to work. I will start working on a way to make config handling, so you dont have to poke around manually to change stuff

Fixed the issue where some permissions were working, some are not. Also fixed the issue happening when a player interacted with a non waystone block.

Added a help command, that lists the current avaliable commands. · /wsp help [page] The help command appaers also when the player is not giving any arguments to the main command

The new permissions are: · "waystonesplus.teleport" · Toggles if the player can teleport to another Waystone from the GUI · "waystonesplus.command.get" · Gives access to the /waystonesplus or /wsp get command · "waystonesplus.rename" · Gives access to rename the Waystone spawner item in an anvil · "waystonesplus.breakwaystone" · Gives access for the player to break a Waystone · "waystonesplus.craft" · Gives access for the player to craft a Waystone · "waystonesplus.interact" · Gives access for the player to interact with a Waystone with left click, this will bring up the Waystone list GUI · "waystonesplus.placewaystone" · Gives access for the player to place a waystone · "waystonesplus.distanceoverride" · Remove the 50 block radius boundary from the player, so it can place multiple Waystones less then 50 blocks from eachother

Every time a new waystone is created, it would create a new instance of MemoryManager to access it's values, not it does not.

If it detects any server with a version below 1.19.4, it automatically disables to ensure no weird error messages happen.

Added support for 1.19.4 so now it works 1.19.4 - 1.20.1

· Now you can modify the player head of the Waystone type. · Added Blackstone type to the config · In the Waystone selector, now the icon is not a Grass block, but the 2nd block/middle block

I didn't know about shading, until now. I fixed it as soon as I could of course

Fast bugfix, I should've tested it all the way