I believe this started with Patch 5.22 for the preseason. The announcer no longer gives audio for every single kill like it used to. It still calls multi-kills, and an unknown pattern for other individual kills. Is there a setting or something to re-enable this? I like the audio cue to know how many champions are still alive, particularly in large teamfights where it can be hard to keep track of which particles mean something is dead or not.

  • 3
    5.22 patch notes do not designate any changes to the announcer, and I cannot find anyone else mentioning similar problems. i have had a delay in announcement when multiple kills were made or when turret kills and champion kills happened at the same time. it may be a bug. you can try contacting customer support.
    – Dragonrage
    Nov 23, 2015 at 18:50
  • 1
    Same here. I've experiences delays but I've not been paying attention enough to notice that the announcer missed to broadcast a kill. Nov 23, 2015 at 19:23
  • 1
    The visual cue is still there, just not audio
    – Brian J
    Nov 23, 2015 at 19:28
  • As mentioned before, this wasn't documented anywhere. Try using the repair function in the game patcher and see if that helps. If not, it's probably an unintended bug and you should mention it on the boards.
    – gwj17
    Nov 23, 2015 at 20:29
  • 1
    I have experienced this (in ARAM). It doesn't even always call out the multi-kills and shutdowns, and also when there no kills for > 30 seconds before or after a kill. I think I have experienced this in most if not all ARAM games I've played since 5.22
    – clcto
    Nov 23, 2015 at 23:19

1 Answer 1


According to my researches (which came up empty) i would assume that somewhere in the game code they must've made so the sounds don't overlap (so you won't hear double and triple kill at the same time) and i guess (again sorry for not being sure of anything, these are assumptions and speculations, but i couldn't find anything online) that if a certain time passes they no longer play the audio since it's pointless by then.

Again, do not take anything i said has a certainty this is all speculation on my part , for which i am posting to try and give some possible reasons has to why this happens (again, not sure on anything!!)

This question is something either a Riot Staff or a person who know's or has access to the actual game code (Or someone who knows someone there, you get where i'm headed don't you?) to be able to specify the reason, it might even be an actual bug in the game that Riot themselves haven't noticed, or have but haven't made any impactfull changes to fix it since it doesn't affect the actual gameplasy (What's wrong with missing the announcemment on a kill or two? You can still see the kill feed and score).

What i'm trying to say is, all we can do is wait until Riot either fix this, or just cry about the announcer not saying Pentakill when you are playing Full Ap Amumu (It works some games!)

  • League's announcer sounds haven't been able to overlap since I started playing over 2 years ago, so this doesn't seem correct.
    – gwj17
    Feb 29, 2016 at 15:50
  • I'm not saying it is correct, just giving some thoughts of what i think might be the reason has to why the announcer doesn't announce everything
    – Magmagod
    Feb 29, 2016 at 15:50
  • I think it might be a change to make it so that announcements don't go on forever when a bunch of announcements get queued up at once. I'm not sure what the priority is, but if someone gets a triple and there's a double ace and the minions take a tower, you'll get two ace messages, a triple message, and a tower down message, but none of the single kill announcements. Like I said, I don't know the priority (or if this is even how it works) but anecdotally, I feel like this is the case.
    – nukeforum
    Feb 29, 2016 at 20:56
  • Well for all we know, that is how it works, only Riot Staff and people that have access to the actual code and such will know
    – Magmagod
    Feb 29, 2016 at 21:03
  • Actually, not even a Riot Staff may know exactly how it works. The current version is most likely the end result of a series of bug fixes, and unless someone decided to document exactly how the announcer fixes were done (unlikely), nobody will know exactly how this works unless they go spend hours and reverse engineer all the code. From observation, we just know that it doesn't overlap, and does not play all the queued sounds, so somewhere there is logic that drops announcements to make it less annoying.
    – Nelson
    Apr 5, 2016 at 7:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .