Custom Jumppads | [1.8 - 1.21] icon

Custom Jumppads | [1.8 - 1.21] -----

A Jumppad-plugin like no other! Featuring realistic arch-like flight!




[​IMG]

  • 1.21.8 | Custom Jumppads should now function properly on all versions up to and including 1.21.8.
----------, Aug 1, 2025

[​IMG]

  • Fix | Sound can now only play once for a jumppad location.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Oct 22, 2022

[​IMG]

  • DeluxeCombat | Added support for Deluxe Combat. If a player is in combat they can't launch.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 27, 2022

[​IMG]

  • 1.19 | The plugin has been fixed and now works on 1.19.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jun 17, 2022

[​IMG]

  • Fix | Fixed particles for trails if using "NONE" as value.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 8, 2022

[​IMG]

  • Particle and Sound | You can now use "NONE" as the value for /jp set particle/sound to disable particles or sound for individual jumppads.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 6, 2022

[​IMG]

  • Fix | Fixes the Spartan integration to function with the latest Spartan version.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Feb 3, 2022

[​IMG]

  • Fix | Custom Jumppads now works properly with Matrix Anticheat.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 20, 2021

[​IMG]

  • AntiCheat | Custom Jumppads now support NoCheatPlus, WitherAC, Matrix, AAC, and Spartan.

    The implementation testing of Matrix, AAC, and Spartan has been very limited. Let me know if there are any issues.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 7, 2021

[​IMG]

  • Fix | The PlayerData class method visibility has been changed to public for external use if required.

  • 1.17 | The plugin works fine on 1.17.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 7, 2021

[​IMG]

  • Fix | In some cases, JumpPads did not register all worlds on startup requiring you to reload the plugin with the built-in /jp reload command. This issue has been addressed and should hopefully no longer occur.

    Reported by @mibby; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 10, 2021

[​IMG]

  • Improvement | Custom JumpPads will now maintain an internal list of all worlds that have jumppads. Depending on how many worlds your server has with no jumppads this update can vastly improve performance. This especially applies to the launchLivingEntities option as most entities can be filtered very early on if the world has no jumppads.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Feb 18, 2021

[​IMG]

  • Change | The launchLivingEntities option default is now false for newly generated configs. This option is quite resource-intensive and often not wanted or needed on most servers. This will not affect your current config so if you want to disable this you can do so in the config.yml to reduce Custom Jumppads resource usage on your server.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Feb 12, 2021

[​IMG]

  • Fix | The integration with CombatLogX could fail if the plugin loader did not respect the plugin load order for whatever reason. This has been solved.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jan 16, 2021

[​IMG]

  • CombatLogX | Custom Jumppads now support CombatLogX. You can now decide if players should be able to use jumppads if they are in combat. Please add the following to your config.yml file if you wish to make use of this feature:
    Code (YAML):
    # Should players be allowed to use Jumppads when in combat?
    # Requires CombatLogX.
    disableInCombat
    : true
    The default is false. You do not have to add this if you do not want to make use of it.

    The following message has been added to the messages.yml:
    Code (YAML):
    Messages:
      InCombat
    : ' %prefix% &cYou can't use jumppads when in combat!'
    The message is automatically generated.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jan 4, 2021

[​IMG]

  • WitherAC | Jumppads is now compatible with WitherAC.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Nov 3, 2020

[​IMG]

  • Fix | Using jumppads to launch into portals or similar could result in spamming your console with exceptions as the plugin was trying to measure the distance between the player and the launch-entity which may not be in the same world.

    Reported by @XipsAhoy; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Sep 4, 2020

[​IMG]

  • Fall damage | The player lands before the launch-entity. In that timespan from the launch-entity lands and the player is in the air the player could accumulate fall distance resulting in them taking damage when landing. Jumppads will now keep track of the player until they either land or their y-direction stops decreasing. This should eliminate fall damage from jumppads completely.


  • Sound | You can now specify whether jumppads sounds are played in the world or only to the player with the following option:
    Code (YAML):
    sound_world : true
    The default is true. If set to false the sound is only played to the jumping player. If you do not wish to change the default you do not have to add the above.

    Suggested by @Lambsauce; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 23, 2020

[​IMG]

  • Memory Optimization | PlayerData is now handled properly.

    Prior to this update, a PlayerData entry was created for a player as soon as they moved; with this update, the entry is first created once the player actually uses a jumppad. This will significantly reduce the number of entries.

    PlayerData is now cleared once a player leaves the server. The entry serves no purpose between client sessions thus the reason for removing the entry.

    All in all, this should make jumppads use a lot less memory.

    Reported by @Mr.Midnight; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 17, 2020

[​IMG]

  • 1.16 | Custom Jumppads support 1.16(.1) servers.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jul 3, 2020

[​IMG]

  • Feature | If the player for some reason lands further than 10 blocks away from the launch-entity they are teleported to it. Failed launches can occur due to client-side lag, high ping, long launches, etc. This should act as a failsafe for such scenarios.

    Reported by @Mr.Midnight; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jun 22, 2020

[​IMG]

  • Clear Lag Plugins | This update improves compatibility with clear lag plugins. This is done by overriding the launch entity's life tracker by continuously setting it to 1 tick during launch. This will make it seem as if the entity is brand new for the duration of the flight thus tricking lag plugins. Furthermore, the entity is named internally which some clear lag plugins check for as well.

    Suggested by @Mr.Midnight; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jun 19, 2020

[​IMG]

  • Fix | NCP on newer versions could result in some jerky landings. This has been fixed.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, May 29, 2020

[​IMG]

  • Fix | If an entity other than a player used a jumppad on 1.8-1.10 it would cause a very spammy stacktrace. This has been fixed.

    Reported by @BluueJay; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, May 25, 2020

[​IMG]

  • Fix | WorldGuard could throw an exception stating that it isn't possible to drop air. I've disabled the launch-entity's drop-item attribute (It didn't drop anything previously). This should stop the server from trying to drop air and thus eliminating the exception thrown by WorldGuard.

    Reported by @MorpheusTresdin; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, May 2, 2020

[​IMG]

  • Improvement | Due to caching changes on Spigot the latest version of a plugin returned from the websites API can take multiple hours before updating to the correct version. E.g. your version is 1.0.1 but Spigot still incorrectly returns 1.0.0 as the latest version.

    Due to the large number of "The plugin says there is a new version available, but I already downloaded the latest version" messages I've been receiving I've gone ahead and implemented a parser that'll only notify you of updates if the version on your server is less than the one on Spigot. If you're on 1.0.1 and Spigot returns 1.0.0 you'll no longer get an incorrect notification.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Apr 25, 2020

[​IMG]

  • Teleporting | You can now allow teleporting during launch. By default this is disabled. If you wish to enable teleporting please add the following to your config.yml:
    Code (YAML):
    # Block teleporting during launch.
    blockTeleporting
    : false
    If you wish to continue blocking teleports during launch you do not have to add the above.

    Suggested by @AcornMC; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Apr 13, 2020

[​IMG]

  • Launch Fix | If a player landed on the edge of a block there was a chance that the entity the player follows would hit the edge of the block and fall down causing the player to be dragged off the block and down. This version fixes this and the launch is stopped once the player is on the ground even if the launch-entity isn't.

    Reported by @BigLife5 and Pempkin; thanks!


  • Improvement | The plugin will now detect if the player is next to a ladder. If they are the launch is ended and the player can climb the ladder without being dragged down for a few seconds.

    Reported by Pempkin; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Apr 8, 2020

[​IMG]

  • Fix | A teleport cause was not valid in 1.8. This caused the plugin to not initialize at all. This has been fixed.

    Reported by @DebuffPvP; thanks!


  • Debugging | Removed some unnecessary debugging.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 15, 2020

[​IMG]

  • Fix | All teleportation during launch, with the exception of portal teleportation, is now blocked.

    Suggested by @BurntValentine; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 15, 2020

[​IMG]

  • Fix | The "maxPower" setting in the config now applies to the /jp set power command as well as that wasn't limited.

    Reported by @BurntValentine; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 11, 2020

[​IMG]

  • Fix | Using the /jp list command you can teleport to jumppads by clicking on the entry in the list. If you had jumppads in multiple worlds clicking would cause an IAE as it would try to measure distances between worlds. This has been fixed.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Mar 9, 2020

[​IMG]

  • Permissions | You can now give users permission to use specific /jp set commands. E.g. if you want your users to be able to set the color of jumppads you can give them the permission "jumppads.set.color". You can still use "jumppads.set" to give permission to all set commands. The following are valid sub permissions: power, angle, direction, permission, color, particle, sound

    Suggested by @BurntValentine; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Feb 29, 2020

[​IMG]

  • CleanUp | You can now disable the CleanUp functionality or disable it in specified worlds. The following has been added to the config.yml file:
    Code (YAML):
    # CleanUp will remove any jumppads that have been incorrectly removed during server startup.
    # An example of this is removing a jumppad with WorldEdit. It will then be removed on next startup.
    CleanUp
    :
      # Set whether or not CleanUp should run on server startup.
      enabled
    : true
      # Configure any world in list format that you want excluded. E.g. if you have a world
      # that gets reset but don't want to remove the jumppads then add the world here. (Case-Insensitive)
      ignoredWorlds:
    You'll have to add the above manually if you wish to configure it. If you're fine with CleanUp running on server startup as always you do not have to add the above.

    Suggested by @RuymanphoneR; thanks!
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Feb 21, 2020

[​IMG]

  • Fix | The latest version i.e. 1.15.2 broke the plugin. This was due to materials being resolved in a different way in 1.15.2. This has been fixed.

    Reported by @dada513 & @self_slaughter; thanks!

  • API Version | The API version has been updated to 1.13.2.

  • Particle changes | Due to some methods not being available in the new API version some refactoring and restructuring had to be done.
[​IMG] [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jan 22, 2020

[​IMG]

  • World Fix | Removing a world before removing all jumppads would cause the plugin to spam NPE's as the visualizer is trying to spawn particles in non-existent worlds. This has been fixed.

    Reported by @PirateCraft; thanks!

  • Clean-Up Improvement | The clean-up check during server startup will now remove jumppads that have not been removed from any removed worlds.

  • Block Break Improvement | When removing the block beneath a jumppad (manually) the plugin will now correctly detect it and remove the jumppad above as well.

  • Debugging | Removed some unnecessary debugging regarding effects.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Jan 14, 2020

[​IMG]

  • Fix | It is not possible to stop sound in 1.8 and 1.9 as the method doesn't exist. If you were running one of those versions exceptions would be thrown every time someone used a jumppad. This has been fixed.

    Reported by @LoneDev; thanks!

  • Maven | Maven framework support has been added to make handling dependencies easier.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Jan 12, 2020

[​IMG]

  • 1.15 Support | Custom Jumppads now support 1.15 servers.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Dec 13, 2019

[​IMG]

  • Angle Constraints | When creating a jumppad the angle has to be within 1 and 90 both inclusive. This applies to the set command as well.

    Suggested by @SoulStriker_; thanks! ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Nov 17, 2019

[​IMG]

  • Spectator | Jumppads will now ignore players in spectator game mode.

  • Vanish | If you're in vanish mode jumppads won't play effects, sounds, or particles.

    Both suggested by @Maxito; thanks ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Oct 20, 2019

[​IMG]

  • Actionbar | The actionbar utility class has been completely rewritten. Prior to this update NMS classes, constructors, methods, and fields were all accessed directly via reflection every time a message was sent to a player; that is quite resource-intensive if used frequently.

    This update ensures that all of those code related entities are cached and reused. This means that they are only accessed during startup and then reused as needed when messages are requested. This will have a significant positive impact on performance.

    Please note that this only concerns 1.8, and 1.9 servers. 1.10 and up use the built-in method in the Spigot API for sending these kinds of messages.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Sep 21, 2019

[​IMG]

  • Owners | Jumppads created from here on out has an owner with the possibility of multiple in future updates. Currently, this does not have a purpose, but in future updates, this will allow players to control their own Jumppads based on who owns them. E.g. I can only edit my own Jumppads (also based on permissions).

    Please note that even though this doesn't have a purpose yet I'd suggest updating as soon as possible to this version as "old" Jumppads won't have an owner assigned. In other words the sooner you update the more prepared you are for what is to come ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Aug 30, 2019

[​IMG]

  • Quick Fix | The last update contained an error where interactions would produce a NullPointerException. If you updated to 1.22.7 please update to this version as soon as possible. Sorry for the inconvenience.

    Reported by @Truger23; thanks!
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Aug 28, 2019

[​IMG]

  • Sound | Pressure plate jumppads will no longer play a generic click sound when you step on them.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Aug 28, 2019

[​IMG]

  • Particle Fix | The visualizer had a few flaws due to some particle spawning logic that was changed after implementation of the visualizer. Prior to this update the angle would increase based on the number of players on the server which would result in spawning multiple rings getting bigger and bigger the more players online which resulted in spawning a lot of extra unnecessary particles. This has been fixed.

  • Particle Improvement | Due to particle implementation changes in JumpPads the many distance calculations have been removed as they are unnecessary. This will improve performance in conjunction with the above fix.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Aug 5, 2019

[​IMG]

  • Fix | If the entity was "caught" during launch (e.g. by cobweb) it could result in some weird glitchy behavior. This version ends the launch if the launch-entity's velocity is 0 i.e. it's stationary when it should be moving.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Aug 3, 2019

[​IMG]

  • Fix | If you were to run the /jp list command with no configured jumppads an exception was thrown. This has been fixed.

    Reported by @Tazler; thanks! :)
[​IMG] [​IMG]
[​IMG]
----------, Jul 29, 2019

[​IMG]

  • Plugin.yml | All permissions have been migrated to the plugin.yml. The default for the jumppads.update permission is false to comply with the updateCheckerPermissionOnly setting.
[​IMG] [​IMG]
[​IMG]
----------, Jul 28, 2019

[​IMG]

  • Fix | The culprit of the spammy error has been found and corrected. Thank you to @AldenSH for providing the stacktrace! :)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Jul 9, 2019

[​IMG]

  • Fix | Changed up an incorrect equality check. This should hopefully prevent a rare spammy error that could occur after many hours of uptime.
[​IMG] [​IMG]
[​IMG]
----------, Jun 26, 2019

[​IMG]

  • Tab Completion | The main command will now suggest its subcommands or those that start with the current input.

    All subcommands with additional parameters will suggest those. E.g. the /jp set sound command will suggest all available sounds even based on the server version you're running as well as suggestions for the volume and pitch parameters. This goes for other attributes as well such as particle. You are no longer required to open your browser and search for what the enum is; just press tab and find the one you require! ;)

  • Command Framework | The command framework was a bit outdated in comparison to what some of my newer plugins use. I've gone ahead and changed up quite a few things during the process of implementing the tab completer.
[​IMG] [​IMG]
[​IMG]
----------, Jun 17, 2019

[​IMG]

  • Color Fix | Most colors would show as black on 1.13/1.14. This has been fixed and all colors now work correctly again.

    Reported by @HexedHero; thanks :)


  • Lombok | Migrated the entire project to make use of Project Lombok which reduces a lot of the Java language verbosity.

  • Fix | The prior update regarding sounds now also applies to entities getting launched.

Sorry for the frequent updates.
[​IMG] [​IMG]
[​IMG]
----------, Jun 15, 2019

[​IMG]

  • Sound Options | You can now specify volume and pitch with the /jp set sound [sound] [volume] [pitch] command. Volume and pitch are both optional and both default to the value specified in the config (mentioned later).

    Suggested by @HexedHero; thanks :)

  • Config Options | Two new options have been added; volume and pitch. These are used to specify the default value for the sound. Add the following to your config.yml if you wish to configure this:
    Code (YAML):
    volume : 1
    pitch
    : 1
    The defaults are 1 as before. If you're fine with that you do not have to add the above.

  • Improvement | Specified sound values are now case-insensitive. Prior to this update, you had to write in uppercase.

  • Improvement | The parameters for the different attributes have been added to the help hover message as seen below.
    [​IMG]
[​IMG] [​IMG]
[​IMG]
----------, Jun 15, 2019

[​IMG]

  • ActionBar | By prepending any message in the messages.yml file with <ActionBar> you can send the message as an ActionBar message instead of a chat message.

    Example:
    Code (YAML):
    Messages:
      ConfigurationsReloaded
    : <ActionBar> %prefix% &aConfiguration files successfully reloaded!

  • Fix | One of the messages sent could cause an exception. This has been fixed!
[​IMG] [​IMG]
[​IMG]
----------, Jun 14, 2019

[​IMG]

  • NoCheatPlus | This update introduces support for NoCheatPlus. Jumppads will automatically detect if NCP is installed. During launch players are exempted from survival- and creativefly checks.

    Thank you to @Digital_Beast for suggesting this and testing the implementation! :)
[​IMG] [​IMG]
[​IMG]
----------, Jun 8, 2019

[​IMG]

  • Fix | Any user executing the /jumppads command with no args would get the help menu printed in chat regardless of permissions. This has been fixed and /jumppads with no args now correctly require "jumppads.help".

    Reported by @csorrows; thanks! :)
[​IMG] [​IMG]
[​IMG]
----------, Jun 4, 2019

[​IMG]

  • Flight Prevention | In some rare cases (this has only ever been reported once) jumppads could leave the player in flight after the launch had ended. This version should eliminate that as an effect of the added check and prevention logic.
[​IMG] [​IMG]
[​IMG]
----------, May 29, 2019

[​IMG]

  • Quick Fix | Since one of the recent 1.19 versions it was no longer possible to create jumppads on Slime Blocks. This has been fixed and is now possible again.

    Reported by @self_slaughter; thanks!

    Sorry for the double update!
[​IMG] [​IMG]
[​IMG]
----------, May 11, 2019

[​IMG]

  • Void | The trajectory responsible entity is now removed if its y position is lower than -10. Before this update, it was removed by the server at approximately -80.

  • Entity Launcher | The update speed of the entity tracker has been increased due to the fact that it wasn't fast enough. If you had a carrot on a stick and a pig following you walking over a jumppad it would in most cases not trigger.
[​IMG] [​IMG]
[​IMG]
----------, May 11, 2019

[​IMG]

  • Case-insensitive | Attributes were case-sensitive i.e. required lowercase; also in commands. E.g. /jp set Color &a wouldn't work but /jp set color &a would. This has been changed and attributes are now case-insensitive.

    Reported by @kyorionaaa; thanks! ;)
[​IMG] [​IMG]
[​IMG]
----------, May 10, 2019

[​IMG]

  • 1.13/1.14 | All new pressure plates in both 1.13 and 1.14 are now supported!
[​IMG] [​IMG]
[​IMG]
----------, May 4, 2019

[​IMG]

  • 1.14 | Custom Jumppads now support 1.14 servers! ;)

  • Fix | If inputting an incorrect value in the /jumppads set <attribute> [value...] command it would respond with both the error and the success message. The following attributes were affected: power, color, particle, sound, and angle. It was harmless though confusing. This version fixes that issue as well.
[​IMG] [​IMG]
[​IMG]
----------, Apr 28, 2019

[​IMG]
If you're running Custom Jumppads on a 1.13+ server it is strongly advised that you update to this version.

  • 1.13 Fix | A while back some major fixes were implemented to address an issue where the trajectory-assisting entity wasn't removed and was only removable by using world edit. This could also result in the removal of water blocks and other non-solid blocks. This fix was only implemented for player launches but it has come to my attention that other entities such as animals and monsters were affected. This version fixes this issue!

    Reported by @self_slaughter; thanks! ;)
[​IMG] [​IMG]
[​IMG]
----------, Apr 18, 2019

[​IMG]

  • Fix | During startup, an exception could occur when the CleanUp algorithm was run. This has been fixed in this version.

    Reported by @ZamanPvpNetwork; thanks! ;)
[​IMG] [​IMG]
[​IMG]
----------, Apr 15, 2019

[​IMG]

  • Fix | As part of my testing with the teleport command I used particles to verify that the location offsets were the correct ones. This resulted in errors on 1.13 servers. The "debug" particles have been removed and should no longer cause issues.

    Reported by @RobotoRaccoon; thanks! ;)
[​IMG] [​IMG]
[​IMG]
----------, Apr 1, 2019

[​IMG]

  • Teleport Fix | One of the previous versions fixed an issue with teleportation during launch in 1.8, however, this introduced a new error for non-1.8 versions. This has been fixed and the teleportation is now correctly canceled.

    Reported by @OpvpYT; thanks! ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Mar 20, 2019

[​IMG]

  • Messages File | All messages in the plugin are now configurable. You can even configure hover and click events on any message to your liking. The prefix and invalid permission message have been removed from the config.yml file. You do not have to remove them, however, they no longer work as they are in the new file.
    Code (YAML):
    # This is the Message file for all Custom Jumppads messages.
    #
    # All messages are fully customizable and support color codes, formatting and ASCII symbols.
    # Set the Prefix and use %prefix% to add the corresponding prefix to a message.
    # Leave a message blank ('') to disable it.
    #
    # You can also create messages with Hover and Click events. Syntax options: (Space between comma and quote is NOT allowed)
    #  - ["Message","/Command"]
    #  - ["Message","Hover"]
    #  - ["Message","/Command","Hover"]
    #  - ["Message","/Command","Suggest"]
    #  - ["Message","/Command","Hover","Suggest"]
    # You can add as many events to a message as you want. Example:
    # '%prefix% &cInvalid arguments! ["&c&n&oHelp","/jumppads help","&aClick to get help!"]'
    # The "Suggest" tag is used if the click event should suggest the command. Default is Run.


    Prefix
    : '&7 [&eJump Pads&7 ]'
    Messages
    :
      PlayerOnly
    : ' %prefix% &cCommand can only be used as a Player!'
      InvalidPermission
    : ' %prefix% &cYou do not have permission to do this!'
      InvalidArguments
    : ' %prefix% &cInvalid arguments! ["&c&n&oHelp","/jumppads help","&aClick to get help!"]'
      InvalidTarget
    : ' %prefix% &cJumppads can only be created on pressure plates and slime blocks!'
      InvalidPower
    : ' %prefix% &cYou do not have permission to set <power> above %maxPower%!'
      ConfigurationsReloaded
    : ' %prefix% &aConfiguration successfully reloaded!'
      Created
    : ' %prefix% &aJumppad created!'
      Deleted
    : ' %prefix% &aJumppad deleted!'
      NotAJumppad
    : ' %prefix% &cThe targeted block is not a jumppad!'
      InvalidAttribute
    : ' %prefix% &cInvalid Attribute!'
      AddedAttribute
    : ' %prefix% &aThe attribute value has been set.'
      RemovedAttribute
    : ' %prefix% &aAttribute removed. Using default if any.'
      NotSupported
    : ' %prefix% &aNot supported in this version.'
      UnsafeTeleport
    : ' %prefix% &cThere is no safe destination at the jumppad!'
    The file is automatically generated.

    Suggested by @columb ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Mar 6, 2019

[​IMG]


  • List Command | This version features a new list command accessed with: /jumppads list [page]

    This command will print a list of all configured jumppads and their info in a hover message. There are 8 entries per page. Using the page parameter allows you to open a specific page. The permission for using this command is the jumppads.list permission.

  • Teleport | This update also features a teleport function to the /jumppads list command. When you click on any of the list entries you are able to teleport to any of jumppad. The implementation has been done thoughtfully i.e. when teleporting the plugin will find a safe location at the jumppad (solid block to stand on and 2 air blocks above); it will even make you look at the jumppad!

    The implementation makes use of a "hidden" command (not listed in the help menu), however, it has been implemented in a way that makes it impossible to abuse it. When executing the command it will only teleport you if there is a jumppad within a 1 block range. You can't use it to teleport anywhere in the world by executing the command manually with arbitrary parameters;)

    The permission to use the teleport functionality in the list is jumppads.list.teleport

    Suggested by @mibby; thanks! ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 28, 2019

[​IMG]

  • Fix | The plugin makes sure that teleporting is not allowed when launching, however, if you tried to teleport on 1.8 it would throw an exception due to a slight mistake. The chorus fruit teleport cause is not known in 1.8 as it was first introduced in 1.9. This has been fixed and it will now function correctly on 1.8 as well.

    Reported by @OpvpYT; thank you! :)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 26, 2019

[​IMG]

  • Attributes | Power and Angle have been added as attributes which you can now change with the /jumppads settings power/angle [value] command. Doing that previously involved the create command and setting the angle would require you to first know the power value as to not alter that etc. In other words, it was simply not good enough which is why they have been added to the attribute command.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 23, 2019

[​IMG]

  • Update Checker | You can now disable the update checker if you do not wish to receive notifications of new updates. The following has been added to the config.yml file:
    Code (YAML):
    # Enable or disable the update checker.
    updateCheckerEnabled
    : true
    The default is true. If you wish to disable the update checker you'll have to manually add the option above and set it to false.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 20, 2019

[​IMG]

Please read this update note carefully. Your current jumppad settings will most likely not behave the same way as with previous versions and needs re-configuration.
  • Launch Computation Revised | The launch computation in the prior versions was not very well implemented. The launch velocity was highly dependant on e.g. the angle. Those should not affect each other. E.g. changing the angle should merely make the parabolic curve steeper and reduce the launch length, however, it increased the final velocity launching you farther. It was discovered by @Rocket32 that if you created a jumppad with /jp create 1 90 i.e. a jumppad with power 1 and angle 90 it would launch you sky high even though the power was only one.

    Enough rambling. The launch computation in this update has been totally revised and now reflects your chosen settings and parameters without affecting each other other than what you'd expect. The result of this is incompatibility with previous settings. Once you've replaced the jar you should check if your jumppads still launch correctly; if not then re-configure them.

    Discovered by @Rocket32 ; thanks! ;)
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 18, 2019

[​IMG]

  • Fix | Due to a project structure artifact build error the latest update was not correctly built. This has been fixed and the last update is now correctly integrated into the plugin.

[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 7, 2019

[​IMG]

  • Commands | The main command has gotten quite a few new aliases. Check out the main page to see them all. A few of the subcommands have also gotten new aliases.

  • Clean up | The command setup has been cleaned up. There were quite a few methods that were verbose and could be removed/condensed into more specific methods.
[​IMG] [​IMG]
[​IMG]
[​IMG]
----------, Feb 6, 2019

[​IMG]
  • Improvement | The entity launch checker ran every 5 ticks which were a bit "overkill". I've changed this to once every 10 ticks. This change cuts the resources needed for the entity launch checker in half without any noticeable in-game change i.e. launch latency.

[​IMG]
----------, Jan 18, 2019

[​IMG]
  • Stuck Entities (Major) | On some servers it could occur that entities were not removed correctly trapping players and leaving behind particles. This could result in a number of exploits/issues and has been fixed. This only concerns 1.13.x servers.

  • Flight Fix | If switching between flight enabled/disabled or survival/creative it could occur that your flight ability was disabled. This has been fixed and no longer occurs.

  • CleanUp Fix | A missing check could result in an NPE when checking chunks in a non-existent world.

  • Improved Commands | Prior to this update all commands were only executable in-game. This update allows you to use the help command and reload command from the console.

    Huge shoutout to @mibby for taking the time to test the plugin and find the cases in which the bugs above occurred :)

[​IMG]
----------, Jan 12, 2019

[​IMG]
  • Update Checker | The update checker task will cancel itself if it is unable to check for an update. On some systems or newer Java versions, this could result in a stacktrace every 10 minutes due to a failed check. This will no longer happen.

    Requested by @mibby :)

I have been made aware that there still are a few complications with the plugin on 1.13 servers. Due to exams, I am unable to fix this here and now. I will be looking into it as soon as I can. Thank you for your patience.

[​IMG]
----------, Jan 5, 2019

[​IMG]
  • Fix | A missing null check could result in a quite spammy exception stack. This has been resolved in this update.

    Reported by @DrOreo002 & @Diego_ht; thanks! :)

[​IMG]
----------, Dec 31, 2018

[​IMG]
  • Update Checker | The update checker will now check for an update once every 10 minutes instead of just on server reload/restart. The check is performed async and won't impact performance.

[​IMG]
----------, Dec 29, 2018

Changelog:
  • Fix | There have been quite a few problems with running Jumppads on 1.13 servers. Mainly it was the issue with leaving behind entities when landing and particles sticking. After a lot of testing, I found that 1.13 servers will actually convert the entity into an invisible "block" without truly being a block when landing. I've implemented some extra logic that'll prevent the conversion. Hopefully, this should make the plugin run on 1.13 without issues.

    Thanks to @mibby for providing the error circumstances! :)

    If 1.13 still causes errors please shoot me a PM and I'll take a look at it!

[​IMG]
----------, Nov 9, 2018

Changelog:
  • Fix | Due to the way JumpPads handled resetting fall damage you could by performing certain actions right before landing still receive fall damage. I've changed this completely and players will no longer be able to accidentally receive fall damage.
I am aware that there are still a few issues running JumpPads on 1.13 servers. I am working on fixing these issues.

[​IMG]
----------, Oct 28, 2018

Changelog:
  • Fix | The block the hidden entity is about to enter is now checked. If it is a liquid type the entity is killed and the launch is ended. This resolves the issue where if you were launched into e.g. water, a water block would be turned into air and you could only replace it again using a plugin like WorldEdit.


  • Improvement | The jumppad clean up now runs during startup instead of shutdown. There were a few server freeze issues in 1.13 with this feature but this change should eliminate this issue. (If this is, in fact, the culprit)

    As there are a few issues with 1.13 and JumpPads please contact me if you're experiencing any and I'll take a look!

[​IMG]
----------, Oct 19, 2018

Changelog:
  • 1.13 Fix | Due to some changes in 1.13 a problem regarding reloading and shutting down has irregularly been an issue. The issue seems to have been caused by the JumpPads clean-up algorithm which runs on plugin disable. I've made a few changes and hopefully solved the issue.

    Thanks to @mibby for providing useful info on this issue! :)

[​IMG]
----------, Oct 13, 2018

Changelog:
  • Fix | Due to the implementation of the 1.13 support for particles using the 1.12.2 API this caused an error to be thrown on 1.8 servers. This has also been fixed.

[​IMG]
----------, Sep 26, 2018

Changelog:
  • 1.13 | Custom Jumppads now supports 1.13. All features, to my knowledge, are working except for the launch effect which has been disabled in 1.13. If you get any errors on startup it is most likely a sound enum that has changed in 1.13. If you can't figure it out for yourself please send me a pm or join the discord :)

[​IMG]
----------, Sep 9, 2018

Changelog:
  • Fix: Prior to this update you could use the '/jp set <attribute> [value]' command on any block; also non-jumppads. This caused some pretty nasty and spammy stacktraces. The issue was caused by a missing check which this update adds. I recommend updating as soon as possible.

    Thanks to @mibby for discovering this issue!

[​IMG]
----------, Jul 31, 2018

Changelog:
  • Update Checker: An update checker has been implemented. This will notify you in the console on startup/reloads when a new update is available on Spigot as well as OPs when they join.

    Please note that you won't get notified about this update. Once you've updated to this version you'll get notifications of following new updates.


  • Permission: A new permission regarding the update checker has also been added: jumppads.update

    Players with this permission will get notified of a new update even if they are not an OP.


  • Config Option: Not all OPs on a server has to be notified of new updates as that might not be a part of their "job". Therefore the following has been added to the config.yml file:
    Code (YAML):
    # Update Checker.
    # false: All OPs are notified of a new update when they join.
    # true: OPs are only notified if they have the jumppads.update permission as well.
    # N.B. any user with the jumppads.update permission is notified; OP or not.
    updateCheckerPermissionOnly
    : false
    If you do not wish to change the default value (false) you do not have to add it to your config.yml file.

[​IMG]
----------, Jul 9, 2018

Changes:
  • Fix: Fixed the permission for breaking jumppads. Previously jumppads.create was both used for creating as well as deleting/breaking jumppads. As per 1.10.0 that was no longer the case as jumppads.delete was introduced.

    You will now need jumppads.delete to break jumppads.

[​IMG]
----------, Jun 28, 2018

Changelog:
  • Command Framework: The commands have been totally recoded. JumpPads is now using my latest command framework which is also used in my premium plugins GPS and Pocket Games. The help menu has also been overhauled and now looks like this:
    [​IMG]

    The command framework allows you to easily input commands using aliases. Take this command as an example:
    /jumppads set permission jp.test

    This can now be written in multiple ways such as:
    /jp s p jp.test
    /jp s perm jp.test
    /jp set perm jp.test

    Etc.

    In general, the new framework is useful for everyone.

  • Permission: The new framework also introduces a few new permissions. Previously you would need jumppads.create to use any command at all. This is no longer the case. Permissions have been deligated to each command.

    New permissions:
    • jumppads.help
    • jumppads.delete
    • jumppads.set

  • New Command: The many setSomething commands have been replaced by a single set command. This has been done as the menu was cluttered with the many commands and would only get messier as more are potentially added.

    The new command: (An example can be seen earlier in this update)
    /jumppads set <attribute> [value...]

    You can leave the [value...] parameter blank to remove the attribute.

    Hover over the command in the help menu to see the attributes available.

[​IMG]
----------, Jun 24, 2018

Changes:
  • Fix: The info command showed 0.0 for permission. This has been fixed.

  • Particle: You can now set a custom particle on a jumppad via the /jp setParticle [particle] command. This is only supported in 1.11 and up.

  • Sound: You can now set a custom sound on a jumppad via the /jp setSound [sound] command. Remember to use the appropriate enum if you are using 1.8 or a newer version.
[​IMG]
----------, Jun 13, 2018

Changes:
  • New Command: You can now set individual trail and visualizer colors on each jumppad with this command:

    /jumppad setColor [code ]

    Example:
    /jumppads setColor &a
    This will set the visualizer color and trail color to green. All Minecraft color codes are supported.

    If you execute the command without the [code ] parameter the custom color will get reverted to the default color.

    Suggested by @Mavhill .


  • Teleport Support: If you were launched into a portal you wouldn't get teleported as the plugin blocked all teleports during launch. This has been changed. Teleports with chorus fruits, player commands, and ender pearls are now the only teleports that are blocked. This allows other plugins to teleport you including portals.

    Discovered by @Mavhill .

  • Fall Damage: Increased fall damage invulnerability by a few ticks.

[​IMG]
----------, Jun 10, 2018

Changes:
  • Sound Enums: Sounds exclusive to newer versions are now also supported in their respective version and up.

  • Sound Volume: The sound volume was incorrect and would play the sound multiple hundred blocks in range. This has been fixed and the sound will now be played at a normal volume.

    Discovered by @mibby , thanks :)
[​IMG]
----------, Jun 6, 2018

Changes:
  • Launch Effect: You can now set a launch effect when a player or entity uses a jumppad.
    [​IMG]

    Add the following to your config.yml file:
    Code (YAML):
    # Enable launch effect:
    launchEffectEnabled
    : true
    # Choose an effect to be played here: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Effect.html
    launchEffect
    : EXPLOSION_LARGE
    # Set the duration/data of the effect played.
    launchEffectDuration
    : 5
    The effect is enabled by default so if you want to disable it you will have to add the configuration options and set the launchEffectEnabled to false.

    Suggested by @Toldi :)

[​IMG]
----------, May 16, 2018

Changes:
  • Kicked for Flying: Since the system has been migrated from riding an entity during the launch to no longer riding an entity the server would flag players for flying and kicking them depending on the duration of the launch. This has been fixed and players should no longer be kicked for flying during launch. This has been tested on a server with no anti-cheat, on a server with AAC, and on a server with NCP.

    Discovered by @ICEconchy - thanks :)

  • Improved: During some flight checks, an unnecessary event cancellation was performed. This will simply return without cancellation resulting in a smoother trajectory as well as improved accuracy.

[​IMG]
----------, May 13, 2018

Changes:
  • Permissions: This update introduces a new command. /jp setPermission [permission]. With this command, you can set individual permissions for each of your jumppads. (Players will still need the jumppads.use as well) The command works the same way as the setDirection command. Look at a plate and execute the command.

    Suggested by @__Melowelei__ :)


  • Fix: The direction setting did not work properly for slime jumppads. This has been fixed.

  • Optimized: The jumppad pre-launch checks have been heavily optimized. This goes for both players and entities.
----------, May 11, 2018

Changes:
  • Living Entities: You can now enable entity launching. This means that if a Living Entity (cow, pig, villager etc) walks onto a jumppad they will get launched just as a player would.
    [​IMG]

    This feature is enabled by default. Please add the following to your config.yml file:
    Code (YAML):
    # Should living entities (cows, pigs, villagers etc) get launched also?
    launchLivingEntities
    : true
    If you do not wish to have this enabled you have to add it and set it to false.

  • Sound: The launch sound is now played to everyone instead of just the player getting launched.
----------, May 11, 2018

Changes:
  • Sitting Removed: Finally! This fix/change has been requested by so many of you! So after some critical thinking, this has been fixed. Players will no longer sit down as if they were riding something during a jumppad launch. Players still won't be able to change direction or teleport during a launch. (However, they may slightly impact accuracy by holding a key down. Only by 2-3 blocks)

    During this change, I noticed that the launch may actually have triggered twice. This has also been fixed. This may affect your jumppads launch distance by a few blocks.

    New Preview:
    [​IMG]

  • Event change: The dismount event has been replaced by the entity damage event as it is no longer needed. The damage event cancels the fall damage received after a launch. Previously the damage cancellation was handled by the entity ridden.
[​IMG]
----------, May 6, 2018

Changes:
  • Set Direction: A new command has been introduced with this update:

    /jp setDirection

    With this command, you can set individually fixed directions for each of your jumppads. The command works this way:
  1. Walk up to a jumppad and look at it.
  2. Look in the direction you want the jumppad to launch the player.
  3. Use the /jp setDirection command.
  4. The jumppad will now always launch the player in the direction in which you were looking.
Suggested by @ICEconchy :)
----------, Apr 29, 2018

Changes:
  • Particles: The particle launch trail is now supported for 1.8, 1.9, and 1.10 servers as well.
    This does not include the visualizer.

  • Sound: Sound is now supported in 1.8. Both pre-1.9 and post-1.8 Sound enums are supported.

  • Teleport blocking: Teleport blocking is now supported for 1.8, 1.9, and 1.10 servers as well. This feature prevents players from using enderpearls, teleport by command, or getting teleported by any other source during a launch.

  • Fix: Removed a debug message which was sent to console everytime the /jp info command was used.

Version support features requested by @EwrsPlay :)
----------, Apr 27, 2018

Changes:
  • Enhanced Precision: Prior to this update long-distance jumps had a slight flaw as the players looking direction could affect the distance they would get launched. This was mostly an issue with jumps over 100 blocks though this update also adds a new direction feature where this issue is way more noticeable. Take a look at the gifs below:

    Prior to this update:
    [​IMG]

    Now:
    [​IMG]

    The jump pad is set to a distance equivalent to the location of the redstone block. The player is looking down which will in return affect the jump. If the player was looking straight forward they would get launched the correct distance. This inaccuracy would increase exponentially with the launch power. This has been fixed and the looking direction no longer affects the jump.


  • Direction Option: You can now choose if the jump pad should launch you in the direction you are walking or the direction you are looking. E.g if you are walking sideways onto a jump pad you'll get launched sideways. Though you can now choose to have it launch you in the direction you are looking instead.

    Simply add the following to your config.yml file:
    Code (YAML):
    # Launch direction:
    # true: launched in the direction the player is walking.
    # false: launched in the direction the player is looking.
    launchInWalkingDirection
    : true
    The default is true. If you're happy with the way the jump pads launch you, you do not have to add this.

    Suggested by @Arkobat :)
----------, Apr 26, 2018

Changes:
  • Fix: Disabled the visualizer for 1.8, 1.9, and 1.10. The plugin would throw an error as soon as it tried displaying a particle ring.

  • Fix: If you haven't created any Jump Pads the path "JumpPads" was not created in the jumppads.yml file. This caused a spammy NPE error since the plugin tried getting something which did not exist yet. This has been fixed and the plugin will simply wait till a jump pad has been created.

    You do not have to download this update if you already have created jump pads prior to the previous update.

Sorry for the frequent updates. Missed a few things :)
----------, Apr 23, 2018

Changes:
  • Visualizer: The previous update added support for slime blocks as a valid jump pad type. Slime blocks do not stand out as a pressure plate does hence the reason for this new feature. All jump pads will now have a rotating circle of particles hovering above them:
    [​IMG]

    This is of course highly customizable. Simply add the following to your config.yml file and change the default settings to fit your needs:
    Code (YAML):
    # Visualizer settings:
    # The visualizer creates a hovering rotating circle of particles above all JumpPads.
    Visualizer
    :
      # Enable or Disable the visualizer.
      enabled
    : true
      # Set which type of particles should appear.
      particleType
    : REDSTONE
      # Set the color of the rotating particles.
      # Colorizeable particle types: REDSTONE, SPELL_MOB and SPELL_MOB_AMBIENT.
      particleColor
    : 'red'
      # The max distance the visualizer is visible to the player.
      renderDistance
    : 20
      # The radius of the rotating circle.
      circleRadius
    : 0.5
      # The speed in which the circle rotates. Lower is faster. Minimum is 1.
      rotationSpeed
    : 2
    Even if you choose to not add the configuration settings the default settings are chosen internally and the circles will appear regardless. If you do not want this feature you'll have to add the above settings and set the 'enabled' to false.

    Suggested by @WarnDangerous :)
----------, Apr 23, 2018

Changes:
  • Fix: Disabled the visualizer for 1.8, 1.9, and 1.10. The plugin would throw an error as soon as it tried displaying a particle ring.
----------, Apr 23, 2018

Changes:
  • Slime blocks: Added support for creating jumppads on top of slime blocks. These work the same as regular plate jump pads and can contain the same properties (power and angle).

    Suggested by @WarnDangerous :)

  • Debug: Removed some unneeded debugging from the previous update regarding launch parameters.
----------, Apr 21, 2018

Changes:
  • Angles: You can now set a launch angle on your jumppads. This is optional and will not break existing jumppads. This change might, however, change the launch distance of your current jumppads. Please check that the distance is still correct.

  • Launch perfections: Previously the jumppads would launch you in the direction you were looking. This resulted in if you were, for instance, walking sideways you would get launched in your looking direction instead of the direction you were walking. Another issue was that the launch angle would also be based on your pitch (looking up/down) which resulted in inconsistent launch distances. It is now based on the angle you set or the default value (10) resulting in perfect launch distances every time.

  • Fix: Prior to this update you could only manually edit the jumppads config by stopping the server -> edit -> save -> start. This has been fixed and you can now edit the file manually and simply use the /jp reload command to make your changes take effect.

You do not have to make any config changes to support the new angle feature. If you wish to use it simply go to a jumppad and use /jp create <power> [angle].
----------, Mar 22, 2018

Changes:
----------, Nov 5, 2017

Changes:
  • Improvement - Added the '/jp info' command to the help command.
----------, Oct 21, 2017

Changes:
  • Added - '/jumppads info' command. Look at any jump pad, execute the command and get the exact location, jump pad type, and power value.
  • Added - 'jumppads.info' permission. Grants permission to the new command.
No config changes. Drag and drop JumpPads.jar to apply changes.
----------, Oct 11, 2017

Changes:
  • Update - Replaced 1.12 spigot build with the latest 1.12.2 build.
  • New command - Reload your config changes instantly with '/jumppads reload'
  • New permission - Permission to use 'jumppads reload' --> 'jumppads.reload'
----------, Sep 19, 2017

Changes:
  • Fixed - A small flaw in Particle trails.
  • Fixed - An unhandled sound event in 1.8.
  • Improved - Removed redundant console message on startup.
  • Improved - Made config more foreseeable. (Changes are purely cosmetic)
----------, Aug 30, 2017

Addition:
  • Added support for 1.8.x, 1.9.x. & 1.10.x (Though some features in those
    versions are disabled e.g particles & dismount prevention)
    Make sure to change default launch sound to a sound supported in your version!
Fix:
  • Fixed an error message if using some commands without having created any Jump Pads before.
----------, Aug 16, 2017

Updating?
Updating from 1.1.0 or below? Save a copy of your current config, and let a new one generate.

Additions:
  • Added customizable particle trail on launch with configurable colors and density. Can be disabled in config.
  • Added customizable sound effect on launch with configurable sound. Can be disabled in config.
  • Plugin prefix can now be changed/edited.
  • Added permission 'jumppads.maxpower.bypass' to create jumppads exceeding the power limit.
Fix:
  • Updated some deprecated methods.
  • Reworked some code.

[​IMG]
----------, Aug 15, 2017

Additions:
  • Added Click & Hover events to the '/jumppads' command
    for easier creation, deletion and navigation.
[​IMG]
----------, Aug 13, 2017

Additions:
  • Added [DELETE] button in '/jumppads list'.
  • Added [TP] button in '/jumppads list'.
  • New permissions:
    jumppads.list.delete (Permission to delete from list)
    jumppads.list.tp (Permission to tp from list)
[​IMG]
----------, Aug 2, 2017

- Fixed jittery landing resulting in disconnect. ( Too many packets)
- Disabled teleporting during jump/launch. ( Commands, Enderpearls & from other Plugins)
----------, Aug 1, 2017

- Fixed a bug where you were able to cancel the jump midflight.
- Small optimizations.
----------, Jul 31, 2017

Resource Information
Author:
----------
Total Downloads: 142,642
First Release: Jul 31, 2017
Last Update: Aug 1, 2025
Category: ---------------
All-Time Rating:
101 ratings
Version -----
Released: --------------------
Downloads: ------
Version Rating:
----------------------
-- ratings