You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Houston have a free win any time Junkertown is in the pool, likewise with Boston on Anubis/Volskaya. NYXL are unbeaten on King's Row and Hanamura. London are incredible at Numbani and Gibraltar. It's time to start thinking about Overwatch more in terms of maps, à la CS.
I've been waiting for this for a while, it's taken a long time and a lot of sustained matches for teams to figure out styles and map-specific strengths, but I think we're there to start talking about "X is the 2nd best team in the world on X map".
It also means that we NEED to have a discussion in the future about how the map pool is implemented. No secret that OWL S1 has a format that does not work well with this.
why are there no vetoes?
Because then the league runs the risk of having maps that are generally unpopular (like Blizzard World and Junkertown) never — or rarely — be played.
Whats your take on map drafts?
Loser's pick at least should be implemented, if not full drafts. The strawman of "infinite King's Row" is easily refuted with statistics and by thinking about why teams would pick maps. They don't pick them because they like them. They pick them to win. Niche maps = wins.
Sounds like it is pretty similar then, since maps decide a lot in CS
The key for me is that this has only just become the case. Previously we did not have enough parity for maps to be the deciding factor. Overall strength, playstyle matchup etc. was overpowering the map variable in most situations.
Now start to introduce map veto for owl
They just lost Junkertown to Boston the other night so no not really a "free win"
you gotta consider Boston's current strengths though. Sideshow just means in general, every team plays a map better than their opposition, and teams cannot focus their game stratrgy around those maps because the current format predetermines the map pool, etc.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
