All versions
1.2.3
Release
Bladebound v1.2.310 months ago 37
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Bladebound v1.2.3
⚔️ New Content
🗡️ Soul Split Katana (Legendary Weapon)
- Added the Soul Split Katana, a powerful late-game blade.
- Deals bonus damage that bypasses armor, making it effective against heavily armored enemies.
- Features unique soul-themed particle effects and sound feedback on successful hits.
- Includes full Codex entry with lore and acquisition details.
How to obtain:
- Found in:
- Bastion Treasure chests
- End City Treasure chests
🏗️ World Generation Improvements
Structure Placement Fixes
- Fixed multiple structures spawning underground or floating above terrain.
- Structures now properly carve into terrain and hug the surface naturally, matching intended placement behavior.
- Improved ground snapping logic for consistent placement across slopes and uneven terrain.
Water & Terrain Handling
- Structures now avoid spawning in water-heavy areas where flooding or invalid placement would occur.
- Improved safety checks to prevent broken or submerged spawns.
Village Interactions
- Adjusted placement logic to reduce destructive overlap with existing terrain features and settlements.
✨ Visual & Gameplay Polish
- Refined particle effects for the Soul Split Katana to clearly differentiate them from Black Flash visuals.
- Improved hit feedback using darker, sharper particle effects and sound design.
🛠️ Internal Improvements
- Codex updated with new legendary weapon entry.
- Loot table updates validated for late-game progression balance.
- General stability and cleanup pass on worldgen logic.
⚠️ Note: World generation changes require new chunks to see the effects.
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:njF9D7EO:4NUQjMFB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:njF9D7EO:4NUQjMFB"
}

