#Brewmaster stat priority iso
It's also the primary summon you'll have to micro if you want to survive after the Split iso ver.īut Brewmaster's greatest impact comes with controlling a fight, and that's the territory of the Storm summon. It's a single target stun on low-cd, and it follows what players want to do with their heroes-kill other heroes. Hurl Boulder is usually the go-to spell for most Brew players. It's fairly straightforward to just sic all the Primal Split summons onto one hero and call it a day, but there are a few small things players can do that can lead to a greater impact. Instead, support Brews leverage all of their impact on his ultimate, which is most likely the reason he's in the draft in the first place. He won't have Blink and BKB to maximize his Thunder Clap and Brawler damage. Support Brewmaster won't have the same kind of impact and initiation as one in the core role. Puppey’s Blink-less build against VP at ESL Hamburg Team Secret has been a proponent of playing Brewmaster in the 5 position, with much success back at ESL Hamburg. Brewmaster is now decent flex pick in the draft, leaving opponents guessing at which lane the hero will land in. Decent base stats and a solid AoE slow makes him sturdy in the lane against opposing support hero. Puck has excellent right click animation, high base damage, and a mobility spell-great traits to have as either an offlaner or a support. But it’s those same strengths that benefit them as supports. These are heroes that scale well, so it would seem counter intuitive to place them lower on farm priority. How much resources should one team dedicate to shut down a support hero? Moving these traditional cores to support heroes also sidesteps the kind of attention opposing teams place on countering them. CompLexity also dug Puck out of the dumpster and put it in the hands of Zfreek, their support player. Both CompLexity Gaming and Team Secret have experimented with a 5 position Axe, as well as Brewmaster. While we’ve seen competitive teams pick heroes that can be flexible in a core or support role, there’s been an evolution in this theory to even the most traditional of offlaners.
Brewmaster has managed to evade the curse of micro-intensive heroes, with a greater than 50% win rate across all skill brackets. These are heroes with inherently higher skill floors, compared to the “press R to win” heroes that tend to dominate the top of pub charts. Chen, Enchantress, Naga Siren, and Lone Druid are historically at the bottom of our win rate charts, even in eras where they were considerably strong. Though, like I said, a nice read and well presented.Heroes that require multiple units haven’t been very kind to the average Dota player. Though, in a normal situation, your priority would seem to just hinder you in early gear levels.Īlso, you gain 20% un-dr'd (As far as I am aware) Parry from BoK, so reforging into Dodge is a smart idea. Your build seems to work well with hard hitting bosses (In the Brewmaster Thread I referred to Heroic Sha of Fear for my argument), like taking the slash attack he does to the Tank. Hit > Expertise > Dodge / Parry > Mastery / Crit (Preference) > Haste In a standard situation, you preferably be reforging In a Magic heavy fight, sure, Haste will be by far the favoured stat since we have very little Magic defence outside of a Glyphed Guard and a 1.5 min Magic CD. You avoid attacks that you would otherwise need to spend chi to get rid of. Yes, we can argue that Haste will increase energy regen = more Chi = Higher uptime of PB's and BoK, though a Dodge / Parry heavy build would come up better in the long run. More Haste will be needed for more PB's being use in a standard fight.
I believe, (As I have discussed in the Brewmaster Tanking Thread) Haste is a deflated stat as it only increases in priority with the more Mastery you have. This is how I feel the stat priority will end up, though no theorycrafting for brewmasters has been finalized yet.Įxpertise and Hit to cap > Crit > Haste > Mastery > Parry = Dodge A nice little read, though a few concerns
0 kommentar(er)
