Tags
Creators
Details
1.2.4-beta
Compatibility
Changes
Features added:
-
Javascript expressions with PlaceholderAPI as ritual conditions. This should allow for any custom conditions you want as long as there's a placeholder for it. Requested by SilentAssassin9.
-
Option to disable restricting shrines to certain players. Add
all-players-can-interact-with-shrines: trueto your config.yml. Requested by KidoAkira. -
Option to run a list of commands when an offering is accepted. Refer to the wiki for the updated syntax. Requested by Yash Pandey.
This should also address some of the issues that were happening with rituals. Next update I'll get database support implemented.
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:bYjKAJ0a:IbIlqeTl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bYjKAJ0a:IbIlqeTl"
}

