Tags
Creators
Details
3.0.2
Compatibility
Changes
Honeypot 3.0.2
This version adds a new %world% placeholder for custom actions. It also removes the Vault requirement, and instead soft-depends on it, allowing you to run this in Folia servers without issue.
PLEASE NOTE Folia is an experimental server software. In order to make Honeypot run on Folia, I had to move Vault from a hard to soft dependency. This means that, without Vault, you cannot use custom actions of type permission. This is the only caveat!
Core
Additions:
- %world% placeholder for custom actions. The %world% placeholder will be replaced by the name of the world the block was broken in. For example, if broken in the default Nether, it will say
world_nether.
Changes:
- Vault is no longer required. If not installed, permission custom actions won't work, but that's the only thing that will stop functioning :)
- Config version has been increased to 16. The %world% feature was a suggestion in my discord, so I'm crediting the suggester accordingly. If you want to be included in the credits, be sure to suggest a feature, report a bug, or translate Honeypot to your native language!
Removals:
- None
Known Bugs:
- None at the moment. If you find a bug, raise an issue!
API
Changes:
- The #process event within the abstract BehaviorProvider class no longer marks the
blockas @Nullable. This was part of the original design just in case a block wasn't necessarily passed to a provider, but later I wrote the internal code to require a block to be passed before a behavior is processed. This result in this annotation not only being unnecessary, but also contextually wrong. This won't affect your builds, by the way :)
Removals:
- None
Nerd info
MD5 checksums:
d9bd5aa5876977856107abfd77acb2d3honeypot-core-3.0.2.jar05654bb2f17c0f8bb764b5d57934e87ehoneypot-core-3.0.2-javadoc.jar0866d4954cbd69669d830c8bc712c52ehoneypot-core-3.0.1-sources.jar
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:io6Njp64"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJC8WBdk:io6Njp64"
}

