All versions
0.2.6-1.21.1
Release
Titan Reborn 0.2.6-1.21.14 months ago 230
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Titan Reborn 0.2.6
Additions
- Added Essence effect removal for Swords via Grindstone.
- Added alternative crafting recipes for modded bows and crossbow via smithing table.
- Includes Titan Bow, Titan Crossbow, and Multi Bow.
Gamerules
- Added DisableFireEnchantments (default: true)
- Prevents fire-related enchantments from obtaining and functioning.
- Added ArmorHudOverlay (default: true)
- Toggles the armor HUD overlay.
- Added DisableSwimming (default: true)
- Disables fast swimming mechanics.
Balancing
- Increased Netherite Armor resistance from 10% to 15%.
- Increased Citrin Ore generation slightly.
- Decreased Ember Ore and Titan Ore generation slightly.
Fixes
- Ember Armor now correctly scales fire and lava damage, burn duration, and damage-tick chance.
- Fire and Soul Fire state now resets and renders correctly on client-side.
- Immunity effect is now properly synchronized on client- and server-side.
- Ores now generate correctly outside of chunk borders.
Visuals
- Added colored particles for Citrin Star effect conversions.
- Reworked the Immunity effect HUD overlay for better clarity.
- Reworked the armor HUD overlay to always render armor regardless of applied Plating.
- Backpack preview fill bar calculation and stack merging now render correctly.
EMI
- Removed invalid recipes for smelting.
- Added missing recipe for Multi Bow.
Removed
- Removed Potion Bundle offhand gamerule.
- Removed infinite Soul Fire burning gamerule.
- Removed various Frostburn-related gamerules.
Miscellaneous
- Reorganized creative tab order.
- Various minor adjustment and fixes.
Optional dependencies
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:9K53v0ys:C3w9Fgez"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9K53v0ys:C3w9Fgez"
}


