Original Post — Direct link

TL;DR: Death screen updated in the future? Would like an answer from GGG.

Recently I've been looking at the logs because of a project I have in mind and I've noticed some interesting logs regarding player deaths and information about (I assume) the entity that last hit the player and I haven't seen any tool update use it or any post or information about it (GGG doesn't usually make public technical changes i believe but weird nobody noticed, I think). It is by no means designed to be human readable but some parts are very obvious. An example:

2021/05/18 21:17:21 Player died, killer=Metadata/Monsters/InvisibleFire/InvisibleChaosstorm_@83 (0x1e6cea64090), killer var=Metadata/Monsters/InvisibleFire/InvisibleChaosstorm_@83 (0x1e6cea64090), killer deleted=false, killer destructing=false

Note: There are some numbers between the date and the word Player that I removed from every line, just in case they mean something. I removed the date apparently too, you can check your logs if you want.

This line in particular refers to Sirus' Storm (deduced since the last entered zone was the "Eye of the Storm") we can see some data about the storm but not much, here is a pastebin with all my LOGGED (more about this later) deaths: https://pastebin.com/kaE1ND0y

The most interesting fact IMO is that is was introduced this league, I made a little script (https://pastebin.com/3pqpgwwQ on C++) that reads the file and outputs another file with only the lines with the characters "Player died, ", that is how the pastebin with logs was generated, and the first line in the output is from 2021/04/22 16:38:02.

A weird thing about this is that not every death is logged like this, tried to test what outputs I would get by dying in different ways but got no logs.

Fun note: a line with "Setting player killer var... or are we?" is logged just before every line i'm talking about. Doesnt appear when I die and it doesn't log it.

Another thing I noticed while playing with Client.txt is that some messages aren't getting logged. Searched for info about this and saw a post about Korea laws but that doesn't make sense in this case because the "Hi, I would like to buy..." message wasn't logged and the "ty" message was. In case someone is wondering how I noticed this: I made a discord bot that has an event that is triggered by a change in the Client.txt file and if it's a chat message (there are a lot of debug and instance messages) the bot PMs me the message to my discord account so I get a notification on my phone (brilliant, I know) and didn't get the notification then checked log file and nothing, maybe my bot interferees with the log mechanism but I doubt that.

To wrap up I wanted to say maybe something was said about this and I missed, if so please send it to me and I'm sorry for the long, badly structured pile of non-sense this post is but I'm just terrible at this. Also didn't know what flair so fluff ¯\_(ツ)_/¯

Also I was thinking maybe the community (if GGG doesn't say anything) could make a huge investigation about the names each source of damage registered and the tags and compile it in a database to then make a tool than whenever something logged is detected it tells us what killed us. This could be a huge QoL improvement IMO to know what killed you when it isn't obvious.

External link →
almost 3 years ago - /u/chris_wilson - Direct link

Originally posted by AlexDenfordGGG

Hello. This logging is actually some debug information used to figure out a nasty crash on production that was very hard to track down. It was not intended to make it to the client as this crash was only happening on the instance, but unfortunately the commit which removed the logging was missed.

To add to what Alex mentioned, the reason why we don't show the player this information as a death log is that it only tracks the last point of damage that killed you and is often misleading because in hectic combat situations there are a lot of damage sources. It's likely this would show some random burning debuff that happened to get processed at the right time to be the thing to technically kill you.