0 Komentarze
Przewaga drużyn Inferno (M1)
Rekordy Inferno
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Zabójstwa za pomocą M4A4 na mapie
133.6448
Obrażenia od M4A4 (avg/round)
38.112.7
Obrażenia od koktajla Mołotowa (śr./runda)
6.62
Obrażenia od koktajla Mołotowa (śr./runda)
8.22
Zabójstwa za pomocą M4A4 na mapie
123.6448
Wynik gracza (runda)
36441012
Obrażenia (total/round)
48873
Wynik gracza (runda)
37591012
Multikill x-
4
Multikill x-
4
Informacja
Map Analysis of Liquid vs New England Whalers by the Bo3.gg Team
Liquid on Inferno Analysis
Liquid demonstrated their prowers on Inferno, securing 16 out of 29 rounds, showcasing their ability to control and adapt to various situations on this specific map. Victory on this map contributed to their overall success in the match.
The standout players for Liquid on Inferno were EliGE, who contributed 27 kills, and Twistzz, who added 28 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Inferno, the team inflicted a total of 11220 overall damage.
On the defensive side of Inferno, Liquid held their ground firmly, successfully defending 10 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
New England Whalers on Inferno Analysis
Inferno proved to be a challenging battleground for New England Whalers, as they managed to secure 13 out of 29 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for New England Whalers on Inferno included PwnAlone, who contributed 28 kills, and Rampage, who added 24 kills. Despite their individual efforts, inflicting 10185 total damage, New England Whalers couldn't prevent Liquid from securing victory on Inferno
On the defensive side of Inferno, New England Whalers struggled to hold their ground, successfully defending 9 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze