Tags
Creators
Details
0.9.1
Compatibility
Changes
š ļø Theosis 0.9.1 ā Stability & Spigot Compatibility Update
This update focuses on polishing existing systems, improving compatibility, and fixing several issues reported by the community.
⨠What's New
-
š Bosses now use colored glow effects based on their rarity, making elite encounters much easier to identify at a glance.

-
š Improved
names.ymltranslations. Loot from Bosses, Towers, and many other systems now uses the translation file consistently, making item names fully customizable and much easier to localize. -
š Improved tier progression.
- Tier scaling is now fully dynamic.
- Previously, once you unlocked higher tiers, all mobs permanently kept their increased stats. Now, lowering your tier also lowers mob difficulty, allowing players to freely choose the challenge they want. Want to fight a Warden with strong gear without everything becoming overwhelmingly difficult? Now you can!
-
šØ Several Anvil improvements, including:
- Better compatibility for cooldown action bar messages on Spigot.
- Fixed socket lore rebuilding so custom text is preserved.
- Item names now correctly keep their original colors after anvil operations.
-
āļø Major Spigot compatibility improvements.
- The perk system no longer fails completely when unsupported features are present.
- 95 out of 100 perks now work correctly on Spigot, while unsupported perks are safely ignored instead of disabling the entire module.
-
ā¤ļø Fixed the Max Health perk on Spigot, restoring proper attribute handling with improved compatibility.
š General Fixes
- Fixed visual cleanup for boss glow effects after spawning.
- Improved configuration fallback behavior across multiple systems.
- Reduced unnecessary debug output in production environments.
- Various stability improvements and internal code cleanup.
Thank you to everyone who continues reporting bugs and helping improve Theosis! š
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:KGuFWktu:U6q9yt3O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KGuFWktu:U6q9yt3O"
}

