All versions
1.0.2
Release
ShibaGrace - A Grace Period Server Mod 1.0.23 months ago 130
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Dedicated servers only
Changes
Changelog
[1.0.2] - The Visuals & Stability Update
- Major Fix: Fixed a critical rendering bug where the floating feather would flicker rapidly or drop to the ground.
- New "Drone Mode": The feather no longer acts as a rigid passenger. It now uses a custom server-side tracking system with interpolation, making it glide smoothly above the player's head.
- Memory Leak Prevention: Added automatic garbage collection to instantly remove any orphaned feather entities when a player disconnects, dies, or changes dimensions.
- Visual Tweaks: The feather's size was reduced to 30% and its position was adjusted to float perfectly above the head without obstructing the view.
- Quality of Life: Reduced the tracking latency to the absolute minimum (1 tick) for ultra-smooth following, even when sprinting.
[1.0.1] - The Feedback Update
- Player Commands: Added the
/shibagrace checkcommand so non-OP players can check their own remaining grace time down to the second. - Smart Announcements: Added dynamic chat warnings that notify players when their protection is ending (at 10 minutes, every minute under 5 minutes, at 30 seconds, and a precise 10-second countdown).
- Visual Identity: Introduced the 🪶 scoreboard prefix in the tablist and chat to easily identify protected players.
- Entity Spawning: Initial implementation of the floating feather visual indicator.
[1.0.0] - Initial Release
- Core Protection: Added the core 45-minute PvP protection grace period for new players.
- Admin Controls: Added OP commands to easily toggle the system (
/shibagrace on/off), change the default grace time, and add/remove/set time for specific players. - Data Persistence: Implemented robust
.datstorage so grace periods safely survive server restarts and crashes.
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:1R7NOWFk:RR0B7iJX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1R7NOWFk:RR0B7iJX"
}

