Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 3 months ago
All versions
1.21.1-3.10.0+neoforge
Beta
SummoningRituals-NeoForge-1.21.1-3.10.06 months ago 33
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Note: This release reworks the block pattern condition. It's no longer part of the main condition system. Refer to the wiki for an updated syntax.
- added rotation awareness to the block pattern condition
- added option to add optional tooltip lines to the block pattern condition
- added block pattern preview cancellation when player is too far away from the Altar
- added a dedicated failure message if the block pattern is not correct when starting the ritual
- added highlights for wrong blocks when trying to start a ritual
- added option to add an optional block pattern extension that can be used to modify logic on additional blocks not required for the ritual to work
- add config option to make block pattern preview checks block state aware
- improved type info for KubeJS builder methods returning the same instance
- moved recipe inputs and outputs to container classes for better maintainability
- changed the component column count in block pattern tooltip from 4 to 8
- changed inner key of moon phase condition from
phasetomoon_phase - changed some recipe component key to optionals, so they can be omitted from the JSON
- decoupled the block pattern condition from the loot condition system
- removed the utility methods for obtaining the block pattern condition in favor of the dedicated field in the recipe
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:19smZ71v:no9ThdWM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:19smZ71v:no9ThdWM"
}

