Tags
Creators
Details
3.0.3
Compatibility
Changes
Honeypot 3.0.3
This version fixes some bugs around the block break listener, and also changes some core behavior of the block break functionality
Core
Additions:
- None
Changes:
- The
allow-player-destructionvalue in config.yml now determines if action is taken at all. If allow-player-destruction is set to true, action will only be taken if A)blocks-broken-before-action-takenis <= 1, or B) the player has reached theblocks-broken-before-action-takenvalue. This allows Honeypots to be broken without triggering events, if the staff still choose. If you hadblocks-broken-before-action-takenset to 1 or less and/or hadallow-player-destructiondisabled, this won't affect you. If it was set to a greater value and you had player destruction enabled anyway, then this WILL affect you, as your Honeypots will silently disappear upon breaking.
| Allow Player Destruction | Blocks Broken Before Action Taken | Are you affected? |
|---|---|---|
| True | <=1 | No! |
| True | >1 | Yes, this change affects you! |
| False | <=1 | No! |
| False | >1 | No! |
- Fixed some issues with the Honeypot break logic. It wasn't all inclusive, and some edge-cases would allow certain players to break blocks without punishment.
- Added more detailed logging to Honeypot. If
enable-loggingin config is enabled, honeypot.log will include all debug, info, warning, and severe messages. Console will always include info, warning, and severe messages regardless.
Removals:
- None
Known Bugs:
- None at the moment. If you find a bug, raise an issue!
API
Changes:
- None
Removals:
- None
Nerd info
MD5 checksums:
730d53cc77f90427fa5c83b5685e0e20honeypot-core-3.0.3.jar3125da1a01b32a21cae95bdbf52463dehoneypot-core-3.0.3-javadoc.jar46d61e6ff0b3965fda8883e03c671948honeypot-core-3.0.3-sources.jar
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:arx3scHr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJC8WBdk:arx3scHr"
}

