Tags
Creators
Details
Licensed ARR
Published last year
Updated 2 months ago
All versions
1.0.6
Release
1.0.6 The Better Flag System Update!10 months ago 158
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
New Features
Commands
- Added
/grace stopcommand to manually stop an active grace period - Added
/grace start [duration]command with optional duration parameter in seconds - Added
/grace delete <regionName>command to remove existing regions - Added
/grace listcommand to display all created regions - Added
/grace info <regionName>command to view detailed region information including all flag states - Added
/grace setflag <regionName> <flag> <true|false>command as an alternative syntax for setting region flags - Added full tab completion support for all commands, subcommands, region names, flag names, and boolean values
Configuration
- Added
default-flagssection in config.yml allowing server admins to configure the default state of each flag - All flags now default to
true(enabled) when not explicitly set - Added
grace-stoppedmessage configuration option - Flags can now be pre-configured before the plugin loads
Permissions
- Added
grace.stoppermission for stopping grace periods - Added
grace.deletepermission for deleting regions - Added
grace.listpermission for listing regions - Added
grace.infopermission for viewing region information
Quality of Life
- Status command now displays the state of all global flags
- Help menu now only shows commands the player has permission to use
- Time formatting now includes hours for longer durations
- Improved feedback messages with color coding for flag states
- Region creation now validates that both corners are in the same world
- Region creation now checks for duplicate region names
- Added helpful hints after command execution
Bug Fixes
Combat and Damage
- Fixed projectile damage (arrows, tridents, etc.) not being blocked during grace period
- Fixed invincible-players flag logic being inverted
- Fixed PVP checks not properly considering per-player grace status
- Fixed mob damage flag not applying correctly in some situations
Grace Period Management
- Fixed grace period not properly ending when time expires
- Fixed boss bar progress calculation going negative or above 100%
- Fixed paused grace time not being calculated correctly when resumed
- Fixed grace period persisting across server restarts incorrectly
- Fixed auto-start not finding valid worlds when worlds section is missing
Per-Player Grace
- Fixed personal grace period not starting for new players
- Fixed players receiving duplicate grace start notifications
- Fixed personal grace expiry check not removing expired entries
- Fixed extra life feature not properly preserving inventory and experience
Deathban System
- Fixed deathban not properly kicking players after the delay
- Fixed spectator mode not being applied before deathban kick
- Fixed IP ban using incorrect method
- Fixed deathban ignore permission not being checked correctly
Regions and Flags
- Fixed region flag values not being read correctly from grace.yml
- Fixed global flags not loading default values from config
- Fixed command blocking flag logic being inverted
- Fixed flight not being disabled when leaving a flight-allowed region
- Fixed null pointer exception when checking regions in unloaded worlds
General
- Fixed cooldown messages being sent too frequently
- Fixed null pointer exceptions when items have no metadata
- Fixed region selection tools not being recognized after relog
- Fixed mob spawning flag blocking custom/plugin spawns
- Fixed movement event firing on head rotation without position change
- Fixed configuration not reloading all values on
/grace reload
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:Yp18gs4n:isnbk0wM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Yp18gs4n:isnbk0wM"
}

