Apologies for the delay, I've been busy doing other things and it took a while to get some confidence in these changes.

This also includes changes from 2.1.0 which I forgot to properly release. As with any new release, please look at the new default config and update yours with any new settings.

Known Issues:

• Whenever StayPut redirects a teleport, big red warning text appears from Multiverse about the teleport being messed with. I'm not sure how to avoid this at the moment, probably going to have to ask the MV devs.

Features:

• Multiverse 5 is now supported. StayPut no longer supports Multiverse 4. Like Multiverse 5, this release is compatible with 1.18 and up. 1.17 and older are no longer supported. If you needed some fixes for an older server, open an discussion.
• Checking if a teleport is near a spawn is now done with a threshold, spawn-detection-threshold in your settings. 0 keeps prior behavior. 1 is recommended as it solves some strangeness with MV5 (MV devs, for some reason flying and jumping messes with a player's destination when teleporting to world spawn).
• Multiverse 5 offers slightly more information about a teleport and StayPut will use that to try to make a more nuanced decision of whether to interfere.
• Added some extra debug logging to help solve issues with blacklisted worlds

Bugs:

• Fixed an issue where a teleport without a destination might cause a crash
• Reduced some debug console spam by ignoring UNKNOWN type teleports
• Fixed an exploit where quitting from the death screen would not reset your location

Build:

• Removed the rest of ormlite (the old database library used before 2.0.0)
• Updated Kotlin to 1.9.22, Spigot minimum version to 1.18

This update contains some important changes! If you are coming from an older release, the tl;dr is

1. The config file changed a bit, make a new one from the template.
2. Large database changes, please back up your database. Discuss problems here.

This release brings the long awaited database overhaul, which fixes some previous issues with duplicate location entries for good and brings support for world groups. This is mostly handled automatically and it should work now, but it's recommended to back up your database. Migration will occur over time as players teleport between worlds and update their locations. Completing the migration requires some admin intervention. You can read all of the details here.

Changes:

• Rewrote all database code in plain SQL/JDBC
• Fixed connection issues with MySQL and newer versions of Java
• Added initial world group support
• Slightly changed config file format
• Fixed death logout loophole (#24)

Thank you to all of the users who helped test the database migration and to my Discord for helping me test!

• Fixed an issue where setting a world's spawn with Multiverse would result in teleports to that world never redirecting to the last location.
• Fixed an issue where StayPut would incorrectly redirect teleports within a world

Sorry for the update spam everyone, supporting all teleport events exposed a number of oversights on my side. Thank you everyone who has been reporting issues and testing things for me!

Sorry about the wait but it's finally here!

This update adds support for Multiverse-Portals. This was contributed by PixeLInc so thank you very much to them! If you have a good idea or can fix a bug, I'm open to contributions. File an issue on the GitHub repo and send me a pull request.

This update also fixes an issue with duplicate DB entries. If you were using a MariaDB/MySQL server, you probably noticed that the plugin made a lot of duplicate entries for the same player and world. This update should fix all that.

To remove duplicate rows, remove all rows that have the same username and world name except for the row with the lowest ID number. So for example, if I have three rows for the user pmdevita in world survival with IDs of 3, 17, and 80, I would remove the rows with ID 17 and 80. 1.2.1 update automatically takes care of this.

Thanks for using StayPut Remixed!