Tags
Creators
Details
Licensed ARR
Published 9 months ago
Updated last month
All versions
2.1.5
Release
Sengoku Jidai Mod 2.1.5last month 5,466
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
2.1.5.1
Follow-up patch from a few days ago, making sure all Better Combat bugs are gone and added some new stuff while I was at it.
🌸 New Biome: Prevernal Meadow
- Semi-snowy version of the Meadows/Plains.
- Figured while I messed with the Summer > Autumn biomes, I'd mess with the Winter > Spring biomes.
- This biome will sit along the new Prevernal biome category along with Windswept Forest (Now Prevernal Forest) and Windswept Hills (Now Prevernal Bamboo Grove).
- All "prevernal" biomes have been rearranged in the biome spawns to better match their neighboring biomes.
- Made the Winter > Spring transitions even smoother.
🏯 Structures
- All Overworld Structure Sets now use a frequency reduction system so they won't be as overabundant as before.
- Large Surface Mineshaft spawns in more mountainous areas.
🔧 Misc
- Updated Russian Translations
- Shide recipe now requires Lapis Lazuli.
- Certain Trees bleed into other biomes to make transitions feel smoother.
⚠️ Important
- Do not use the latest version of Sodium; it has beef with Polytone, which is a dependency for this mod. I am not a Polytone dev, so I can't do anything about it.
- Do not use the newer versions of Polytone; they done fucked up my bamboo models.
- If you are using Better Combat and the animations aren't working, use
/tag @p remove bettercombat_disabledto re-enable Better Combat. If you noticed it stopped working again after restarting the client, let me know.
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:I1r0dZiV:uL0ovPRO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:I1r0dZiV:uL0ovPRO"
}

