Tags
Creators
Details
3.4.1
Compatibility
Changes
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-destructionwas 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
Supplementary resources
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:MJC8WBdk:emZbLxOh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJC8WBdk:emZbLxOh"
}

