All versions
1.2.0
Release
Ancient Forgemastery 1.2.0last year 806
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
- Added Remnant Artifact as loot in Ruined Portal chests (16.6% chance).
- Added compatibility for upgradable items between main-hand and off-hand use.
- Added Ember Blossom compatibility with the Domestication Innovation mod
- Added advancement “It Belongs in a Bastion!”, granted when obtaining a Remnant Artifact.
- Added advancement “It’s a Simple Spell, but Quite Unbreakable”, granted upon using an Echoing Ward on a tamed animal.
- Added Ender Pearls use on empty Warping Lanterns as a valid replacement for lost Anchored Ender Pearls.
- Adjusted Echoing Ward summoning so it no longer relies on vanilla taming.
- Adjusted rarity tiers for upgradable items to match vanilla conventions.
- Adjusted the list of entities Echoing Ward can be used on to be more consistent (non-hostile only, unless tamed or renamed).
- Increased Remnant Artifact loot chance in Bastion Treasure chests (33% → 66%).
- Fixed Elixir of Vitality's extra-hearts mechanic not working correctly alongside other heart-modifying mods.
- Fixed Ember Blossom being able to consume Elixir of Vitality after activation.
- Fixed Collection Medallion storing XP past its full capacity when used in off-hand.
- Fixed Collection Medallion item state not updating after upgrade until used.
- Fixed Wardlings' and Wardlets' despawn particles playing even after death.
- Fixed Echoing Ward triggering unintended interactions when used on certain entities.
- Fixed Wardlets forgetting their warded entities after these transform (e.g., villagers → witches).
- Fixed Wardlings' and Wardlets' protection preventing death by the /kill command.
- Wardlings and Wardlets are no longer vulnerable to dragon breath.
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:rciLBWn7:KT8JPVOD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rciLBWn7:KT8JPVOD"
}

