Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last month
All versions
1.0.1.0
Release
Tensura: Reincarnated 1.0.1.02 years ago 5,802
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
- Increased the analysist level of some skills:
- By default, [Analytical Appraisal] & [Dragon Eye] can only analyze targets with EP x1.5 of the user's EP or below (2x with Mastery).
- [Creator]'s limit is now 2x and 4x with Mastery.
- [Mathematician]'s limit is now 5x and 7x with Mastery.
- [Great Sage]'s limit is now 5x and 10x with Mastery.
Balance:
- [Godly Craftsman] now will cost more xp to enchant TR's Engraving.
- [Unyielding] now will also be affected by the
maximumEPStealconfig like other skills like [Gluttony].
QoL:
- Added new gamerule
[resetIncompletePenalty], deciding the number of points gets removed from the Reset Counter when a player uses any type of reset scroll while not meeting the requirement for a full reset - Default: 0. - Gamerule
[resetCounterBonusUnique]now decides how many counters needed for 1 extra skill instead of just 1 counter for 1 skill when enabled.
Bugs Fixing:
- [Martial Master] doesn't boost x3 damage from battewills.
- [Gluttony]'s Predation can reach 15 blocks without Mastery.
- [Swipe] doesn't boost damage on Mastery.
- Some Haki skills' cooldown are messed up.
- Holding skills doesn't get unactivated when going through portals.
- Magics can be spammed with changing modes button.
- Orc Disaster race's evolution requirement is messed up.
- Reset Counter not working properly
- Other minor 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:Br0kXPwc:2ExgOgX8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Br0kXPwc:2ExgOgX8"
}

