[9.10] Cho'Gath R - Undocumented Change or Bug?

The23rdGamer·5/15/2019, 10:19:18 PM·4 votes·4,589 views
https://gyazo.com/c71c51a1cd9f1e824d17ec3c24345302.png

When the patch for 9.10 came out on Wednesday, May 14th, Cho'Gath's infamous R indicator was changed, and now it seemingly is identical to Pyke's ultimate indicator.

https://gyazo.com/c71c51a1cd9f1e824d17ec3c24345302.png

Pictured: Rammus with Pyke's ultimate indicator, despite Pyke not being in the match at all (I was playing Dark Star Cho'Gath)

  • While I'd like to call this an undocumented buff....
  • It was never mentioned anywhere at all
  • It seems to be identical to Pyke's ultimate; it seems unlikely that the asset would be reused on Cho'Gath even if this was intentional
  • His original ultimate indicator can still be seen below the champion, just as obscure as normal
  • Changes to the execution threshold for Cho'Gath's Ultimate have been repeatedly denied in the past due to it "being a necessary part of his challenge"

It feels strange (but nice) that Cho'Gath has a very obvious ultimate indicator now though. I'm just wondering if we can get a comment on whether this was intentional or not!

26 Comments

letsfeedtogether5/15/2019, 10:46:07 PM2 votes

Its intended.

On My Kill List5/15/2019, 11:38:18 PM2 votes

might as well give darius an indicator at this point.

KVbqbFsC8e5/16/2019, 2:25:47 AM2 votes

I can't imagine it not being intentional. As someone who plays Cho, I find it to be completely unnecessary, but alot of players wanted it.

DeathBurst5/16/2019, 12:50:51 PM2 votes

I believe it was intended, but as you pointed out it's weird they finally did that while changes have been repeatedly denied in the past.

As for the "reusing assets": it's not part of Pyke's assets, it's part of the generic health-bar assets, including armor buffs, revives, etc. So it's perfectly expected for them to use it here.

ZaFiReX5/22/2019, 9:16:32 AM1 votes

I found a bug on this patch... If Cho where if the enemy flashes I don't do damage and R goes on cooldown. That's a real bug, not this.