Tags
Creators
Details
3.0.1
Compatibility
Changes
Honeypot 3.0.1
This version fixes a few bugs, and adds preliminary support for Folia. Soon, Honeypot will natively support Spigot, Paper, and Folia, instead of using the Spigot API in its entirety. This will mean it'll perform better on Paper servers, but will still run on whatever you like!
PLEASE NOTE Folia is an experimental server software. While Honeypot does support Folia, in order to do so I had to disable Vault while testing. Vault is still a dependency, and does not support Folia yet, meaning you will not be able to load Honeypot on your server until Vault adds support. However, the good news is that once Vault does add support, Honeypot will be ready and waiting for you! 😁
Core
Additions:
- Complete Folia support. Honeypot will work with Folia as soon as Vault adds support. If you need to use Folia now, please head to my Discord and I can work something out with you! Discord link is in the project's README
Changes:
- Running /hpteleport (An internal-only command) could cause errors in console. This has been fixed
- Fixed a bug where if you spam click an inventory that is a Honeypot (Such as a chest or barrel) fast enough, an item might be placed. (If this still happens for you even after the fix, please create an issue so I can investigate!)
Removals:
- None
Known Bugs:
- None at the moment. If you find a bug, raise an issue!
API
Changes:
- None
Removals:
- Individually packaged API is no longer available
Nerd info
MD5 checksums:
a97fb2fc03ffb687c4001bd1afb6f9abhoneypot-core-3.0.1.jar6587dec2e4262d51f4c646d98b58009ehoneypot-core-3.0.1.jar89f4425bd9bede390e00d7b92244c743honeypot-core-3.0.1.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:b26ztqNj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJC8WBdk:b26ztqNj"
}

