Tags
Creators
Details
5.1.2
Compatibility
Changes
Honeypot 5.1.2
Honeypot 5.1.2 fixes a single bug in the /honeypot list command that was accidentally introduced in 5.1.0. /honeypot list sorted blocks based on distance from the player, but used Location::distanceSquared(), which throws an exception if the Locations are in different worlds. The sorting mechanism didn't account for this, sorry about that!
Core
Changes & Additions:
- The
/honeypot listcommand now includes the world name
Bug Fixes:
- Fixed a bug where
/honeypot listand the List GUI option failed if Honeypots existed in worlds the player was not currently in. This also meant that if Honeypots existed in multiple worlds, this command would always fail Removals: - None
API
Changes & Additions:
- None
Bug Fixes:
- None
Removals:
- None
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:luBJP5HN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MJC8WBdk:luBJP5HN"
}

