Tags
Creators
Details
1.1.1
Compatibility
Changes
🎉 LimitedGrace v1.1.1 Released!
LimitedGrace brings an important logic upgrade in version v1.1.1! This release introduces a two-layer protection system, making the server’s death-protection mechanism more flexible and easier to manage. 🚀
✨ New Features
-
🛡️ Core Logic Upgrade: Introduces a dual system of New Player Protection and Extra Protection, allowing more precise protection calculations.
-
➕ New
/lg addCommand: Administrators can now add extra protection counts for specific players without overwriting their existing statistics. -
⚠️ Major Command Changes:
/lg setis now dedicated to modifying a player's extra protection count.- A new
/lg setDeathcommand has been added to modify a player's actual death count.
-
☕ Java 21 Support: The project has been fully upgraded to run on Java 21, providing improved performance and stability.
-
⚙️ More Detailed Configuration: Supports customizable low-protection warning thresholds and comprehensive internationalized message configuration.
-
📊 Detailed Information Display:
/lg getnow clearly shows the remaining counts for both new player protection and extra protection.
📜 Commands & Permissions (Latest)
| Command | Description | Permission | Default |
|---|---|---|---|
/lg get |
View your own remaining protection count details | limitedgrace.get |
All players |
/lg get <player> |
View another player's remaining protection count details | limitedgrace.get.it |
OP |
/lg getDeaths |
View your own total death count | limitedgrace.get |
All players |
/lg getDeaths [player] |
View another player's total death count | limitedgrace.get.it |
OP |
/lg add <player> <amount> |
Add extra protection counts for a player | limitedgrace.add |
OP |
/lg set <player> <amount> |
Set a player's extra protection counts | limitedgrace.set |
OP |
/lg setDeath <player> <amount> |
Set a player's actual death count | limitedgrace.setdeath |
OP |
/lg reload |
Reload the configuration file | limitedgrace.reload |
OP |
📦 Upgrade
Note: The configuration structure has been updated (new fields for extra protection). It is recommended to backup and delete the old config.yml so a new one can be generated, or manually add the new fields according to the updated configuration.
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:CDohNxJz:ljiqdGaX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CDohNxJz:ljiqdGaX"
}

