[Gameplay Bug] Thresh's Relic Shield does not function properly

MIDNIGHT KITE·1/26/2015, 3:34:38 AM·1 votes·940 views

Compared to other champions such as Blitzcrank; Thresh cannot easily hit the minions with a relic shield stack and kill the minion. His auto attacks deal very little damage so you will usually have to wait until the minion is very very low to have the relic shield stack work properly. This is especially frustrating because other champions such as Blitzcrank will kill the minion under 50% health almost every time and still recieve the relic stack bonus for him and his teammate. You need to examine how Thresh functions with relic shield by testing this out in any custom game. Notice the difference when playing with blitzcrank and using the exact same auto attack.

6 Comments

ballatwenty41/26/2015, 3:37:43 AM1 votes

This has been known for a long time because Thresh's auto attacks are considered ranged attacks & not melee. Relic Shield/Targon's stacks only apply & proc to melee auto attacks & so it puts Thresh in a weird position with the item, especially in late game.

MIDNIGHT KITE1/26/2015, 3:40:49 AM1 votes

Okay I was wondering if that was the case or not. IF this is intended by riot it can be very frustrating and annoying for player experience and can probably be disregarded as a bug. Otherwise I believe riot should look into this a bit more to see how unfair an advantage it is to ranged players.

MIDNIGHT KITE1/26/2015, 3:42:18 AM1 votes

Also it is extremely retarded that Thresh's melee auto attack with his fucking chain that he holds in his hand would be considered ranged. >:{

Murlock Rager1/26/2015, 2:52:27 PM1 votes

its ranged, but not a projectile (hello yasuo wind wall) but letting an item such as relic shield go off on him would be such an advantage, the reason it executes on a melee hit is cause by them walking up they can get more easily poked, and them getting pointblank might as well execute, so they dont die trying to proc it, where as a ranged champion doesnt have to get that close, so the execute isnt needed.

Nucleophilic atk1/26/2015, 2:58:22 PM1 votes

Uhm, this isn't a bug at all actually. it is supposed to do that.