after the 2nd dragon knight, if the same team got both, dragon shire really turns into stomp territory and comebacks become near impossible.
Without forts near the objective, you are at a massive disadvantage and are 100% in gank territory. Its very hard to make a comeback when the objective has high uptime so its hard to get free time to safely soak lanes if they are pushed back to your keeps (you’ll just miss exp if you go to the objective, and likely die since they have a level advantage if its a stomp). Many other maps don’t have the objective up almost all the time, which gives bigger windows to catch up on exp and levels. But i think dragon shire objectives need a larger gap between them
Are you kidding? This is one of the best maps. Well balanced, requiring cooperation and frequent rotation. On this map, the comeback is very strong.
If you keep losing fights over the DK there are a few other ways to put pressure on the enemy team.
One is trying to only control the bottom lane. It has bruisers and two sieges. You can get a lot of pushing power just by constantly capturing these and pushing as 3-4 while someone else soaks top/mid.
Dragon Shire is one of the few maps you can reliably take a hero that power spikes at level 20 – because almost all of your games will get that far unless there is a radically different skill level between the two teams.
Yo Ray sup That was a stupid raynor last game. Feeds more than Illidan rofl.
1 Like
Be it my DK or the enemy’s, a lot of times the first two DK does basically nothing.
And because the constant need for splits (thanks to the obj, the most stallable obj), this map has the most rooms for comebacks (after ToD).
Tod literally has pro stomp mechanics…
That’s not easy to pull off.
ToD’s objective is stallable and the core cannot be rushed. The boss is never overwhelming.
That map has the best chances for comebacks. And just because ppl can create a stomp there it doesn’t mean this is untrue.
1 Like
It didn’t help that the Illidan has never played the hero before. Malfurion should not be almost top damage…