
RPG Mob Leveling System
Every mob has the potential to grow stronger, smarter, and more dangerous as they gain levels. With dynamic scaling of health, damage, and special abilities, each encounter becomes a unique challenge that will test your survival skills
Tags
Creators
Details
1.2.0
Compatibility
Changes
:tools: Ascendant Mobs Patch Notes
:wrench: Fixes
- Name Display Settings:
- :tools: Fixed an issue where the option to toggle name display was not functioning correctly.
:arrows_counterclockwise: Changes
:gear: Attribute System Update
Attributes are now assigned as fixed values per level instead of modifiers, using a new syntax for clarity and flexibility:
:new: New Syntax
The new format follows this structure:
[attribute]ATTRIBUTE_NAME[attributeEnd][value]VALUE_PER_LEVEL[valueEnd][max]MAX_VALUE[maxEnd] [mob]MOB_TYPE[mobEnd]
Configures attribute scaling with mob levels: [attribute] defines the stat, [value] is per-level increment (raw number addition) => base_value + level * value [max] is the cap, [mob] is optional, targets specific mobs or all
Examples:
- :heart: Max Health:
Only Skeletons now gain health using the following syntax:
[attribute]minecraft:generic.max_health[attributeEnd][value]5[valueEnd][max]30[maxEnd][mob]minecraft:skeleton[mobEnd]
This new syntax ensures better readability and allows easier customization for different mobs and attributes
:computer: Command Rename
:straight_ruler: /getdistancedebug renamed into /ascendant distance debug:
Use this command to view debug information about the player's distance from spawn.
:bar_chart: /getbestdistance [level] renamed into /ascendant get [level]:
Retrieves optimized spawn parameters for the specified level.
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:4eSfhd3M:CYI9yQQk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4eSfhd3M:CYI9yQQk"
}
