Tags
Creators
Details
1.20.1-1.1.0
Compatibility
Required content
Changes
Bugfixes / Mechanics Changes
Target focus has been moved from the Shift key to a dedicated keybind (Left Control by default).
Fixed a Sharingan self-damage bug: damage from your own techniques is no longer registered as an attack you need to dodge or focus on. The Fire Destruction technique no longer sets the caster on fire when used.
The Medical Scroll now accounts for currently equipped eyes. A tier list from the strongest MS (Mangekyou Sharingan) to the weakest has been added to the website to determine the resulting EMS (Eternal Mangekyou Sharingan).
The Medical Scroll now supports combined eyes (hybrids can now also be upgraded to EMS).
Rebalanced trades with the Konoha Merchant / Shinobi.
The Konoha Merchant / Shinobi can now naturally spawn in the open world.
Weapon rebalance: certain weapons are now unbreakable (no longer lose durability).
Tweaked casting particles for several techniques (currently only for Fire Style).
Susanoo now correctly drains chakra and consumes eye durability.
Samehada (as an entity) received an increase to both HP and damage.
TECHNICAL CHANGES: Reorganized the project's folder structure.
Rewrote READ_ME_BEFORE_PLAY. Several steps are now more detailed, and explicit update instructions have been added.
Added
3 functional Sage Artifacts + 1 placeholder base.
Prepared the backend foundation to transition from element-based items to a full GUI/UI system.
Added the "Uchiha House" structure (narutomod:uchiha_house) to allow awakening EMS in singleplayer mode.
Started developing new structures Further server-side optimizations for Pain.
Lightened rendering load for certain particles by transitioning them to AAA Particles.
Started reworking the visual effects for Water and Wind Style techniques. Ongoing development for Wood Style techniques.
Started reworking the Jinchuriki UI and the technique selection menu.
Compatibility: 1.1.0 is fully backward compatible. Worlds created on versions 0.6.2 through 1.0.0 will not be affected.
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:fNR6d0ai:CahkTVF7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fNR6d0ai:CahkTVF7"
}

