• Siigari
    Honest to Betsy, when are you guys going to fix death recaps? They should be full of valuable information about how you got killed, not some smattering of random information telling me that this ability was used once and I died.

    PLEASE FIX THIS RIOT.
    #1
    1 year, 7 months ago
  • Associate Software Engineer
    I have some death recap changes that should come out next patch.

    The system itself was in a pretty bad place, so it required changes from both code and design (thanks to Coronach who did all design-related changes). For example it did not have enough data to figure out where the damage actually came from, and the event array was not big enough so that it would be full before all relevant events were processed...

    Anyway, please try death recap after next patch is out, and give me some feedback. It should at least make the damage source and numbers more accurate.
    #2
    1 year, 7 months ago
  • Associate QA Analyst
    Originally Posted by DietPepperPhD
    Humans learn best when given constant and obvious feedback.

    The death recap should show what skills were used against you, even if they did no damage.

    The best thing would be if you could highlight over the skill name and read what the skill does as well.

    This is especially important for the combo skills like Brand, Lux, and Akali. After getting marked there is an additional effect, an in-game way to learn about the conditions would help people learn to face those match ups.
    This is the intended functionality for Death Recap. The issues we were running into dealt primarily with the fact that Death Recap was misunderstanding a lot of the information we had passed it and thus was providing nonsense information, or flagging things as basic attacks that were actually abilities. Those issues should be gone in Wiksy and Coronach's fixes.

    Originally Posted by Necroclysm
    This is how it works.
    Create fix.
    Hold fix in reserve until someone actually notices that the thing you fixed is broken and posts about it.
    Announce the fix will be coming extremely quick, next patch!
    Get praise for expedient coding
    *scribbles some notes in his "plans" notebook* Excellent thinking... I will begin compiling a list of such issues.

    Actually, we've been working on this for a while - this thread just happened to have really fortuitous timing.
    #3
    1 year, 7 months ago
  • Associate Software Engineer
    Originally Posted by Erafumo
    Wiksy read your mind.
    I'm five steps ahead of you.
    #4
    1 year, 7 months ago