Links
Tags
Creators
Details
All versions
0.1.0-beta
Beta
Tensura Compat: FancyMenu v0.1.0 Beta3 months ago 46
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Initial beta release!
- Added 40 new Placeholders and 9 new Requirements to FancyMenu that provide support for Tensura-related values.
- New Placeholders
- Player Race Name
- Player Tracked Evolution Name
- Current % Player Evolution Progress
- Player Alignment
- Current, Max and Current % Player Magicules
- Current, Max and Current % Player Aura
- Current, Max and Current % Player Existence
- Current, Max and Current % Player Spiritual Health
- Current, Max and Current % Mount Spiritual Health
- Current and Current % Player Health Severance
- Player Multilayer Barrier
- Player Soul Points
- Player Analysis Mode Level
- Player Presence Sense Level
- Player Dodge Cooldown
- Player Magicule Poison Resistance
- Ability Active Preset
- Ability Slot Skill Name
- Ability Slot Skill Icon (Resource Location)
- Ability Slot Mode Name
- Ability Slot Mode Index
- Current, Max and Current % Ability Slot Learning
- Current, Max and Current % Ability Slot Mastery
- Ability Slot Cooldown
- Area Magicules
- New Requirements
- Is Player Demon Lord Seed
- Is Player True Demon Lord
- Is Player Hero Egg
- Is Player True Hero
- Is Player In Spiritual Form
- Is Ability Slot Filled
- Is Ability Slot Learned
- Is Ability Slot Mastered
- Is Ability Slot On Cooldown
- New Placeholders
- Patched an issue between FancyMenu and Tensura: Reincarnated where having any amount of menu blur as set through Tensura's config would cause screens to not render correctly in larger modpacks.
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:kFycsJBz:FQ3DfXA0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kFycsJBz:FQ3DfXA0"
}

