Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 6 days ago
All versions
2.0.0-BETA-1c
Release
Naruto Destination 2.0.0-BETA-1clast month 65
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
Changes & Updates
Primary Jinchuriki Rework
Tailed beast primary jichurikiis the first player who reaches stage 2 of the Bijuu- Every holder of a Bijuu's chakra can always use the first transformation stage, only stage 2 and up require being the primary
Skill Treebeast nodes now show the primary jinchuriki by name, or the amount until the cap is reached if a higher cap than one per beast is configured- This entire feature is entirely optional and can be toggled off in the
Tailed Beast config - New admin command:
/nd tailedbeast primary <beast> [set|clear <player>|clearall]Other - Pin marks in the
Flying Thunder Godmarker menu (Jutsu Picker) to protect them from being overriden DNA: any two identified samples can be crafted (shapeless) into one unidentified vial, so duplicates are worth another rollMode Wheelspeed arrows: the unlit ones are near-white now instead of grey, so you can actually see how many stages you haveNPC Editor: the status line now shows the server's real verdict (applied or the refusal reason) instead of saying "Applied" the moment you click
Bug Fixes
- "That beast will not answer you. Another jinchuriki holds it" no longer blocks selecting a beast in the skill tree
- Players who sealed chakra before the last patch and had no tailed beast on the mode wheel get it back on their next login
- Fixed a server crash (StackOverflowError) when teleporting with
Flying Thunder Godto a mark whose chunk was still loading Flying Thunder Godmarks with a broken anchor can no longer crash the server, they are skipped insteadNPC Editorno longer loses an NPC'sdrops_modewhen you apply an editNPC Editornow actually tells you when the server is done applying the changes
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:vOjCavUT:xSIBGog9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vOjCavUT:xSIBGog9"
}

