Links
Tags
Creators
Details
1.5.9
Compatibility
Changes
e5b2f5e Geyser Integration is here at last :D
- Solved #14 by PGRjoystick. Only took 3 months because like my pc was stolen, but whatever, Geyser should work with the plugin.
- For anyone who's ever gonna make a plugin, Geyser (or is it floodgate?) saves Bedrock usernames with a
.in front, so Bukkit hates that and makes everything not work - OH AND you can now place blocks on top of the deathchest if sneaking, BUT as i'm not a good developer, you can still access the chest even if covered on top :)
Enjoy, I really doubt I'll be doing much more for the time being, and I know no one reads these changelogs, but still I like making these. Like yk, sometimes you feel like you have many things you want to say out loud, and when you do it, it just feels great.
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:kdfRxKkQ:JGqC8enJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kdfRxKkQ:JGqC8enJ"
}

