Links
Tags
Creators
Details
1.1.2
Compatibility
Changes
Death Return is a Fabric mod focused on death position tracking with a minimal and practical workflow.
When a player dies, the mod automatically records the dimension, coordinates, and timestamp, keeps the latest 20 death entries, and provides command-based viewing plus clickable chat actions for quick access and teleportation. Both vanilla and modded dimensions are supported.
Overview
- Automatically records death location without manual input.
- Keeps the latest
20death history entries per player. /deathposshows history in pages of5entries.- Each entry includes a clickable teleport action.
- Sends a compact chat message on death with quick actions.
- Supports admin queries for other players.
- Supports vanilla dimensions and mod-added dimensions.
- Main logic is server-driven, so client installation is optional for multiplayer use.
Compatibility
| Item | Requirement |
|---|---|
| Minecraft | 1.21 to 1.21.11 |
| Fabric Loader | 0.16.0+ |
| Java | 21+ |
| Fabric API | Required |
| Fabric Language Kotlin | Required |
Required Dependencies
Install the following dependencies into the target mods directory together with this mod:
| Dependency | Required | Notes |
|---|---|---|
| Fabric API | Yes | Provides Fabric events, commands, and runtime APIs |
| Fabric Language Kotlin | Yes | Required because this mod is written in Kotlin |
If fabric-language-kotlin is missing, the game will fail to load the mod.
Installation
Dedicated Server
Place the mod and its dependencies into the server mods directory. Clients do not need to install the mod in order to join.
Client / Singleplayer
The mod can also be installed on the client side for singleplayer or LAN host usage. Since singleplayer uses an integrated server, the mod works normally when installed locally.
Commands
Player Commands
| Command | Description |
|---|---|
/deathpos |
Show the first page of your death history |
/deathpos page <page> |
Show a specific page of your history |
/deathpos tp <index> |
Teleport to a specific death record |
Admin Commands
| Command | Description |
|---|---|
/deathpos player <player> |
Show the first page of another player's death history |
/deathpos player <player> page <page> |
Show a specific page of another player's history |
/deathposadmin reload |
Reload the config file |
/deathposadmin set announceOnDeath <true|false> |
Enable or disable death chat notifications |
/deathposadmin set allowPlayersUseCommand <true|false> |
Allow or block regular players from using /deathpos |
/deathposadmin set adminsCanQueryOthers <true|false> |
Allow or block admin queries for other players |
/deathposadmin set allowTeleport <true|false> |
Allow or block teleporting back to death points |
Configuration
Config file path:
config/death-return.json
Default config:
{
"announceOnDeath": true,
"allowPlayersUseCommand": true,
"adminsCanQueryOthers": true,
"allowTeleport": true
}
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:KiPgT8vD:Jm72ZRkz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KiPgT8vD:Jm72ZRkz"
}

