Source-checkedQuality of life & UI

Death Logger

by pamquale · for Minecraft

Keeps track of your deaths, restores inventory layouts, and saves coordinates, deaths screenshots and more.

2.8KDownloads
3d agoLast updated
MITLicense
Fabric · Forge +1Loaders

About Death Logger

From Modrinth

Keeps track of your deaths, restores inventory layouts, and saves coordinates, deaths screenshots and more.

DeathLogger

GitHub release Minecraft Loaders

DeathLogger keeps a log of every time you die: when and how it happened, where you were, your level, everything you were carrying and, optionally, a screenshot of the moment. You can browse and search the log in game, see what was inside your shulker boxes and bundles, and put a lost inventory back.

DeathLogger is a rewrite of DeathLog by glisco03 for Minecraft 26.x, with a new storage format, networking, GUI and a Fabric/NeoForge/Forge build. The data model and a good part of the design still come from DeathLog, and its MIT copyright notice is kept in LICENSE.

The death log screen An entry with its inventory and screenshot

What gets recorded

Each entry stores the death message, the time, the coordinates and dimension, the world or server name, your score, level and experience, your main inventory, hotbar, armour and offhand, and the screenshot if screenshots are on.

On the client, each singleplayer world and each server gets its own log in <game directory>/deathlogger/, with screenshots in deathlogger/screenshots/. Servers are told apart by address, LAN worlds and Realms by name. A dedicated server with DeathLogger installed also keeps one log per player in <server directory>/deaths/.

Using it

  • Open the log with the DeathLogger button on the Statistics screen, or bind a

key to it under Controls (it has none by default).

  • Select an entry on the left to see its details on the right. The search box

matches the death message, time, coordinates, dimension, world name and item names.

  • Middle-click an item to copy a /give command for it, including enchantments,

names and container contents.

  • Items the game can no longer read, for example from a mod you removed, show

as empty slots but stay in the log, and come back if the mod does.

  • The Restore button replaces your current inventory and experience with the ones from

the entry, after asking. It works in singleplayer worlds with cheats enabled; on a server, operators restore through the commands below. When it is not available, the button's tooltip says why. A restored entry shows when and by whom, and restoring it again warns that the items will be handed out twice.

  • The Delete button removes the entry and its screenshot, after asking.
  • The Settings button opens the options below.

Settings

Stored in config/deathlogger.json. Also reachable from Mod Menu on Fabric and from the mod list on NeoForge and Forge.

| Option | Default | Effect | | :-- | :-- | :-- | | screenshotsEnabled | true | Take a screenshot at the moment of death and show it with the entry. Screenshots are scaled down to about 960 pixels wide when the window size allows. | | useLegacyDeathDetection | false | Also record a death when your health drops to zero, for servers that never send a death message. Those entries have no cause, and false positives are possible. Has no effect in singleplayer. |

Server commands

By default these need permission level 4. A permission mod can hand them out separately through the nodes deathlogger.list, deathlogger.view, deathlogger.restore and deathlogger.delete; the last two also cover the Restore and Delete buttons in a log opened with view. On Fabric this goes through fabric-permissions-api (LuckPerms supports it), on NeoForge and Forge through their PermissionAPI.

  • /deathlogger list <player> [search] prints a player's recorded deaths,

optionally filtered by the same text the search box uses.

  • /deathlogger view <player> opens that player's log in your own client. Your

client needs DeathLogger for this.

  • /deathlogger restore <player> <index|latest> restores a recorded inventory.

The player has to be online, and their current inventory is replaced.

Requirements

  • Minecraft 26.3 and Java 25
  • Fabric: Fabric Loader and Fabric API
  • NeoForge or Forge: nothing beyond the loader

Optional:

DeathLogger menu next to File, View and About (Fabric and NeoForge; there is no Forge build of it)

  • Mod Menu on Fabric links to the settings

Older Minecraft versions are covered by earlier releases on the releases page.

Upgrading from 1.0.0

DeathLogger 1.0.0 wrote the deaths from every singleplayer world into one shared log, deathlogger/deaths_3a52ce7809.dat. Each world now gets its own log. The shared one is kept as it was, and the death log screen in any singleplayer world shows an "Older deaths" button that opens it (restoring is disabled there, since its entries may come from other worlds).

Server logs used to be named after the server list entry, so two entries with the same name, such as the default "Minecraft Server", shared a log. They are now named after the server address, and the old log is taken over the first time you join the server.

Upgrading from 0.4.x

Read the full description on Modrinth →

Highlights

From source data

Game versions

Supports 15 Minecraft versions, the newest being 26.3.

Loaders

Runs on Fabric, Forge and NeoForge.

Footprint

Rated a light load on a server.

Death Logger on Nxeon

From our catalogue
One-click install
Supported on Nxeon Minecraft servers. We download it from Modrinth, place it, and restart the server.
Server side
Optional on the server
Server type needed
Fabric, Forge, NeoForge
Server load
light
Smallest plan we suggest
Minecraft — 2 GB (2 GB RAM). This follows our own load rating above, not a benchmark.
Latest build
1.1.0+neoforge-1.21.1, released 2026-11-01

Game versions by loader

LoaderGame versionsNewest
NeoForge1.21.1 to 26.3 (6 versions)26.3
Forge26.1.2 to 26.3 (2 versions)26.3
Fabric26.326.3

From 9 recorded builds of Death Logger.

Recent builds

BuildReleasedGame versionsLoaders
1.1.0+neoforge-1.21.12026-11-011.21.1NeoForge
1.1.0+26.3-fabric2026-10-3126.3Fabric
1.1.0+26.3-neoforge2026-10-3126.3NeoForge
1.1.0+26.3-forge2026-10-3126.3Forge
1.0.0+forge-26.1.22026-07-3026.1.2Forge
1.0.0+neoforge-26.22026-07-3026.2NeoForge

Dependencies

  • Required: modrinth project P7dR8mSH (modrinth, not in our catalogue)

Declared by the newest build that lists any. Required ones are installed with it on one-click installs.

Run Death Logger on a Minecraft server

Pick a server or deploy a new one above; it is installed in one click.

What kind of mod it is

From the catalog
Listed on Modrinth as “Mods”

Quality of life & UI

Small conveniences, tweaks and interface improvements players notice straight away.

Works on a server

From source side support

Modrinth lists server-side support for Death Logger as optional: it can run on a server, but isn’t required there.

Compatibility

Game
Minecraft
Loaders
FabricForgeNeoForge
Runs on
Serveroptional on the server
Game versions
26.3 and 14 earlier

Verified at the source

  • ✓ModrinthOfficial listing, checked 2026-11-02Open ↗
  • ✓Authorpamquale, as published on Modrinth
  • ✓LicenseMITFree

Death Logger, answered

Generated from the mod’s own source data.

Do my players need to install Death Logger?

Modrinth lists server-side support for Death Logger as optional: it can run on a server, but isn’t required there.

Which loaders does it support?

Fabric, Forge and NeoForge.

Is it free?

Yes. Death Logger is free to download from Modrinth. Its license is MIT.

How do I add it to my Nxeon server?

Use “Add to a server” on this page, or open NxLabs from your dashboard. We install it, restart your server and switch it on.

NxLabs

Run Death Logger on a Minecraft server.

Deploy in about a minute from $4.99 a month, then add Death Logger in one click.