2.0
Compatibility
Changes
V2.0 Major Overhaul
This is a full rewrite of PlayerDeathLocation. Nearly every part of the plugin has been reworked for better usability, configurability, and correctness.
New Features
- Custom messages: All in-game messages are now configurable in
config.yml. Only plain text; the visual style is handled by the plugin itself. - Teleport to death location: Click the
[✈ Teleport]button directly in chat. Uses native Bukkit teleport no command hacks, no console spam. - Delete death entries: Click
[✕ Delete]in chat to remove an entry. Requiresplayerdeaths.delete.self(granted to all players by default). - Auto creative on teleport: If a player has a gamemode permission
(
minecraft.command.gamemode,essentials.gamemode.*, or*), they are automatically switched to creative before teleporting. Can be disabled viateleport-set-creative: falseinconfig.yml. - Void protection: Teleport Y coordinate is clamped to a minimum of -70 to prevent players from falling into the void.
- Relative timestamps: Deaths are shown as
2m ago,3h ago,5d ago. - Configurable max deaths:
max-deaths-per-playerinconfig.yml(default: 10). Oldest entries are automatically removed when the limit is exceeded. - New aliases:
/pdand/deathsboth work as aliases for/playerdeaths. - Auto config migration: Missing config keys from new versions are automatically added on server start without overwriting existing values.
Improved Permission System
All actions are now gated by fine-grained permissions:
| Permission | Default | Description |
|---|---|---|
playerdeaths.view.own |
true |
View own death locations |
playerdeaths.view.others |
op |
View other players' deaths |
playerdeaths.teleport.self |
op |
Teleport to own deaths |
playerdeaths.teleport.others |
op |
Teleport to others' deaths |
playerdeaths.delete.self |
true |
Delete own death entries |
playerdeaths.delete.others |
op |
Delete others' death entries |
Improved Help Command
/deaths helpnow shows only commands the player has permission to use.
Bug Fixes
- Fixed: Clicking the teleport/delete button caused an "unrecognized command" error
when EssentialsX was installed. Both actions are now proper subcommands of
/deaths. - Fixed: New config keys added in plugin updates were not written to existing
config.ymlfiles after a server restart. - Fixed: Deaths list used a sequential display counter (
#1, #2, ...) instead of the real database ID, causing teleport/delete commands to target the wrong entry.
Breaking Changes
- The internal
/pdtpand/pddelcommands have been removed. Use/deaths teleport <ID>and/deaths delete <ID>instead. - Config structure has changed. Old
config.ymlfiles will be auto-migrated, missing keys are added automatically, existing values are preserved.
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:mk0qMEG7:lcp4EcFZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mk0qMEG7:lcp4EcFZ"
}

