Tags
Creators
Details
0.2.3+Fabric-26.4
Compatibility
Changes
0.2.3 introduces gem modification and 70 gem weapons to Runeforged, alongside expanded Celestial crafting and improvements to affix interactions, equipment ratings, and item tooltips. Gem Modification:
- Added Charged Obsidian, Charged Amethyst, Charged Lapis Lazuli, Charged Ruby, and Charged Emerald for modifying Common or Magic weapons and armor.
- Different gems affect main-affix strength, value limits, and affix capacity.
- Charged gems can be crafted or obtained as drops, and naturally generated equipment can also come with a gem modification. Gem Weapons:
- Added 70 gem weapons across five gem materials and all seven weapon types, available in normal and Charged tiers.
- Gem weapons feature inherent gem affixes. Ruby, lapis lazuli, amethyst, and emerald weapons deal Fire, Frost, Lightning, and Holy base damage respectively, while obsidian weapons retain Physical damage but have higher durability.
- Normal gem weapons are crafted with matching mineral blocks, while Charged weapons use matching charged gems. Celestial Crafting:
- Added the Celestial Reforging Stone, which preserves one of the highest-tier main affixes when reforging equipment.
- All eight Rune-Cursed archetypes now support crafting with Celestial currencies, strengthening fixed-tier affixes and granting additional bonuses to selected archetypes. Other Improvements:
- Recalibrated panel DPS ratings and added rating support for all gem weapons.
- Fixed issues with affix compatibility, Infusion conflicts, and Legendary affix rerolling, along with incorrect restriction tooltips on equipment with sealed fixed affixes.
- Improved equipment names, colors, and crafting previews, and updated related text across all 12 supported languages.
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:Co8e7VJI:sIJTQbym"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Co8e7VJI:sIJTQbym"
}

