Modpack version
0.5.4

Describe the bug
I created first random RFTools dimension on a server, and while I was flying in it using pneumatic armor, server lagged pretty hard and I've fallen into the void.

When I try to restore my items via /enigmatic_graves Glubo restore I do not get any list of deaths after ...restore<SPACE><TAB> and when I try /enigmatic_graves Glubo restore 1 (or 0 or death_0 or death_1) I get an error message

Input does not match pattern 'death_<id>...'

Logs
https://paste.ee/p/nZ4Eb - client
https://paste.ee/p/omM14 - server

Thanks for the report. Are you OP on the server?
What does /enigmatic_graves Glubo list output?

I think that the list is not yet in enigmatic graves in e6 0.5.4 --

[22:29:17] [Render thread/INFO] [minecraft/NewChatGui]: [CHAT] Incorrect argument for command
[22:29:17] [Render thread/INFO] [minecraft/NewChatGui]: [CHAT] ...ves Glubo list<--[HERE]

Did you run the command from the server console or?

I've tried both client as OP and rcon on server, same error message.

Hmm, damn :/ could you possible update Enigmatic Graves yourself and see if that helps? If not, I hope to get an update out tomorrow evening (~24 hours from now) with an updated version of Enigmatic Graves.

Upgrading EnigmaticGraves to 1.4 (same jar to client and server) actually broken ability to join the server for me. Client crashes while connecting.
server:

[18:08:59] [Server thread/INFO] [minecraft/PlayerList]: Glubo[/46.4.123.137:55343] logged in with entity id 338 at (839.5978141507994, 57.0, 5054.201557032157)
[18:08:59] [Server thread/INFO] [minecraft/DedicatedServer]: Glubo joined the game
[18:08:59] [Server thread/INFO] [se.mi.te.da.DataManager/]: Sending data to client: Glubo
[18:09:00] [Netty Epoll Server IO #5/ERROR] [minecraft/ArgumentTypes]: Could not serialize dev.maxneedssnacks.interactio.command.RegistryArgument@4a659fb1 (class dev.maxneedssnacks.interactio.command.RegistryArgument) - will not be sent to client!
[18:09:00] [Netty Epoll Server IO #5/ERROR] [minecraft/ArgumentTypes]: Could not serialize dev.quarris.enigmaticgraves.command.GraveEntryType@50e6fc15 (class dev.quarris.enigmaticgraves.command.GraveEntryType) - will not be sent to client!
[18:09:00] [Netty Epoll Server IO #5/ERROR] [minecraft/ArgumentTypes]: Could not serialize dev.maxneedssnacks.interactio.command.RegistryArgument@4a659fb1 (class dev.maxneedssnacks.interactio.command.RegistryArgument) - will not be sent to client!
[18:09:00] [Netty Epoll Server IO #5/ERROR] [minecraft/ArgumentTypes]: Could not serialize dev.quarris.enigmaticgraves.command.GraveEntryType@50e6fc15 (class dev.quarris.enigmaticgraves.command.GraveEntryType) - will not be sent to client!
[18:09:01] [Server thread/INFO] [minecraft/ServerPlayNetHandler]: Glubo lost connection: Disconnected
[18:09:01] [Server thread/INFO] [minecraft/DedicatedServer]: Glubo left the game

client:
https://paste.ee/p/7cnP2

Paste.ee

View Paste 7cnP2

Paste.ee - View Paste 7cnP2

Well that's disturbing O_o I wonder if it has something to do with your OS, cause I can't reproduce this at all.

I've relayed the issue to the mod dev, hopefully he has an idea.

Good news is that you can not reproduce it, so it looks like some weird cornercase, the server lagged really bad when the death happened, probably generating new chunks in RF dimension, so weird things could have happened.

I can test the world on the new e6 release when it's released, but we can hope that it's some low probability corner case.

I was also unable to reproduce it on a new world

I was strangely able to connect to the world with E6 0.5.6 client/server, the commands still don't work, but at least I have found the grave -- it was generated at height 70, iirc.

I am still unable to reproduce this on a new world, so it was probably really a weird rare cornercase and we can close this ticket.