Links
Tags
Creators
Details
Licensed MPL-2.0
Published 2 months ago
Updated 2 weeks ago
All versions
2.0.0+mc1.21.1
Release
SOUL ASCENSION 2.0.0 for Minecraft 1.21.12 months ago 378
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
- Requires U-API 2.x (
[2.0.0,3.0.0)). - Breaking release: Soul Ascension 2.0 supports clean installations only. Player data, worlds and configuration from Soul Ascension 1.x are not migrated or supported.
- Moved the Character Screen onto U-API's retained UI lifecycle and reusable layout/components.
- Added explicit public-profile privacy settings and exact-version rejection for every serialized player attachment, including progression, titles, counters and active-title sync state.
- Added bounded U-API profile facets to public profiles without expanding the base player snapshot.
- Hardened Soul Lens privacy, observation throttling and client cache cleanup.
- Added native, optional Epic Fight support for versions
>=21.17.3.1and<21.18through Epic Fight's public attribute and player-capability APIs. - Added balanced default Epic Fight rewards: Strength grants Impact, Endurance grants maximum Stamina, and Agility grants Stamina Regeneration, each with a final-value cap.
- Mirrored Strength's Impact reward into Epic Fight's hidden off-hand attribute and refresh capped rewards through the official weapon-change hook after main-hand or off-hand swaps.
- Added Epic Fight rules to the freshly generated 2.0
attribute_rewards.json; generated rules carrynative_integration: "epicfight"and can be disabled globally or individually. - Kept Epic Fight outside Soul Ascension's runtime dependencies and packaged JAR. Damage-based Soul XP continues to use the final NeoForge damage event exactly once, including Epic Fight combat.
- Preserved the purple visual identity and server-authoritative allocation flow.
- Finalized and frozen the 2.0.0 feature set after client validation; further gameplay/UI changes move to a later version.
Compatibility
- Minecraft: 1.21.1
- Loader: NeoForge
- Java: 21
- Requires: U-API
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:nIkFUlCR:YmvEJXzA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nIkFUlCR:YmvEJXzA"
}

