Tags
Creators
Details
1.0
Compatibility
Changes
LootrDeathChest
LootrDeathChest is a lightweight Minecraft plugin that creates a chest containing a player's dropped items at their death location. It is designed to be compatible with Lootr while remaining completely independent and conflict-free.
This plugin prevents items from scattering on the ground and instead stores them safely inside a chest.
Features
- Creates a death chest at the player's death location
- Stores all dropped items safely inside the chest
- Prevents item loss from despawning or scattering
- Lightweight and simple implementation
- Fully compatible with Lootr plugin (no dependency required)
- Works across multiple Minecraft versions
Compatibility
Tested and designed to run on:
- Minecraft 1.20.x
- Minecraft 1.21.x
The plugin only uses the standard Spigot/Bukkit API, which allows it to remain compatible across multiple versions.
Installation
- Download the latest compiled
.jarfile. - Place the file inside your server's
pluginsfolder. - Restart or reload the server.
/plugins/LootrDeathChest.jar
How It Works
When a player dies:
- The plugin intercepts the dropped items.
- A chest is placed at the death location.
- All dropped items are stored inside the chest.
This keeps the area clean and prevents items from being lost.
Configuration
Example config.yml:
death-chest:
remove-time: 300
hologram: false
protect-owner: false
You can modify these values to change how the death chest behaves.
Compatibility with Lootr
LootrDeathChest is designed to coexist with the Lootr plugin without modifying or interacting with its internal systems.
- No API linking
- No shared storage
- No conflicts
FOR NOW
Both plugins can run side-by-side safely.
Building from Source
Requirements:
- Java 17
- Maven
Build the plugin with:
mvn clean package
The compiled plugin will appear in:
target/LootrDeathChest-1.0.jar
Author
Sunny Mittal
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| LootrDeathChest-1.0.jar | Unknown | 6.39 KiB |
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:ZE4GCgF4:9lJaidhO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZE4GCgF4:9lJaidhO"
}

