Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 10 hours ago
All versions
1.21.1-0.1.0
Release
New Shinobi Era 0.1.010 hours ago 12
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Added
- Six Mangekyo Sharingan variants for Itachi, Sasuke, Obito, Madara, Shisui, and Izuna. A random variant awakens once when a tamed pet dies within 10 blocks of its owner while the owner is wearing a regular Sharingan.
- Each variant has its own abilities. These include Amaterasu, Hinokagutsuchi, Tsukuyomi, Kamui, Intangibility, Rewind, Time Freeze, Kotoamatsukami, and Susanoo.
- Kamui teleports the caster or a selected target to a separate dimension and remembers their return point. Susanoo can be summoned and ridden. It has four stages, including a full form.
- Added the Amaterasu black flame block and a keybind to extinguish the flames within 5 blocks.
- Added the Fire Release technique Dragon Flame Bullet, an expanding cone of fire that ignites targets. Its scroll is in the B-rank loot table.
- The Uchiha Council building now generates in the world.
- Added sounds for Chidori, Raikiri, Sharingan, Byakugan, and Mangekyo Sharingan.
Changed
- Sharingan and Byakugan now share a dojutsu system. Ability handling, owner data, and eye positioning on the player model were reworked.
- The third Sharingan tomoe now requires 1,200 maximum chakra. The second tomoe requires 700.
- Combat experience is awarded after the player completes the root NSE advancement.
- Updated Russian and English names, tooltips, and messages, including those for Mangekyo abilities.
Foundations
- Added base items and assets for Eternal Mangekyo Sharingan, Rinnegan, Tenseigan, and Golden Byakugan.
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:XjVrwLWC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fNR6d0ai:XjVrwLWC"
}

