Links
Tags
Creators
Details
1.0.2
Compatibility
Changes
- Fixes issue where renaming a beacon to anything containing waystone would create a waystone and vice versa.
- the plugin doesn't throw an IllegalArgumentException on load anymore
⚠️ NOTE: Due to changes in the way the custom items are handled the plugin won't be able to recognise waystone items that have been crafted, but not yet placed in version 1.0.1 after the update to version 1.0.2. This only affects the waystone item in inventories, chests, etc., not the waystone block that is placed in your world. It is recommended to place crafted waystones down, update, and then after restarting the server break the waystone block to ensure they stay waystones.
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:P9hapbJh:1mOLBsMT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P9hapbJh:1mOLBsMT"
}

