0 Komentarze
Przewaga drużyn Ancient (M2)
Rekordy Ancient
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Zabójstwa za pomocą Galil kna mapie
71.8168
Obrażenia od Galil (avg/round)
29.66
Zabójstwa za pomocą Galil kna mapie
41.8168
Obrażenia od Galil (avg/round)
20.16
Zabójstwa za pomocą GLOCK na mapie
31.4516
Obrażenia od GLOCK (avg/round)
11.94.2
Zabójstwa za pomocą AK47 na mapie
146.4203
Obrażenia od AK-47(śr./runda)
60.525.2
Asysty na mapie
10.924.4746
Asysty na mapie
11.974.4746
Informacja
Map Analysis of Fire Flux vs CYBERSHOKE by the Bo3.gg Team
CYBERSHOKE on Ancient Analysis
CYBERSHOKE demonstrated their prowers on Ancient, securing 13 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 CYBERSHOKE on Ancient were lov1kus, who contributed 17 kills, and FenomeN, who added 18 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Ancient, the team inflicted a total of 8011 overall damage.
On the defensive side of Ancient, CYBERSHOKE held their ground firmly, successfully defending 7 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
Fire Flux on Ancient Analysis
Ancient proved to be a challenging battleground for Fire Flux, as they managed to secure 8 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 Fire Flux on Ancient included soulfly, who contributed 18 kills, and Banjo, who added 13 kills. Despite their individual efforts, inflicting 7990 total damage, Fire Flux couldn't prevent CYBERSHOKE from securing victory on Ancient
On the defensive side of Ancient, Fire Flux struggled to hold their ground, successfully defending 6 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze