PoE1: Apparently GGG now has something like "Death Recap" tech.

In the following they can not only distinct between Mercenary and monster doing the killing blow but even name the monster:

"
Mirror of Kalandra has spawned on 14 Mercenaries.

Of these, 7 were skipped, so a year of bad luck for each one results in seven years of bad luck!
5 players successfully claimed their Mirror(s).
2 players lost their duels, losing 2 Mirrors each.
One of these players didn't even die to the Mercenary, but got third partied by a Vendigo they had neglected to kill before beginning their duel.


Source: https://www.pathofexile.com/forum/view-thread/3804909
No wonder it's lost, it's in the middle of the jungle!
Last edited by Zrevnur#2026 on Jul 2, 2025, 5:07:56 AM
Last bumped on Jul 2, 2025, 10:05:59 AM
This is not new. At one time you could find this info in Client.txt, but it was fixed.
https://www.reddit.com/r/pathofexile/comments/o2yzsl/clienttxt_changes_and_bugs/

The original reply from 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.
The follow-up from Chris:
"
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.
"
MonaHuna#6449 wrote:
This is not new. At one time you could find this info in Client.txt, but it was fixed.
https://www.reddit.com/r/pathofexile/comments/o2yzsl/clienttxt_changes_and_bugs/

The original reply from 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.
The follow-up from Chris:
"
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.

Thanx for posting. Didnt know they actually had the tech available.

(However I have to disagree with AlexDenfordGGG here: I consider it "fortunately" not "unfortunately" that they blundered like that.)
No wonder it's lost, it's in the middle of the jungle!
"
The follow-up from Chris:
"
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.

From a simple math POV the "likely" claim is obviously wrong. If 80% of incoming is X then there is (from that simple math POV) ~80% chance for the last damage point to be done by X.

So this seems like a dishonest answer by Chris/GGG suggesting that the real motivation was/is something else.
No wonder it's lost, it's in the middle of the jungle!
neat

Report Forum Post

Report Account:

Report Type

Additional Info