Tags
Creators
Details
2.4.2
Compatibility
Changes
Bleach_KD 2.4.2 - 1.12.2
Many new blocks for decoration, some more server specific additions to allow more customisation and many fixes to progression that also allow higher levels of powers to be unlocked and obtained. No visual changes for these and boosts may be unnoticable at this stage of the mod but will be in future. Updates to the guide books to reflect these changes and removed some features due to spam attacks and abuse, not bugs, but more exploits.
Additions
- Added "setSchrift <User> <number>" command
- Added Activatable Segunda
- Added Activatable Vollstandig Schrift
- Added Item saving for most Quincy bows
- Added new Las Noches Tile blocks w/slabs
- Added multiple Edge block types
- Added many Sokyoku block variants
- Added a Per player semi-hardcore mode option via commands
- Added config restriction for activating certain powerups
Changes
- Removed offhand damage with Zanpakuto/Shikai/Bankai/Seeleschneider/Spirit Weapons
- Changed SP buff when Bankai is active
- Updated Guidebook for Bankai, Segunda & Vollstandig
- Updated Guidebook for new commands
- Changed function usage for Plant Shikai, crash fix attempt
- Updated guide wording for Zanpakuto in Shinigami guide
- Summoned Sprites (aka Plant Shikai) now have limited life and despawn if deactivating powers
Fixes
- Fixed Bankai Blade attacking the user instead of target
- Fixed offhand bonus damage with spam attack
- Fixed Arrancar Undershirt/Nnoitra Collar option
- Fixed Leztz Cross infinite duplication
- Fixed Zanpakuto default resets
- Fixed Mastered Bankai being unobtainable
- Fixed Mask level 3 not unlocking
- Fixed reset commands not resetting Shikai & Bankai elements
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:lo95ZrCk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5BcVaIsq:lo95ZrCk"
}

