DeathLogger
DeathLogger 会记录你每一次死亡的情况:包括死亡的时间、原因、地点、等级、携带的物品,以及可选的死亡瞬间截图。你可以在游戏内浏览和搜索日志,查看潜影盒与包裹中的物品,并将丢失的物品恢复。
DeathLogger 是 glisco03 开发的 DeathLog 针对 Minecraft 26.x 的重写版本,采用了新的存储格式、网络通信、图形界面以及 Fabric/NeoForge/Forge 构建版本。其数据模型和部分设计仍源自 DeathLog,其 MIT 版权说明保留在 LICENSE 文件中。
记录内容
每个条目存储死亡消息、时间、坐标和维度,世界或服务器名称、你的分数、等级和经验值、主物品栏、快捷栏、盔甲和副手物品,以及如果启用了截图功能时的截图。
在客户端,每个单人世界和每个服务器都会在 <game directory>/deathlogger/ 下拥有独立的日志,截图则保存在 deathlogger/screenshots/ 中。服务器通过地址区分,局域网世界和 Realms 通过名称区分。安装了 DeathLogger 的专用服务器还会在每个玩家目录下生成一份死亡记录,保存在 <server directory>/deaths/ 中。
使用方法
- 在统计界面点击 DeathLogger 按钮打开日志,或在控制设置中为其绑定按键(默认无绑定)。
- 在左侧选择条目,右侧查看其详情。搜索框可匹配死亡信息、时间、坐标、维度、世界名称和物品名称。
- 鼠标中键点击物品可复制
/give指令,包括附魔、名称和容器内容。 - 游戏无法再读取的物品(例如来自已移除模组的物品)将显示为空槽但保留在日志中,模组重新安装后会恢复。
- “还原”按钮会在确认后用条目中的库存和经验替换当前状态。在开启作弊的单人世界中有效;在服务端,管理员可通过以下命令进行还原。当该功能不可用时,按钮提示会说明原因。已还原的条目会显示还原时间和操作者,重复还原时会警告物品将被发放两次。
- “删除”按钮会在确认后删除条目及其截图。
- “设置”按钮打开下方选项。
设置
存储在 config/deathlogger.json 中。在 Fabric 上也可通过 Mod Menu 访问,在 NeoForge 和 Forge 上可通过模组列表访问。
| 选项 | 默认值 | 效果 |
|---|---|---|
screenshotsEnabled |
true |
在死亡时刻截取截图,并在条目中显示。当窗口尺寸允许时,截图会被缩小至约 960 像素宽。 |
useLegacyDeathDetection |
false |
当生命值降至零时也记录死亡,适用于那些从不发送死亡消息的服务器。此类条目没有死因,且可能出现误报。在单人游戏中无效。 |
服务器命令
默认情况下这些命令需要权限等级 4。一个权限模组可以通过节点 deathlogger.list、deathlogger.view、deathlogger.restore 和 deathlogger.delete 单独分配这些权限;后两个命令还涵盖了使用 view 打开日志时的“恢复”和“删除”按钮。在 Fabric 上通过 fabric-permissions-api(LuckPerms 支持该 API)实现,在 NeoForge 和 Forge 上则通过各自的 PermissionAPI 实现。
/deathlogger list <player> [search]打印玩家记录的死亡信息,可选择性地使用与搜索框相同的文本进行过滤。/deathlogger view <player>在你的客户端中打开该玩家的日志。你的客户端需要安装 DeathLogger 才能使用此功能。/deathlogger restore <player> <index|latest>恢复已记录的物品栏。玩家必须在线,其当前物品栏将被替换。
依赖要求
- Minecraft 26.3 和 Java 25
- Fabric:Fabric Loader 和 Fabric API
- NeoForge 或 Forge:除加载器外无需其他依赖
可选:
- Better Statistics Screen 会在文件、查看和关于旁边添加一个 DeathLogger 菜单(支持 Fabric 和 NeoForge;它没有 Forge 版本)
- Fabric 上的 Mod Menu 会链接到设置页面
较旧的 Minecraft 版本可在 发布页面 找到早期版本。
从 1.0.0 升级
DeathLogger 1.0.0 将每个单人世界的死亡记录写入一个共享日志 deathlogger/deaths_3a52ce7809.dat。现在每个世界都有自己的日志。原有的共享日志保持不变,任何单人世界中的死亡日志屏幕都会显示一个“旧死亡”按钮来打开它(在此处禁用恢复功能,因为其条目可能来自其他世界)。
服务器日志过去以服务器列表条目命名,因此两个同名条目(如默认的“Minecraft Server”)会共用一个日志。现在它们以服务器地址命名,当你首次加入服务器时会自动接管旧日志。
从 0.4.x 升级
由 DeathLogger 0.4.x 生成的日志在首次打开时会被转换,原始文件会保留为 <name>.r3.bak。其条目会从 1.21.11 版本进行升级;任何无法升级的内容将以不可读的槽位形式保留在日志中。针对世界和服务器的 0.4.x 日志会在你首次打开该世界或加入该服务器时再次被读取。
构建
./gradlew build
生成的 jar 文件位于 fabric/build/libs、neoforge/build/libs 和 forge/build/libs。Minecraft 版本及所有依赖的版本均在 gradle.properties 中设置。
common 目录包含由所有加载器共享的代码,基于原版 Minecraft 编译。fabric、neoforge 和 forge 分别添加了各自加载器的入口点、网络通信和平台钩子。compat-betterstats 仅编译到 Fabric 和 NeoForge 的 jar 包中。
许可证
MIT,详见 LICENSE。
鸣谢
- glisco03,DeathLog 的作者,本模组所基于的原始模组作者
- pamquale,DeathLogger 的作者与维护者
DeathLogger
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.
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
/givecommand 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:
- Better Statistics Screen gets a 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
Logs written by DeathLogger 0.4.x are converted the first time they are opened,
and the original file is kept as <name>.r3.bak. Their items are upgraded from
1.21.11; anything that can't be upgraded stays in the log as an unreadable slot.
0.4.x logs for worlds and servers are picked up again the first time you open
that world or join that server.
Building
./gradlew build
The jars end up in fabric/build/libs, neoforge/build/libs and
forge/build/libs. The Minecraft version and all dependency versions are set in
gradle.properties.
common holds the code shared by all loaders, compiled against vanilla
Minecraft. fabric, neoforge and forge add each loader's entry points,
networking and platform hooks. compat-betterstats is compiled into the Fabric
and NeoForge jars only.
License
MIT, see LICENSE.
Credits
- glisco03, author of DeathLog, the original mod this one is based on
- pamquale, DeathLogger author and maintainer
下载 Death Logger
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Death Logger
下载 Death Logger
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Death Logger
下载 Death Logger
下载 Death Logger
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Death Logger
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Death Logger
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Death Logger
需要联机服务器吗?
稳定流畅、一键部署,几分钟即可和朋友联机开服
最低仅需 8 元/月 即可畅快联机
下载 Death Logger
已移植至 1.21.1。详见 GitHub 发布页面:
已更新为 Minecraft 26.3 版本,包含一些修复和改进。详细信息请参阅 GitHub 发布页面:
完全重写为多加载器模组。详情请参见 GitHub 发布页面:
关于这个资源的讨论、问题反馈与使用心得
还没有讨论,来发第一帖吧
你是这个资源的作者?登录后可认领此资源。
相似资源
模组
显示你正在注视的方块的信息。(适用于 Minecraft 1.16+ 的 Hwyla/Waila 分支)
模组
使用 JavaScript 编辑配方、添加自定义物品、编写世界事件!
模组
查看物品与配方
模组
在游戏画面角落显示附近世界地形、玩家、生物和实体的地图。可创建路径点,帮助你找到标记过的位置。
模组
AE2:一款流行的自动化与存储模组
模组
那是什么?一个 Waila/Hwyla 的分支。
评论 0
登录后参与评分
还没有评论,来抢沙发吧