Team Liquid secures the final slot at TI11

1Play DOTA2 News
Oct 15

The TI11 Last Chance Qualifier has concluded with Team Liquid securing the final slot in the grand event, finalizing TI11’s lineup. Together with Team Secret, they will join the 18 teams that have qualified via direct invites and the Regional Qualifiers.

As one of the household names in Dota 2, Team Liquid was definitely one of the favorites in the LCQ. However, there were clouds of doubt surrounding their capabilities, mostly due to their lackluster performance in consecutive LAN events. Despite solid consistency throughout the Regional Leagues, Team Liquid placed 9th-10th at Riyadh Masters, 9th-12th at PGL Arlington Major, and 11th-12th at ESL One Malaysia.

But Liquid proved themselves when it truly matters. In the LCQ Lower Bracket Final, Liquid secured a revenge match against the young prodigies on – who had knocked them down to the LB. Throughout the BO3, Liquid showed the power of veteran Dota 2, making the LCQ LB Final look like a walk in the park.

As always, with glorious wins comes heartbreaking losses on the other side., recently joined by Roman “RAMZES666” Kushnarev, comprises young, high-potential players who finished in the top 6 at TI10. Despite a close run in the LCQ, they failed to make it to this year’s TI.

The victory for Team Liquid holds a deep meaning for the community. In our past interview with Lasse “MATUMBAMAN” Urpalainen, he revealed that this year will be his final competitive year and after TI11, he’s donezo. No matter the outcome.

The 27-year-old carry player once lifted the Aegis in 2017, winning TI under the same banner. Will MATUMBAMAN repeat history and seal the final year of his pro career with a 2nd title? Alongside 19 other bloodthirsty teams, Team Liquid and MATUMBAMAN will compete for the coveted Aegis of Champions starting on October 15th. Singapore will be buzzing with some world-class Dota 2 soon and we are all here for it!

Stay tuned to our site for more TI11 coverage!

All comments (0)
No contentNothing here, please try again later.