0 Komentarze
Przewaga drużyn Nuke (M3)
Rekordy Nuke
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Rzucenie dymówki na mapie
1714.6931
Rzucenie dymówki na mapie
2014.6931
Zabójstwa za pomocą Galil kna mapie
41.8171
Obrażenia od Galil (avg/round)
19.65.8
Rzucenie dymówki na mapie
2014.6931
Obrażenia od koktajla Mołotowa (śr./runda)
11.72
Zabójstwa za pomocą USP na mapie
41.6074
Obrażenia od USP (avg/round)
22.84.7
Strzały w głowę na mapie
15.960.3141
Obrażenia (total/round)
40073
Informacja
Map Analysis of Rooster vs Bad News Kangaroos by the Bo3.gg Team
Bad News Kangaroos on Nuke Analysis
Bad News Kangaroos demonstrated their prowers on Nuke, securing 13 out of 19 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 Bad News Kangaroos on Nuke were damyo, who contributed 22 kills, and ADDICT, who added 13 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Nuke, the team inflicted a total of 7880 overall damage.
On the defensive side of Nuke, Bad News Kangaroos held their ground firmly, successfully defending 4 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
Rooster on Nuke Analysis
Nuke proved to be a challenging battleground for Rooster, as they managed to secure 6 out of 19 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for Rooster on Nuke included dangeR, who contributed 16 kills, and nettik, who added 14 kills. Despite their individual efforts, inflicting 7012 total damage, Rooster couldn't prevent Bad News Kangaroos from securing victory on Nuke
On the defensive side of Nuke, Rooster struggled to hold their ground, successfully defending 3 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze