@hsdecktech @Spyvrr Thoughts on crafting Bloodreaver Gul'Dan?
-
-
W odpowiedzi do @kremlincardinal @Spyvrr
He’s real good and irreplaceable in the decks that use him. And it looks like a lot of the cards he likes will be in Standard for a while. Cubelock is less good than when people didn’t get how to play against it, but still solid. I’d say a solid craft.
1 odpowiedź 0 podanych dalej 2 polubione -
W odpowiedzi do @hsdecktech @Spyvrr
It's one of those cases where I've got almost all of the pieces for the better Lock decks...except DK Gul'Dan. I might hold off a while longer, since rn I'm more comfortable playing Hunter or Paladin on ladder.
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @kremlincardinal @Spyvrr
Yeah, no point crafting prematurely. Things change and you may not want him once you are tired of what you’re using now. You already have the rest of cubelock? Wow! I need... a lot more.
1 odpowiedź 0 podanych dalej 1 polubiony -
W odpowiedzi do @hsdecktech @Spyvrr
So I just looked at Cubelock and realized I am WAY off - no Umbra, a lot of missing epics. So really, I just have most of the pieces for Zoolock :D Especially after crafting Keleseth.
2 odpowiedzi 0 podanych dalej 1 polubiony -
W odpowiedzi do @kremlincardinal @hsdecktech
Gul'dan is probably the most powerful DK and he does see play in Warlock Zoo too, a tier one deck.
2 odpowiedzi 0 podanych dalej 3 polubione -
Doubtful. DK Anduin is was better before Guldan and still it. Highlander Priest has been better for longer than any standard lock deck. Guldan is probably #2 now, surpassing Jaina.
2 odpowiedzi 0 podanych dalej 1 polubiony
Deck lists aside, in terms of raw power, I don't think any DK beats Gul'dan. Obviously, Highlander Priest is a better deck than Control Warlock.
-
-
His 3 dmg lifesteal hero power is pretty disgusting.
0 odpowiedzi 0 podanych dalej 1 polubionyDziękujemy. Twitter skorzysta z tych informacji, aby Twoja oś czasu bardziej Ci odpowiadała. CofnijCofnij
-
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.