All versions
1.0.0-rc.2
Beta
Funny Graveyards 1.0.0-rc.2last month 31
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Funny Graveyards 1.0.0 — Initial Release
The first public release of Funny Graveyards is here!
Added
- Cinematic screenshots captured at the moment of player death
- Real player skins, equipment, nearby entities, resource packs, and supported shaders preserved in photos
- Server-side photo storage and synchronization for all players
- Graves that store dropped items, armor, offhand equipment, accessories, and experience
- Scrollable grave inventory interface
- Optional Curios integration
- Recovery Keys with grave coordinates, distance, waypoint support, and remote recovery
- Extractable memorial photos
- Wall-mounted photos with multiple size options
- Ability to attach photos to empty tombstones
- Automatic exposure correction for dark caves and nighttime deaths
- Safe grave placement and item recovery after Void deaths
- Explosion-resistant tombstones
- Public grave access with support prepared for future party and guild integrations
- Singleplayer and dedicated server support
Compatibility
- Minecraft 1.21.1
- NeoForge
- Dedicated servers
- Resource packs
- Supported shader loaders and shader packs
- Optional Curios support
Notes
- Both the client and server must have the mod installed.
- Death photos are rendered using the deceased player’s active visual setup and then shared with everyone on the server.
- Server owners should include the mod’s photo-storage folder when backing up or moving a world.
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:PkYtepFd:oclZYSlZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PkYtepFd:oclZYSlZ"
}

