Tags
Creators
Details
V1.0.0
Compatibility
Changes
π GravesPro Changelog
[1.0.0] - 2026-02-21
π Initial Release
The foundation of the most professional grave recovery system.
Added
- Grave Vault System: A custom 54-slot GUI (Style A) that safely stores player items upon death.
- Quick Recover: One-click recovery that automatically equips armor and off-hand items to the player.
- Holographic Displays: High-performance Text Displays that show the owner's name and a live ticking 10-minute countdown.
- Void Safety Logic: Intelligent location validation that prevents graves from spawning in the abyss or lava.
- Grave Teleportation: Command
/gptpwith a centered 9-slot selection menu for players with multiple active graves. - Teleport Warmup: A 5-second movement-sensitive warmup to prevent combat logging via grave teleport.
- Admin Bypass: Permission-based system for staff to manage or recover any player's grave.
- XP Conservation: Configurable percentage-based experience storage.
Performance & Optimization
- Optimized for Paper 1.20+ using native Text Display entities rather than legacy Armor Stands.
- Minimalistic data structure to ensure zero impact on tick timings (TPS).
π Donate (Optional)
If you enjoy my work and want to support development:
π Donate via PayPal
π¬ Official Support & Community
Need help with this plugin? Join the official Marbzy Discord server for:
- π Direct Support: Fast help via our ticket system.
- π Bug Reports: Help us squash bugs instantly.
- π‘ Feature Suggestions: Shape the future of GravesPro.
- π§ͺ Beta Access: Test new "Pro Max" features before anyone else.
- π’ Announcements: Stay updated on every new release.
π Join the Discord
Developed with care by Marbzy
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:RkUtEjL0:bHpSCG8r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RkUtEjL0:bHpSCG8r"
}

