Information

Minecraft version: 1.21
Modloader: Fabric

Mod name: Death Backup

Feature description

Hello, I am the technical administrator of my small vanilla private server. On such servers, there are often moments when it's necessary to restore a player's items due to in-game death. I use your 'Death Backup' mod and thought it would be great to add a feature that allows Operators/Admins to view the list of backups for each player on the server and restore items without logging into the affected player's account or granting them OP privileges for such situations. Ideally, I would like to use commands like '/deathbackup list (player name)' and '/deathbackup load (player name) (index)'.

I think this would be a wonderful feature, and more importantly, it would make the mod more meaningful on multiplayer servers. Thank you for your attention.

I'm honestly surprised this is how was even setup. "so it works in server environments" It only works in server environments if everyone has OP hahaha.

I use this in my server environment. The way to use it without giving everyone OP is "/execute as Player run deathbackup load 0"
Now I don't give anyone the ability to rollback their death, don't even give it to non-OP staff. I'm the sole arbiter of determining if an inventory restore needs to happen, from either a griefer or server issues. If I did want to give it to the rest staff or to players, I'd use a command script. Melius commands would work for that, where you can make a command run a higher permission command and give you a node you can add in luckperms.

Hey!

I appreciate the suggestion! While I'd love to add all features submitted on the issue-tracker, I've got to prioritize working on them due to having limited time. In order to see which features users would like to see most, I've created https://serilum.com/mods/requests, which shows a table with all feature request submitted.

I'm aware that this is not the reaction you were looking for, but the reality is that I can't keep up with the demand. I try to do as much as I can.

Users are able to upvote requests by reacting to the first issue comment on this GitHub page with one of the 👍 😀 🎉 ❤️ 🚀 👀 emoji's. The request with the most unique reactions, will be shown at the top. You can of course add the reactions yourself too, but don't have to :). The author of the feature is already counted as +1.

I won't only focus on popular features in the upcoming years, but it does help with prioritizing. I'll probably work on a combination of popular and interesting/needed/fun submissions.

I'll close this issue with "not planned" as a way to separate an open feature request from an actual completed issue. This does not actually mean it's not planned! Incompatibilities and bug reports will still remain open.

When the feature is implemented, I'll again post a comment and close it as "completed".

Thank you for taking the time to submit the suggestion! ❤️