This version of Minecraft was released without the "Patch" number in the version string. This might be normal for Spigot, but it threw off Elevator's pattern matcher. This has been fixed in this push.

Please let me know if you come across any bugs

This patches some issues that were occurring when running on forks of paper. The issue was related to an old-deprecated method of getting the server version that paper had just removed, causing the plugin to think you were running a much older version of MC than was really being used.

This version will also stop spitting the version mismatch message when launching on anything past 1.20, as I have no need to manually update code for each version going forwards.

This version has not yet been tested on 1.21; however, I will do that in a bit. If I experience an issue, I will push out an update soon for 1.21+. If I do not, then expect that the next update will also include a "beta" version of ElevatorsV6 which will not only remove a lot of the pitfalls of this version, but also include more abilities and be open source.

Please let me know if you experience any issues. Thanks to Dnaleor and Jozlod for pointing out this issue with 1.20.5+ paper.

Hello everybody,

This is just a version bump for supporting the latest release of Minecraft Please let me know if you find any problems with it and I will work as fast as I can to resolve them. I can't wait for you all to see what I have in store for the future

I apologize for being a little late with this update. I have some big updates on the horizon and had to backpaddle some code a bit to get to a buildable state

This release is just a version bump, however I would still love posts in the discussion about ideas or bug posts. I will be out-of-state for the next week or so, so I unfortunately won't be able to catch a lot of them unless they are prior to 4 AM Central on the 21st, but I will try my best.

As mentioned, I have a big update in store for the future; A complete rewrite that will be open sourced and will not require updates for every release of Minecraft. This update will also fix a lot of odd issues such as world min height problems. I hope it is received well when it is ready. You can check the progress of it on Github.

I apologize that the last update I pushed still contained some debug print messages I was working with. That is embarrassing lol.

I have a plan to make debugs print only if a hidden config value is true, so it should take care of this from happening again in the future.

Thank you for your patience with me

Hello everybody!

This is simply your typical version update I had tested many base features of Elevators to ensure they all work in the new version; as md5 mentioned in his post, nothing really changed that broke much this time around.

Please let me know if you find any issues or incompatibilities. I am aware of a current issue where reloading elevators breaks recipes and am working on that

It's that time again! And I'm not mad late to it this time.

I haven't kept up well with what has been happening and didn't expect for some of the technical features I thought were solely 1.20 to pop into the new 1.19 minor. I'm certainly going to play around with those to my hearts content.

Please keep me updated with any issues you may come across

Exactly as the title says, I had left some annoying debug messages from when I was testing item pickups. This is my bad and I will be sure double, or even triple check next time.

This update primary patches an issue pointed out by LEE3KFC detailing V1 version Elevatord duplicating when being placed. Oddly enough, the fix is to manually adjust the itemstacks amount because Minecraft just doesn't feel like doing it, despite the event never being cancelled... Anyway, I digress.

This patch also includes the dying locale to the default config while introducing parity to this resources overview config example. Thank you SlimeDog

Please let me know if you find anything off about this version of Elevators and I will try to fix it right away!

First off, I would like to apologize for the long wait between the 1.19 and 1.19.3 updates for this plugin; It is unacceptable and I will hold myself to a higher standard moving forward.

First things first: It is now hardcoded in to set a max and min height depending on the MC version. We shouldn't see any more issues where Elevators don't work below 0 due to it not automatically updating the config. This was in response to an issue posted by oNerdyo in March of last year.

Up next: Thomas9078 had posted about the desire to put dying elevators behind a permission so that they could reward players different colored elevators for different events. Players being able to simply put the elevator in a crafting table with a red dye somewhat hurts that possibility. It certainly is strange that I had included the ability to stop players from crafting colored elevators but didn't stop them from dying them from the very beginning.
The permission is elevators.dye if multiColor is false, or elevators.dye.* if the elevator naturally supports multiple colors. The wildcard * can be replaced with a color to add or remove permission for particular colors.

As for the bug video posted by Plattio in June of last year detailing elevators being able to push you into the ground: I don't remember fixing it, honestly... But I remember testing it right after and being able to replicate it, and now I can't. I have more than likely put in some sort of patch that my long time off had caused me to forget. Please message if this hasn't been fixed.

The 1.19.3 Block Break issues have also been fixed in this update. This issue is caused by a single point in code that returns null if Elevators doesn't have an update put out for that CraftBukkit version. Although it hasn't been done in this update, I plan on pushing out an update that will fix this regardless of if the plugin has been updated. This issue is only a result of Elevators needing to support multiple different types of elevators for a premium version I have never released. The least I can do is make it return the default free one if it errors.

Overall, this update also includes a rewrite of the MC version detections as well as a rewrite of the elevator version detection. In my code, I reference a V1, V2 and V3 elevator. V1 is the original version of elevators prior to NBT being accessible. It stored a block in the shulkerbox. V2 was storing the elevator name and type in invisible text of the shulkerbox name. V3 is what Elevators has been on since 1.13; where the elevator types are stored in NBT Tags on the elevator. When an older elevator is used, it updates to the V3 version to be safer. It is important, though, to support all older versions of elevators incase there is someone a world out there that is still from 2012.

Once again, I apologize for the long wait for this fix. Please keep me updated if you find anything wrong with the plugin so that I can fix it ASAP.

Hello! It is that time again!

I didn't expect 1.19 to be here already. Wow. Shame about those fireflies
Between 1.18 and 1.19, nothing much had changed in the way of code. Your basic field and method names changed, but nothing else. It was honestly a kind update for Elevators; though it might be because it didn't catch me mid-project. I do have a plan to cleanup the code a tad bit, but it wouldn't introduce new features. Let me know if you have any ideas c:

This resource update holds nothing more than 1.19 support, but I would still love it if you could post any issues you find with the plugin. Not all of the hooks that Elevators supports have updated yet, so I may see you again soon if their release breaks the hook

Please keep me updated if you find anything so that I can try to fix it as soon as possible. Have fun in 1.19!

Hello! Once again I have been very sparse on updates to the plugin, and I apologize. Regardless of the free time I am afforded, though, I will always do my best to maintain the project

The release of 1.18.2 caught me in a bit of a mid state of testing out collisions; however, I had the main part of it completed. When a player attempts to use an elevator, it will check the bounding box of the player against three blocks above the next elevator. No more small 'blocks' stopping you from teleporting. You can also do neat things like in the video below. I imagine the biggest use of this may be using doors and trap doors to enable or disable elevators lol



Unfortunately, I am removing 1.13 from a list of 'working' versions. Of course the plugin supports 1.13, however the native java version of 1.13 is lower than I plan on supporting. It is possible to recompile a 1.13 jar in a newer version to solve this issue and keep Elevators running smoothly.

Please let me know of any issues you may run into, either with the plugin itself or any of it's hooks. It is your feedback on issues or ideas that keep this plugin running well

If all goes well, I'm hoping for the next update to include a hook for GriefDefender.

Hello! I have a couple things to share about Elevators on top of this 1.18 update

Sorry this had taken so long to get out. I had been fighting with my setup for a while to make something interesting possible. It's no secret, Elevators uses NMS. I have no issue reading, updating, and working with it whatsoever. I quite enjoy the deep dive into the backends of Minecraft. Why is this significant? Well, Minecraft updated to Java version 16 earlier this year. I will say straight up that I love the new efficiency and additions to java 16 over the older editions, but this java version difference had made keeping Elevators backwards compatible difficult. To keep Elevators working on older versions, I needed to compile with java 13... but then I would get an error from 1.17 and 1.18 classes saying that it could not be accessed due to it not being in java 16. Quite a tricky situation, but one I had found a fun backdoor workaround for. This version of Elevators is compiled with JDK 13, so it should be able to run on older server versions more easily.

All that aside, lets get into the less frustrating changes:

This update somewhat hit me at a midpoint between a change of obstruction detection. In the last version (4.0.5), I had a fairly cringy text file containing materials that should not stop a player from teleporting. It was a straight-forward easy-to-work-with method, but very clunky and a mess to keep updated between versions. This version makes use of an API feature to check if a block is passable first, followed by a bounding-box/collision-box check.


In the above video, you can see that the player can happily go to the second floor while the trapdoor is open, but not when the trapdoor is closed. This is a result of the collision testing mentioned above. The actual collision box of the trapdoor while closed is not in the way of the player when they teleport, so it lets them through. I still want to improve this! It works perfectly fine, but there are always ways to do better. In the first place, since this update came at a midpoint from me making this... The nonobstructivelist text file is completely useless and not read at the moment. I plan to reincorporate this, not as a list containing all the blocks that shouldn't obstruct, but as a file where server owners can specify extra materials that shouldn't count. For example: Candles. Candles have such a small height that it is a bit ridiculous that they block an elevator to begin with. This leads me into my next desire for this collision test: Checking the free space! What's my plan? Take the collision box from two blocks above the elevator, subtract the MinY from the bounding box MaxY of the block on the elevator. If there is enough room for a player to squeeze in there, lets allow them to. I hope the next update has these features instead of it just being for bug fixes, but we should be seeing these features soonish.

Oh, and there is now a %top_floor% placeholder usable in actions now that will display the floor count for an elevator X & Z.

I have not yet been able to test this out with latest releases for hooked plugins. Please report it to me if any hooked plugins cause any sort of error or unwanted behavior.

As always, thank you for supporting my plugin. Please post in the discussions, or directly message me if you notice any issues or bugs. Sorry for the tease with the floating elevators in the video as well I do most of my testing with a different version I plan on fully releasing soon.

SlimeDog is very convincing. I will be sure to increment my versions for even the smallest reasons here on out.

Hello!
It seems that in a patch to paper that merges upstream to craftbukkit, a constructor for CraftShulkerBox was removed. This is incredibly strange for a mid-version patch, but it is what it is.

This update intends to patch this issue by replacing the constructor with new block state methods. The version is being kept the same due to no new features being introduced.

Please let me know if you have any issues with this version! The CraftShulkerBox constructor was mostly used when converting old elevators upon breaking, so that is the area I would expect possible issues, if any. I am hopeful there aren't.

The packages for 1.17 vs 1.17.1 regarding NMS had not changed, so this release is mostly a response to a recent report regarding optional hooks stopping the plugin from working in its entirety. I plan on adding the config options soon to completely disable the hooks, but this solution should work fine for now.
If a hook fails to build, it should simply print in the console
"There was an issue enabling the {Plugin Name} hook for Elevators."

On top of this, I had worked on new support for PlotsSquaredV6. I would really love feedback on this hook. Especially if there are any issues with it.

This release does nothing more than provide a supported release for 1.17. Because of this, I did not bump the plugin version.

I'm terribly sorry for how inactive I have been recently . Work has been taking up way too much time. I want to get back into the groove of things. I noticed some suggestions for compatibility with other plugins in both my DM's and the forums, and I hope to look into those.

With this release, I can guarantee that the nonobstructiveMaterials list updates with the newer blocks and that you can teleport between elevators. Unfortunately, some of the compatible plugins do not yet have a 1.17 version, so some features may not work as intended until I can build against them. For example, the opening/closing animation for the shulkerboxes may not properly function. If this is the case, I will bump the version for a fix

This plugin is built against Java 16, and I am aware that some instances of the minecraft jar may not be happy with this. A java 16 rebuild of the versions jar file should work, of course, but this will still be interesting. It could pose absolutely no problem at all, of course.

As per usual, please let me know if you find any bugs or want any additions.

There has previously been a bug with Elevators in the latest version of Minecraft that would cause stacked elevators that were placed via the offhand to simply place blank shulkerboxes. This issue has been fixed in this latest version.

I have also made a slight modification to how hooks are checked in this version of Elevators. Prior to this version, the hooks would only be checked if the elevator had "checkPerms" enabled in the config. I don't quite know why I had wrote it this way in the past; however, now the hooks will be checked regardless of if that option is enabled or disabled.

Joining the GriefPrevention and latest Plots hook is a spot for BentoBox. Players on servers with BentoBox will now be able to type /is settings and find an option to control who can use elevators within the protected boundary.

It is worth noting, though, that this only supports English. For servers that require a different language, you will have to edit the BentoBox locale personally.

Thank you to everyone who has been supporting and using Elevators If you have any more issues, bugs, or requests, please feel free to DM me or leave it in the discussion forum.

This update is only a version bump to support 1.16.4.

Please alert me if there are any problems with the plugin via DM's or the forum, and I will try my hardest to hurriedly fix them. Thank you, and I hope you enjoy the plugin

Hello again!

Today, I am releasing a version of Elevators with a few little quality of life changes. First up, a new "action." Sound. In the past, the sound an elevator made on use was completely separate in the config. Frankly, this just took up space and required extra support in the code. I had changed it into an action to not only clean up the config a bit, but to also narrow down the plugin size, even if by a couple bytes.


The new format is as follows:

While pitch and volume are stated above using the x=y format, the pitch and volume do have a default value of 1 if not stated. 'p' can also be used in place of the word "pitch" and 'v' or 'vol' can replace "volume." The actual sound name can be anywhere in the value, or can even be behind a "sound=" or "s=" if desired. The sound names can be found here: Click me

The ConfigConverter is already setup to transfer your current sound settings into the Actions map.


This is to keep my word in the discussion forum when I stated I might have found a way to support CMI and PlotSquared.

CMI Hook: Short and sweet. Elevators should no longer be able to be opened as backpacks.

PlotSquared: A flag was introduced called "Elevators." It is set to true by default, and while it is enabled, guests can use elevators on the plot. If disabled, only trusted, owners, or members can use an elevator.

I plan to release a version of Elevators in the immediate future that supports PlotSquared V4 instead of just the premium resource that is V5; however, this current version will only support V5.

With the latest release of an aforementioned Spigot fork, I was able to complete a successful compilation of Elevators for 1.16.2

This version of Elevators also supports a fix for placing Elevators via Dispensers found by @Aust1n46.

I was holding off on this update for ensuring the quality, but thanks to the recent 1.16.2 update, I get to announce today that I have created a somewhat baseline API for Elevators
The class name is "ElevatorsAPI" in the package "com.cultivatemc.elevators" and it contains methods ranging from checking if shulkerboxes or itemstacks are Elevators to registering new "actions" for elevators on use. While the "ElevatorClass" object can be retrieved using the API methods, I can not ensure the methods in the "ElevatorClass" class will remain the same in the next update as I hadn't gotten around to cleaning it up before posting this. I hope to get more info regarding this available on the main page soon, and possibly soon introduce a github.

Thanks for supporting my plugin thus far If you have any suggestions or any problems with the plugin, please feel free to DM me or mention it in the resource discussion forum.

This version of Elevators fixes a few previously mentioned bugs, such as a problem with pistons being able to break elevators found by Aust1n46, as well as an issue with Elevators not dropping correctly in 1.14, discovered by La_Chritz.

There have also been a few back-end changes to the code to tidy things up for the sake of my own sanity and generalizing a few variables so that the free version does not contain default data for use only in premium. This can be seen by the locale section of the config file being moved under the key "locale."

On top of this, "actions" have replaced the "commands" section for elevators!
Actions are simply lists of text that define what should occur upon moving upwards or downwards. As of right now, there are only four actions:

These actions can be used in the config like so:

The actions currently allow for placeholderAPI support + a few built in placeholders such as:


The messages for Elevators now also support hex in 1.16+ using the format seen above, or through the bukkit method (§x§0§0§8§8§f§f).

The config converter was also upgraded to be both nicer, and to support upgrading configs all the way from V1 up to the current (V4), so you should not have to worry about updating your config. Even the 'commands' section of the last versions config will be updated automatically to use actions.

Thank you all for supporting my plugin This plugin has been a lot of fun to work on, and, truth be told, the recent update of adding in metrics has been giving me great encouragement to continue updates such as these.

As usual, if you find any bug or any problem with this plugin, please do not hesitate to leave a comment in the discussion forum or directly PM me. I will work to fix the issue as soon as possible

This update is fairly low priority as it changes very little; however, I still wanted this to be let out. Sorry to those who got yelled at by the auto updater The contents of this post were all made to address issues found by @HarlWindwolf.

The first issue pointed out was that the default generated config file would have the two "give" messages swapped. I am sorry for having let this slip past me for so long. This update will fix these values in the config.

The second issue dealt with jumps not always being registered if there was a carpet on top of the elevator. Although I have not personally seen this issue, I have decided to release a new version of this plugin that supports the PaperMC fork's "PlayerJumpEvent."
As mentioned in the past, Spigot does not offer a player jump event, so I have to detect jumps by listening to player movements and choosing when to accept the action as a jump. With this update, though, servers using the fork will possibly experience better consistency.

If any issues are found with the plugin, please feel free to DM me, or mention the issue in the plugins discussion forum. Thanks for supporting the plugin

A minor update that is mostly for my own benefit.
This update includes a method of alerting staff if a new version of the plugin has been released, as well as a lite metrics class so I can see how many people are actively using the plugin.

Although I hope there are no future releases required to fix groundbreaking bugs, the update checker could be of use to alert server owners of such a release. It is completely toggleable in the config, and the ability to see the update message is locked behind a perm node that can easily be negated from op's.

As per usual, thank you for checking out the plugin, and please send me any requested features or issues in DM's or in the plugin thread

There are no new features in this version of elevators, however, 1.16.1 will now be supported. If a later version of 1.16 is released, I will let out an update to support that version as well.

There has been one change to this version, and that is regarding the nonobstructiveMaterials text file. Upon startup, the server will update the text file to include the latest non-solid blocks from 1.16, regardless if your server is using 1.16 or earlier (This will cause no issues). Any additional materials that you might have added to the file yourself should stay in the file after the initial startup.

Please let me know if you find any issues with the latest version of elevators

As mentioned in a post by jay9519 via the discussion forum, there was an issue where renaming an elevator to be blank in an anvil would result in the anvil giving an empty shulkerbox. This update deals with the problem by setting the result of the anvil to a fresh elevator with the custom name.

Please notify me of any issues you might have with this update via DM's or on the forum discussion Thank you all for consistently helping me improve this plugin

A small update to satisfy a request of a spigot user named MrEngMan.
MrEngMan had requested the addition of banners and signs to the list of materials that do not obstruct elevator teleportation.
I can say that I (sorta) did that.

The previous method of detecting whether the block obstructs teleportation was through Bukkits own 'Material .isSolid()' method. Unfortunately this did not include signs and banners. In this newer version, a text file named "nonobstructiveMaterials" is generated in the Elevators plugin folder on first run. This will contain a list of blocks that will not obstruct an elevators usage. (The default list is the same results as what the Bukkit method would return, but I did go ahead and include banners and signs out of the box).

To add a block to the list, simply add a new line and enter in the name of the block as shown at: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Material.html

Jump detection has always been a little strange in Bukkit/Spigot. Despite the velocity change from jumping occurring on the server, a "PlayerJumpEvent" hasn't been made except in some forks like Paper (Which I can't use because I want to support native spigot.)

The method for detecting jumps is listening for the players movement and the difference between the current y value and the previous y value.

I can proudly say that I have rewritten the jump detection code to fix issues where stepping up to a nearby block would cause you to move up a level. I have also, to the best of my ability, fixed the issue where jumping over the elevator will cause you to move upwards. In general, the efficiency of the math in the event was also improved.


In the last update, I made a move to purely saving data via NBT instead of using methods like storing data to the name of the shulkerbox entity. Unfortunately, when a shulkerbox entity is broken, it keeps all the NBT data stored to it except for the ones supplied by plugins. I don't know if this was an oversight, or on purpose, but it ruined the ability to naturally drop the elevator as an item either way. I had to intervene with a listener for BlockBreak and manually drop a new elevator item, which some protection plugins lagged behind mine on listening to the event.

Well... Not anymore. Elevators has natural support for 'V2' stored elevators. That is, elevators stored by the box name versus the NBT tag. Instead of listening to break and spitting out a new item due to loss of NBT, this version will run first and change the name of the shulkerbox entity to match that of the V2 system. This means that the plugin will be able to recognize the dropped item is a "V2" elevator and will convert it to V3 again on pickup. A bit hacky, but in comparison, a computer is a rock we taught to think.

Regardless, this fix should allow protection plugins that didn't cooperate with the previous update to work again. Known ones were WorldGuard and the protection system provided by BentoBox.


The main goal of making this update was to add in GriefPrevention support after it was recommended to me by a person with the name "mtoth."
So I tried my hand at it

Elevators already respected GriefPrevention in terms of breaking and placing, but all players were able to use the elevators. This is why I added in support for GriefPrevention directly.
This update introduces two new boolean config options (and locale player messages) that will control this feature.

' supportClaims' will default be true. If this is disabled, the plugin will naturally allow all players to use the elevator.

' claimProtectionDefault' will default be false to replicate old behavior. When enabled, this will ensure that all placed elevators will only work for trusted players by default.

Since I provided a 'default' value for the config, this should give clues that there is a method of changing the value per elevator. This is true For Minecraft servers 1.14+, trusted players in claims will be able to 'sneak-right-click' elevators to change whether or not that individual elevator will allow anyone to traverse it, or only trusted users. Unfortunately, I cannot get this to work for 1.13 servers due to the lack of ability to set NBT to the entity itself. They are stuck at the config's default.

I also snuck in a cute little animation for the shulkerbox. I Hope you enjoy this feature


The addition of something that is toggleable per elevator is unique to this version. Previously, all elevators followed the same rules. I hope the update + method in which I allow the change is received well. I don't mind changing the methodology based on community input, so feel free to speak your mind. I personally had this update finished for a few days, but was hesitant to put it out. I finally decided to release it due to the mentioning of disagreements with protection plugins.

Regardless, thank you all for supporting me with this plugin. If you come across any issues with it, please let me know via DM or the discussion forum and I will work to fix the problem.

I apologize for not catching this in my own testing, but this should fix the issue where picked up elevators return to normal shulker boxes.

I hope to, someday, reach a level where I am professional enough to nail this sort of thing first try.

Next update, possibly: Allowing players to stack elevators by clicking them together in their inventory. At the current moment, this isn't possible thanks to Minecraft's built in max stack size for shulker boxes, but I think it would be a nice little cosmetic change. If people want this, I will see about it when I have time

For some odd reason, a couple spigot releases ago (Still 1.15.2) broke placing only Purple elevators. I don't quite know the reasoning for this, and it was very weird. BUT, it has been fixed in this version, regardless... So I guess, here's to the re-release of Purple elevators?

Another update coming to this version of Elevators is one suggested by a user named La_Chritz. There will now be a "disabled-worlds" string list in the config where you can specify worlds that elevators can not be used or placed in. I will update the config example on the main page to reflect how to use this.

Behind the scenes of this update, the code is now fully updated to use NBT for storing the elevators in 1.14+. 1.13 will have to live with the older method of naming the shulkerbox block, which should still provide no inconvenience.
Also fixed in this update is an exception that would appear on plugin reload and server stop whilst clearing the plugins recipes. This error came about due to a change in the map type that holds recipes between spigot versions and paper.

As always, I hope this update is well received and doesn't misbehave. I believe I have tested thoroughly, but I can never be as good at finding things as you all. If you find a problem, please DM me or leave the problem in the discussion forum. I will try to answer back as soon as possible.

This is an update for the latest release of Minecraft There aren't any new features from the previous release of Elevators besides compatibility with 1.15 and a few little QOL changes. Like the previous updates, this is compatible with 1.13+.

Please DM me or leave a forum post if you have any troubles at all, and please report bugs.

Thanks for using my plugin

I had previously used the word-directory to grab and export files to without realizing that the world-directory could be changed via bukkit.yml. This resulted in the plugin data folder appearing in the world directory instead of in its rightful place.

This new jar file should fix this issue

This version fixes a horrible issue that I must apologize for. The previous version of elevators would still attempt to convert non elevator shulker boxes by force facing them upwards, and possibly clearing their inventories. If this last part has affected you, please message me.

Story you can just skip:
Around last month, I had seen a post on a discord server about PersistantDataContainers and thought "I just had to use this in Elevators," so I started work on recreating the plugin to be not only be more organized and easier for myself, but to include this new way of saving data. Unfortunately due to work and school, I stopped progress on this until a nice developer named mk7a reminded me of the functionality. Since then, I had finished up both the free and premium versions of the plugin, so here it is

What does this mean?
So far with elevators, I have developed a habit of moving the plugin up an entire version when I remake the method that data on elevators is stored with. First it was through a block in the shulkerbox, second through hidden text in the name. Now it is saved into the NBT tags of the shulkerbox item.

This means you can rename your shulkerboxes to your liking without worry of breaking them!

The past few updates put out for this plugin have been made to stop players from renaming the elevators through anvils or other methods. With this update, there is no longer any need to prevent this action. Old elevators will update.

Other new stuff?
Well, a few. While most direct changes went to the other version of the plugin, a few slipped in here.
For example:

• The give command now has an amount argument
• The give command will now display the message even if simply adding to existing box
• The give command will not always display the "inventory full" message like in some past versions.

As per usual, please report any bugs you discover. I have tried to test a lot to find issues, but sometimes a few slip through the cracks. Please either DM me or post in the discussion forum any you find.

As the data for Elevators are stored in the name, the previous few updates have been for help preventing methods of renaming the shulker box. This should (hopefully) be the final one: Cancelling the anvil event if the item being renamed is an elevator.

Upon elevator break, the elevator will drop an updated box. This should fix the problem of Lore not existing after placing and breaking.

As for permissions, I made a few small changes that should stop confusion.

In the past, if "coloredOutput" was disabled in the elevator, the elevator.use perm would change. This was the same with a recipe use and "
coloredCrafting." From this point on, the version of the permission with the asterisk will work regardless of these config options.

Confusing explanation, but basically:
"elevators.use.*" will now work even if coloredOutput is off. This makes it a uniform permission node. I should've made it this way from the start.


Sorry about all the small individual updates that have quite possibly been annoying to deal with.

This update adds the ability to put lores onto the shulker boxes straight from config.
Although it is a cosmetic addition, it can also be useful for plugins that allow blacklisting based off lore.

Yep! That one previously useless config option is finally working! That's it. A small update, but one nonetheless.

The 'forceFacingUpwards' config option is enabled by default, and will cause placed elevators to face upwards. It will also straighten out already placed elevators on use

As usual, I welcome suggestions

I made a mistake and had flipped around the conditions of permissions. This should fix that, and allow reloading in 1.14.

Known bug is elevators sometimes saying an inventory is full when using the give command despite there being plenty of room. I forgot to fix that by the time I posted this .-.

This update not only includes updates for 1.14, but has been completely recoded in light of a premium version I personally sell.

From here on, elevator updates should work across all versions. Meaning this file will also work in 1.13.2 + 1.14.

The biggest change compared to the previous elevators system is that this stores the data in the display name of the elevator instead of in the shulkerbox. This does make the plugin disposable after being introduced. Old elevators will be updated into the new ones upon use. There are a few new features, such as display name being customizable + commands to run up and down. I believe there were changes with how recipes can be made and individual perms for each recipe.

Although placeholders is supported, I can not vouch it will work in the 1.14 version. If it does not, I will update it.

If you find any issues, please report it to me, I will try to fix them quickly.

Mainly just changing NMS imports to work with 1.13.1

Just a 1.13 update. 1.13 changed the JSON behind the code a lot, but it wasn't really a big change for this...Though, I have been considering adding to it.

If this breaks in the future from another 1.13 release, I'll be sure to update it. You may need to let the config regen itself for this to work.

Let me know if you think that creating custom recipes for elevators with custom max block lengths would be neat. Maybe support other coloured blocks instead of just wool.

I may look into this for future versions. (Busy right now updating other much harder plugins to switch)

Enjoy

Now that I am back from touring, I can post this small little update that people had requested. It is absolutely nothing big at all, but it fixes the "plugin has used deprecated method" statement in the consoles, as well as changes from item ID to the string name. (You will have to change this in the config if you want it to work with a custom recipe)

If you have any ideas for the plugin, feel free to mention them, and when I become available, I will try to look into them. (College, man .-.) I had seen one request for an optional cool down on elevators, for example.

Would you like that?

In the past version of elevators, you could not open an elevator through right clicking, but it was still possible to open it through code. Other public plugins had not respected the cancelled event and had, instead, created ways of still opening the elevator (Such as the bug in the latest review, where one could open the box using flint and steel.)

This update is my attempt at stopping other plugins from still letting players open elevator inventories.

Nothing really changed. Just updating to the new Spigot.

(The old version should work as well, since nothing required change between the versions, but this one did fix a deprecated event)

This is just to fix up those errors from that day we shall never speak about.
- Removal of internal lore counter...and Herobrine.

I apologize so much for the mass updating, or rather I should call it bug fixing without precedence. Maybe I should look into putting an auto updater on this thing for all the times I mess up. I think I have a good idea, and I work on it until I am not thinking correctly anymore...and this comes out...

Well, this is my last update for today, and probably a while. Doing this is very stressful for the amount of possibilities a bug with a shulkerbox can propose, and I don't want to be at fault for ruining someone else's server. I guess i'm in over my head, huh?

Again, I'm sorry. If you have updated to a previous version earlier today... UPDATE NOW. It is of importance.

A bit of a small update, but still a pretty great one to have. This update lets you stack elevators now. Added config for max stack size, and whether or not the stack number appears on the item as well as in the lore. I also removed a little hidden command built in to work with essentials /recipe. Since one essentials resource removed the command altogether, and the other had a temporary duplication glitch before being disabled, it's not needed. Have to resort to showing people on a website, or in item frames. Sorry.

Simply support for 1.12

Added a give command to give a player an elevator. Usage: /elevators give <player> [durability]

Config will now add on to current config without requiring you to delete it first.

More customization in messages to players when they lack permission to use commands.

Gives the configurable options play sounds through the world so others could possibly hear it, or for the sound to be played only to the player using the elevator.

Please..Just please.

In this updated, I have added the ability to use permissions with the elevators plugin. Permissions such as elevators.use.*, or elevators.create, or even elevators.reload. You can specify which elevators can be used individually, as well.

Extra additions: command to reload the configuration, and the ability to specify the amount you get from the recipe. Side note: Shulker boxes do not stack naturally.

Added a ton of config options.