Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 2 months ago
All versions
Heavenly Restricted Update
1.5.0
Release
Heavenly Restricted Update4 months ago 42
Compatibility
Minecraft: Java Edition
1.21.10–1.21.11
Platform
Paper
Changes
Heavenly Restricted Update
New Content:
- ADDED /infinity COMMAND
- grants you invincibility
- pushes entities away from the user
- if smashed into a wall using the infinity push, deals damage
- Permission: sorcery.infinity
- ADDED HEAVENLY RESTRICTION CRYSTAL
- Base Restriction - Permanent speed+jump+night vision+resistance boost
- Heavenly Overdrive - 20s of extra buffed strength, jump boost, speed and absorption
- Heaven's Call - 10s of absolute invincibility
- Passive: While in Base Restriction mode, Infinity/Limitless domain has no effect on the player + bypasses the push of infinity
- Can't use any other crystals during base restriction
- ADDED INVERTED SPEAR OF HEAVEN
- Completely bypasses the new /infinity command and its invincibility
- 9 Attack damage
- 1.8 Attack Speed
Bug fixes:
- Started using infinite value for potions instead of a big number
- Domain Cleanup has been fixed
- Fixed a bug where the Malevolent Shrine caster couldn't use elytra
Balance changes:
- Changed health mode to have 30 hearts on special grade instead of 20, other grades are 3 hearts per grade
- Lapse Blue Default damage: 6 > 5
Config changes:
- Default Flat Point Steal (on kill): 10 points > 5 points
- Default Percent Point Steal (on kill): 50% > 30%
- Added defaults for Heavenly Restriction
Technical changes:
- Added a update checker for the plugin
- This requires reverting to numbers only for update versions
THE CONFIG MUST BE RESET AFTER THIS UPDATE
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:8NUHMWhH:T9zDXMAl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8NUHMWhH:T9zDXMAl"
}

