Honeypot 3.5.1

Version 3.5.0 has been pulled due to 2 somewhat critical bugs pertaining to the Caching System and Double Chests. Version 3.5.1 has no breaking changes from 3.5.0, and it's recommended you IMMEDIATELY update as soon as possible. Version 3.5.0's notes are at the bottom:

Core

Additions:

• Added a new warning in console on startup that will output a warning if the version of Honeypot being ran has been pulled from GitHub (And, by proxy, Hangar and Modrinth)

Bug Fixes:

• Fixed a bug in the Caching System which would store Honeypots in memory with no way to "remove" them without either filling the cache with "new" Honeypots or rebooting the server.
• Fixed a bug with the /honeypot remove command where it would attempt to remove the targeted block instead of the actual Honeypot block when the block is bisected (double chest, doors, beds, etc.)
• Fixed a bug where, when use-inventory-click was enabled in Config, clicking within a Double Chest would throw a ClassCastException in console.
  • The DoubleChest class is the only class in Paper that doesn't implement Container but instead extends InventoryHolder. There is so much custom logic just for DoubleChests because they don't follow the standard. Woo. Hoo.

Changes:

• The Honeypot Cache is now cleared on /honeypot reload should anything go haywire. This also allows you to disable caching on the fly by setting the cache value to 0 in config, then reloading.

Removals:

• None

Honeypot 3.5.0

Hi everyone! I'm back with another small update to Honeypot, but it fixes some critical bugs and improves the plugin a little bit. I hope you are still enjoying Honeypot! Testing of the last few versions has proven successful, so this version brings Honeypot out of Preview and back into Stable again!

Please read

As part of this update, the way the Chat Prefix was handled has been changed. You are not required to change your prefix, but you should add a space at the end. The plugin used to prepend a character automatically after the chat prefix anywhere used in code, but now since the is after the prefix in the translation, if you don't add a at the end of your prefix, your messages will be smashed against the prefix. Heads up!

Core

Additions:

• None

Bug Fixes:

• Fixed a bug where the Locate GUI object would throw an error. Resolves #211
• Fixed a bug where messages in custom Honeypots would send to the player a string representation of the TextComponent instead of the actual formatted text. Resolves #212
• Fixed a bug where Double Chests would not trigger Honeypot actions. Merges in #208 with changes
  • This has been extended to Doors and Beds as well since they are also bisected.
• Fixed an incorrect warning about running Folia on non-Folia servers when the server starts

Changes:

• Removed usage of /hpteleport everywhere in Honeypot. When teleporting to blocks using the Honeypot GUI, internally a fake command /hpteleport was forced to be ran by the player, and subsequently intercepted and cancelled. This was to allow teleporting of players who didn't have /tp access. This was also....really stupid. The plugin now uses the proper APIs to teleport the player instead of psuedo-commands.
  • Fun fact! The only "vulnerability" Honeypot has ever experienced was surrounding this command. Before it was patched, if you ran /hpteleport as a player, you could teleport anywhere in the world without permission, without anyone knowing. It wasn't even output in console. I'm very glad this fake command has been removed.
• Use the Spigot Library Loader instead of compiling libraries directly into the plugin. I discovered this thanks to Restitutor, who also created PR #210. This drastically reduced Honeypot's file size to just 231.39 KB!
• Increment version number of all languages by one to fix an issue where <reset> being at the end of the chat prefix no longer deserializes properly, resulting in the rest of the message formatting not actually being reset properly

Removals:

• None

API:

Bug Fixes:

• Fixed a bug where the #isHoneypotBlock() method of Storage Providers would return false for bisected blocks in which the other part of the block was a Honeypot. For example, if the top half of a door was a Honeypot block and #isHoneypotBlock() was called on the bottom half, you'd get false instead of true.

Additions:

• None

Changes:

• None

Removals:

• None

Honeypot 3.4.1

Honeypot 3.4.1 fixes a few small bugs that snuck their way into 3.4.0.

Core

Additions:

• None

Bug Fixes:

• Fixes a text formatting glitch with certain commands caused by implicit #toString() conversion on Components. Fixes #203
• Fixed a bug where allow-player-destruction was ignored when the player had certain permissions

Changes:

• None

Removals:

• None

API:

These changes are bleed-over from 3.4.0. I'm keeping them here as it's important for developers to see it! :)

PLEASE READ

If you are a developer and have written plugins for Honeypot, please know that they will no longer be supported as of 3.4.0. You will need to do some minor refactoring. Specifically, a new Registry class is available in the API to interact with the Behavior Registry and the new Storage Provider Registry. The TL;DR is: Anywhere you use Honeypot.getRegistry(), change it to Registry.getBehaviorRegistry(). Documentation will come for this new API, I'm working on writing it with Writerside now, and it will be published on a pretty website :) Documentation is now available here!

Additions:

• Support for Storage Provider. Honeypot can now add 3rd party storage providers if PDC or SQLite aren't suited for you. However, do note that Honeypot is not written for asynchronicity in mind, so for now storage providers should be synchronous. Network access in your storage provider is not recommended.

Changes:

• Refactored some classes. Imports will need updated

Removals:

• None

IMPORTANT

As of Minecraft 1.21, Java 21 is required for Paper to run. Plugins can use Java 17 still and that was Honeypot's goal. However, due to certain dependencies being updated to require Java 21 (WorldGuard), I cannot develop on Java 21. Therefore, you MUST run Java 21 as well!

As noted n the previous release, Honeypot as of this version does not support Spigot. Paper is, by far, the most widely used and performant server platform. It's no surprise that it's so widely used either: Paper provides users download links, Spigot requires you to build from source which requires quite a bit of technical know-how. That alone will cause people to gravitate towards it, even if they don't realize that Paper is vastly more performant. Paper is making a hard fork at some point in the future, meaning they will be diverging from the Spigot API, and then I'd have to maintain two versions of the plugin, each with potentially differing feature sets depending on the API availability. Folia is supported currently, but the difference between Folia and Paper is very minute (For the technical people, all I had to do was write a custom Scheduler implementation that utilizes Folia's scheduler instead if the plugin detects it is running on it, otherwise it uses the default Spigot/Paper one). According to bstats, as of typing this only one server is utilizing Spigot anyway.

For these reasons, I have killed support for Spigot and moved fully over to the Paper APIs. If you want to use Honeypot and you are using Spigot, you will need to migrate to Paper. For 99% of users this will be a simple drag-n-drop of the Paper jar in-place of your Spigot jar, no other changes should be necessary. The regular changelog is below! 😄

---

Honeypot 3.4.0

Honeypot 3.4.0 is a MASSIVE rework of many features, internal APIs, and contains several bug fixes and feature improvements.

Core

Additions:

• Adds /honeypot migrate. "Fixes" #188
• Adds support for custom storage providers

Bug Fixes:

• Fixed a bug that caused Honeypot to crash if PlaceholderAPI and Vault weren't installed, even though these are optional dependencies. Fixes #191
• Fixed a potential bug where there was a possibility of Honeypot blocks triggering within areas protected by other Claims plugins (GriefPrevention, Lands, WorldGuard). Fixes #192
• Fixed a bug which caused custom Honeypots defined in honeypots.yml to not be able to trigger their commands.

Changes:

• Changed the way Honeypot Blocks are stored in SQLite and PDC.
  • This change has made Honeypot queries and lookups quite literally almost 100% faster. From testing, Honeypot went from taking 22.36% of the tick time to only 0.21%, which comes out to a 97% reduction in processing times. This was done by migrating SQLite to spatial indexing which allows "querying" in 3D space, and migrating PDC to use the native Location#distance() function within the API. To put this into perspective, SQLite and PDC both can now query a 2,000,000³ area (That's eight QUINTILLION blocks) in only a few milliseconds. Before this change, it was impossible to query anything larger than a 10³ or 20³ without locking up the server. Yay for optimization (And also not doing DB queries the stupid way)! Fixes #187
• Other minor performance changes and enhancements

Removals:

• Spigot support

API:

PLEASE READ

If you are a developer and have written plugins for Honeypot, please know that they will no longer be supported as of 3.4.0. You will need to do some minor refactoring. Specifically, a new Registry class is available in the API to interact with the Behavior Registry and the new Storage Provider Registry. The TL;DR is: Anywhere you use Honeypot.getRegistry(), change it to Registry.getBehaviorRegistry(). Documentation will come for this new API, I'm working on writing it with Writerside now, and it will be published on a pretty website :)

Additions:

• Support for Storage Provider. Honeypot can now add 3rd party storage providers if PDC or SQLite aren't suited for you. However, do note that Honeypot is not written for asynchronicity in mind, so for now storage providers should be synchronous. Network access in your storage provider is not recommended.

Changes:

• Refactored some classes. Imports will need updated

Removals:

• None

IMPORTANT

As of Minecraft 1.21, Java 21 is required for Paper to run. However, plugins can still be developed using Java 17, so Honeypot will still be built on that version to support older server software (I always develop for the latest version though, so I'd highly suggest using 1.21 with 3.3.2!).

However, with this version also comes an announcement: Honeypot, as of all future versions (3.3.3+), will no longer support Spigot. Paper is, by far, the most widely used and performant server platform. It's no surprise that it's so widely used either: Paper provides users download links, Spigot requires you to build from source which requires quite a bit of technical know-how. That alone will cause people to gravitate towards it, even if they don't realize that Paper is vastly more performant. Even though I support Spigot and develop against it, I've actually been exclusively using Paper to test when I create updates. Paper is making a hard fork at some point in the future, meaning they will be diverging from the Spigot API, and then I'd have to maintain two versions of the plugin, each with potentially differing feature sets depending on the API availability. Folia is supported currently, but the difference between Folia and Paper is very minute (For the technical people, all I had to do was write a custom Scheduler implementation that utilizes Folia's scheduler instead if the plugin detects it is running on it, otherwise it uses the default Spigot/Paper one). According to bstats, as of typing this only one server is utilizing Spigot anyway.

For these reasons, I will be killing support for Spigot and moving fully over to the Paper APIs. If you want to use Honeypot and you are using Spigot, you will need to migrate to Paper. For 99% of users this will be a simple drag-n-drop of the Paper jar in-place of your Spigot jar, no other changes should be necessary. The regular changelog is below! 😄

---

Honeypot 3.3.2

Version 3.3.2 brings the plugin out of its SNAPSHOT state since testing of the 3.3.1 feature set is complete. It also adds support for Discord webhooks so you can be proactively notified if any Honeypots are triggered while you aren't online.

Core

Additions:

• Added Discord Webhook support. Simply enable the new discord setting in config.yml, paste your Discord Webhook URL, and state whether or not you want notifications for all block breaks (onbreak) or just when action is taken (action).
  • Do note, this is using OkHttp3 from Square, and during testing I noticed that it was taking nearly 1 second for these requests to be made and would "freeze" the server until the request was sent (See screenshot below). Due to this, I've designed Honeypot to create a separate thread each time a notification needs to be sent to prevent blocking the main server thread. If, however, you notice lag, please let me know and provide me with a Spark profiler export so I can check. Please be sure to do /spark profiler start --thread * so I can see everything happening, not just the single server thread.

Changes:

• None

Removals:

• None

API:

Additions:

• None

Changes:

• None

Removals:

• None

Version 3.3.0 is being re-released as 3.3.1 to fix a bug relating to /honeypot create failing in GriefPrevention areas. It also adds translations for Chinese (Simplified). Thanks, @HaHaWTH! I'm still considering this a snapshot

---

Honeypot 3.3.1

Please see the note at the bottom of this release!

This update brings a feature that was recommended in my Discord a while back, and is finally being released: The type field in the history command. Previously, Honeypot only logged breaks when an action was taken, not if the break was just counted. Now, Honeypot counts each break AND will list whether or not it was a prelimBreak or a break. prelimBreak indicates the block was broken but no action was taken. The block may or may not still exist based on permissions of the player or config options. It also fixes a bug regarding the /honeypot history query command and refactors large parts of the code.

Core

Additions:

• Added a type field to the Honeypot History table. This allows admins to see when players attempted to break blocks, as well as when action was actually taken.

Changes:

• Fixed a bug in /honeypot history query where the command would just return random values from the table instead of the most recent values in descending order.
• (Internal change) Refactored the plugin to use Dependency Injection, which will make the plugin easier and faster to develop. It also has the benefit of potentially making the plugin slightly faster and more efficient since it's not newing a ton of crap every 5 seconds!
• (Internal change) Because this version of Honeypot changes the DB schema, I've implemented a SQLite versioning system within the plugin. This will allow me to add patches at any point in time should I need to add a feature that requires a SQLite DB schema change.

Removals:

• None

API:

Additions:

• None

Changes:

• None

Removals:

• None

---

The SQLite patching system I've written has been mostly tested, but I'm still not 100% about it, more like 98%. Due to this, I'm marking this a pre-release until I finish testing the weird one-off scenarios. If you want to upgrade the DB manually so you don't have to fear anything, here are the two commands you need to run in some SQLite DB explorer!

ALTER TABLE honeypot_history ADD `type` VARCHAR NOT NULL default 'prelimBreak';
PRAGMA user_version = 1;