Xaryu has already streamed this to 8k+ people, so it’s spreading throughout the internet like the plague
Popping a Pyroclasm empowered Pyroblast into an immuned target, will cause the buff to bug out, and add it to your next Pyroblast instead. This bug interaction can be done pre-arena and then gets carried over to the arena and the instant version of Pyroblast through Hot Streak.
Fair. I’m just memeing. Indie company needs to fix this tbh, can imagine this being annoying, especially when the meta-monkeys get their hands on it and scuff the ladder up.
Thank you for sharing this. I hope it gets fixed soon. Question, though. Is the buff still apparent when the Fire Mage enters the Arena? Can it be purged?
I do not know tbh. To my understanding, it’s not a visible buff and pyroclasm’s benefits are simply added onto your next Pyroblast, hardcasted or instant.
Tho all their forces was directed on TBC preparation launch. WF1 race ended, others will whine but pay. kekw. $ green dollars on old content so juicy. mmmmmmmm
you were talking about normal pyroclasm usage. its still a garbage gimmick talent that might work once every 10 games, and the cost of using it is losing meteor (15k instant, borderline unavoidable damage on every combust)
" this mechanism(pyroclasm) has nothing to do in 3s or in arena at all…"
“no spell should do 25k dmg in 3s if you have 35k hp and bis gear.”
And it was already 1 week ago. And that Mitchguy was like in his videofrom yesterday: OH, i found out this spec.
kek
Saw about 5 different teams do this to us this morning, playing in the 2400-2500 mmr range, including some double fire mage teams who got to use this exploit twice in a game.
Pathetic really. Also really embarrassing that they want to cheat to get an easy ‘glad’. Also agree that the players using it should have their rating stripped, but how likely is this to happen if we’re being really honest.
Stuff like this should get fixed moments after they are discovered and reported. For reference, I saw Xar’s stream last night live (around 01:00am GMT) and 13 hours after it’s discovery it still hadn’t been hotfixed.