0 Komentarze
Przewaga drużyn Inferno (M1)
Rekordy Inferno
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Obrażenia od granatu (avg/round)
16.23.4
Zabójstwa za pomocą AUG na mapie
82.6098
Obrażenia od AUG (avg/round)
35.18.1
Obrażenia od koktajla Mołotowa (śr./runda)
9.52
Obrażenia od granatu (avg/round)
14.53.4
Obrażenia od GLOCK (avg/round)
11.43.8
Obrażenia (total/round)
47273
Wynik gracza (runda)
36751012
Wynik gracza (runda)
37791012
Obrażenia (total/round)
40773
Informacja
Map Analysis of Complexity vs Wisla Krakow by the Bo3.gg Team
Complexity on Inferno Analysis
Complexity demonstrated their prowers on Inferno, securing 16 out of 21 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 Complexity on Inferno were poizon, who contributed 23 kills, and blameF, who added 20 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 9103 overall damage.
On the defensive side of Inferno, Complexity held their ground firmly, successfully defending 12 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
Wisla Krakow on Inferno Analysis
Inferno proved to be a challenging battleground for Wisla Krakow, as they managed to secure 5 out of 21 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for Wisla Krakow on Inferno included jedqr, who contributed 11 kills, and hades, who added 12 kills. Despite their individual efforts, inflicting 6079 total damage, Wisla Krakow couldn't prevent Complexity from securing victory on Inferno
On the defensive side of Inferno, Wisla Krakow struggled to hold their ground, successfully defending 2 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze