Tags
Creators
Details
All versions
3.1.1
Beta
Honeypot 3.1.13 years ago 92
Compatibility
Minecraft: Java Edition
1.20–1.20.4
1.19.x
1.18.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
What's Changed
- Optimized some events that may have caused lag on older hardware or shared hosts.
- One of those events was BlockFromToEvent, which was to help prevent water and lava from breaking Honeypots such as torches. This event is now part of the "extra" events in config, and is off by default. If this is left off, the Ghost Honeypot Fixer will come in and, at every interval you set in the config, will check if any Honeypots are water or lava. If so, it's assumed that water destroyed a Honeypot and the block will be removed from the DB. The drawbacks of this are that water can destroy certain Honeypots now, but the benefits are a very noisy event is no longer fired
- The other event that was modified was InventoryMoveItemEvent. This event is what handles processing hopper and dropper moves to/from an inventory. This is a very noisy event as well, and as a result can fire thousands of times a second. I've done what I can to optimize this event as well. On shared hosts or hosts with older hardware, however, this event can still be an issue. I've done Spark profiler tests and Timings checks (Even though Timings is deprecated and isn't accurate per the Paper team), and it seems to be better, but if server owners continue to have issues let me know! I'm still working on optimizing this, and have reached out to folks that know better than I for assistance as well.
- Migrated build system from Maven to Gradle (Resolves #166)
New Contributors
- @SandwichBtw made their first contribution in https://github.com/TerrorByteTW/Honeypot/pull/167
Full Changelog: https://github.com/TerrorByteTW/Honeypot/compare/3.1.0...3.1.1
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:xVKLNFoZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJC8WBdk:xVKLNFoZ"
}

