"{SPELL_APHELIOS_Q_NAME}" in death recap... really?

VampiricLlama·12/22/2019, 7:48:44 PM·10 votes·7,321 views

Does the interface team take no pride in their work or what? There's no way this made it through testing unnoticed, so someone at some point was like "lol whatever we'll fix it later, get this guy out we have the dusk and dawn skin event coming up."

13 Comments

EATARI12/22/2019, 8:13:39 PM6 votes

It’s so sad, his W weapon swap deals damage according to death recap. [zombie-brand-facepalm]

Hotarµ12/22/2019, 8:14:21 PM4 votes

Can I just ask, what game do you all play that's 100% perfect from the ground up?

Invisible champions or ultimate abilities that kill allied champions I can understand, but it's literally just a display error. Every game has these as one point or another, please stop blowing everything out of proportion.

And yeah, even though I don't think it's what happened, if Riot did push Aphelios out with this error being known, it's really not that big a deal considering it'd be pretty ridiculous to halt an entire champion release for nothing more than a graphical error.

ModAcademy Kayn12/23/2019, 2:13:28 AM2 votes

Well it depends on a few things:

  • Does this happen in every instance of Aphelios killing someone who was affected by Q?
  • Does this happen in every game of Aphelios?
  • Is there something else contributing to this alongside Aphelios, like another champion contributing to the kill?
  • Is this an issue with Death Recap or Aphelios?
  • Is this reproducable?

And while this may seem stupid to someone outside the QA industry:

  • Is this issue majorly affecting gameplay?

I've only a year and a half in QA so far, and hoping to get more this coming year, but when it comes to bug testing, sometimes we find issues that are minor and don't exactly impact anything major enough that it's not worth fixing them over things that are far more impactful. For example, it's time better spent fixing a bug that makes someones model's texture inverted, than a minor bug about something's name, which while looking kinda wonky, still tells the player what it was trying to tell them.

But even then, that's all depending on if that bug was even found IN quality assurance. There are some issues that are so rare, that it takes 1000+ automated testings to reproduce and fix it internally, so sometimes things slip through the cracks. When you have thousands upon thousands of players playing thousands of games a day, what may take a tester an entire day to find something, could only take less than an hour.

Ðark Sol12/23/2019, 3:52:03 AM2 votes

[deleted]