3.0.0-BetaE
Compatibility
Changes
Bleach_KD 3.0.0-BetaE - 1.16.5
BetaE of version 3.0.0, aka the 1.16.5 port. A few more fixes, these ones including the Armour renders being fixed, the Russian language file being fixed / added (uses version 2.4.3 language file, so guide will not be accurate yet). Sheathing now works again and the recipes are working in this version (didnt do a data run in previous). Readded Hueco Mundo dimension, it generates a large white sand desert, some code was added to hopefully generate Soul quartz trees but I dont think this works. More work to be done in order to add the underneath and make it feel like a proper Hueco Mundo again, spawn rates have been adjusted as well.
Minecraft will warn you about experimental features, this is because the dimension being json was new to 1.16.5. Click proceed but if worried make periodic backups of your world.
Added
- Added HuecoMundo Dimension & Biome (not finished, but exists)
Fixes
- Fixed Armour renders, report any issues
- Fixed Pendant Item not saving bow correctly
- Fixed & Readded Sheathing with swap hand button
- Fixed / Added Russian language file (uses 2.4.3, so Guide will be incorrect for current version)
- Fixed Recipes not working (data wasnt generated before release last version)
!!! WARNING !!!
This is a beta, some features may be removed, missing, not working correctly or incomplete. Report any and all problems/differences noticed in my discord. Multiplayer has not been tested in any way, attempt at own risk.
Current Potential Issues
=============
- Hueco Mundo incomplete
- Music Discs have been removed (temporarily)
- Some armours may not render correctly
- Several Configurations removed (temporarily)
- Entity spawns have default values and category spawns (eg MONSTER vs CREATURE)
- Flying Hollows are locked to ground
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:5BcVaIsq:iYn2tFj8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5BcVaIsq:iYn2tFj8"
}

