
Immortal Cultivation
A cultivation plugin that allows players to progress through various cultivation realms, meditate to gain qi and experience, and become more powerful. Inspired by cultivation novels, this plugin brings the mystical world of cultivation to your Minecraft se
Tags
Creators
Details
1.8.3
Compatibility
Changes
[1.8.3] - 2026
Added
- Dynamic Race System: Custom races can now be created in
races.yml. The/ic race selectcommand, tab-completion, and selection book now update automatically. - Permission Management: Added
immortalcultivation.racepermission (granted by default to Mortal realm) for race selection. - Data Persistence: Data is now saved globally on server shutdown to prevent progress loss.
- Configurable Toggles: Added
enabledflags inconfig.ymlto independently enable/disable Cultivation Towers and Pools. - Qi Functionality: Implemented the
removeQimethod for complete energy management.
Improved
- Performance Optimization: Implemented a caching system for player data, drastically reducing disk I/O load during meditation.
- Tower Generation: Relaxed spawn requirements (more biomes supported, terrain elevation tolerance, and reduced player distance) to make them easier to find.
- Configuration Updates: New non-destructive update system that preserves user modifications in
.ymlfiles. - Admin Commands: Restructured
/icpermissions to separate administrative functions from player functions.
Fixed
- Corrected the auto-save timer (tick calculation).
- Fixed PlaceholderAPI crashes when sect data was incomplete.
- Optimized race messages to prevent spam during biome changes.
- Fixed the bug preventing tower spawns too close to the player who triggered them.
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:pVWrmrIu:7sraqsm0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pVWrmrIu:7sraqsm0"
}
