Tags
Creators
Details
v1.0.120
Compatibility
Changes
craft fixes for custom item support (third-party modifications to vanilla items)
example: crafting adamantine with a modified echo shard (i.e. an unidentified offering item from offerings plugin) would still craft the adamantine

new config entries
# Paper craft takeover (datapack-only fallback when plugin is not installed).
craft:
# true: PrepareItemCraft sets final loot results; skips datapack pending-paper resolve.
plugin-takeover: true
# true: block all alloys:* recipes in Crafters (one global CrafterCraftEvent listener).
block-crafters: true
add datapack toggle to disable refunding of materials as datapacks cannot read item components to be able to reliably distinguish valid from invalid items for material crafting
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Alloys-ResourcePack.zip | Unknown | 196.51 KiB |
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:PlhRnmGT:veSzuLqa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PlhRnmGT:veSzuLqa"
}

