Difference between revisions of "User:Pier4r/tournaments"

From Gladiabots Wiki
Jump to: navigation, search
(→‎Round 4)
(→‎Stage 2 Top7-9 and Top4-6)
 
(90 intermediate revisions by the same user not shown)
Line 10: Line 10:
 
* https://www.toornament.com/tournaments/2202804424534482944/information
 
* https://www.toornament.com/tournaments/2202804424534482944/information
 
* https://forum.gladiabots.com/viewtopic.php?f=27&t=1765
 
* https://forum.gladiabots.com/viewtopic.php?f=27&t=1765
 +
 +
=== Stage 3 Top1-3 ===
 +
 +
<pre>
 +
milkhunter vs mumpsimus
 +
Game 1 match ID: 1688573.
 +
Game 2 match ID: 1690701.
 +
Game 3 match ID: 1690744.
 +
Game 4 match ID: 1690782.
 +
 +
bockwurst vs mumpsimus
 +
Game 1 match ID: 1688574.
 +
Game 2 match ID: 1689628.
 +
Game 3 match ID: 1690638.
 +
Game 4 match ID: 1690704.
 +
 +
bockwurst vs milkhunter
 +
Game 1 match ID: 1688575.
 +
Game 2 match ID: 1689642.
 +
Game 3 match ID: 1690645.
 +
Game 4 match ID: 1690709.
 +
Game 5 match ID: 1690745.
 +
1690785
 +
Game 6 match ID: 1690794.
 +
</pre>
 +
 +
=== Stage 2 Top7-9 and Top4-6 ===
 +
 +
<pre>
 +
### top4-6
 +
pier4r nvidia k1 vs gtresd
 +
Game 1 match ID: 1687565.
 +
Game 2 match ID: 1688335.
 +
Game 3 match ID: 1688384.
 +
close one, gtresd went 3 vs 4 for a little bit.
 +
1688540
 +
super close
 +
1688549
 +
blue team sg bugged out
 +
 +
thecommonpigeon vs pier4r nvidia k1
 +
Game 1 match ID: 1687564.
 +
Game 2 match ID: 1688114.
 +
Game 3 match ID: 1688143.
 +
Game 4 match ID: 1688308.
 +
1688537
 +
 +
gtresd vs thecommonpigeon
 +
Game 1 match ID: 1687566.
 +
Game 2 match ID: 1688113.
 +
Game 3 match ID: 1688140.
 +
Game 4 match ID: 1688309.
 +
 +
### top7-9
 +
heartlessvoid vs stampid
 +
Game 1 match ID: 1687560.
 +
Game 2 match ID: 1688144.
 +
Game 3 match ID: 1688159.
 +
1688530
 +
 +
kasv vs stampid
 +
Game 1 match ID: 1687561.
 +
Game 2 match ID: 1688100.
 +
Game 3 match ID: 1688118.
 +
Game 4 match ID: 1688146.
 +
 +
kasv vs heartlessvoid
 +
Game 1 match ID: 1687562.
 +
1688104
 +
Game 2 match ID: 1688153.
 +
Game 3 match ID: 1688206.
 +
Game 4 match ID: 1688346.
 +
</pre>
  
 
=== Stage 1 ===
 
=== Stage 1 ===
 +
 +
==== Round 6 ====
 +
Last round of the swiss system.
 +
 +
See also: https://forum.gladiabots.com/viewtopic.php?f=27&t=1765&p=18429#p18429
 +
 +
<pre>
 +
bockwurst vs thecommonpigeon
 +
Game 1 match ID: 1685220.
 +
Game 2 match ID: 1685570.
 +
Game 3 match ID: 1685904.
 +
Game 4 match ID: 1685913.
 +
Game 5 match ID: 1685936.
 +
Game 6 match ID: 1685982.
 +
 +
gtresd vs milkhunter
 +
Game 1 match ID: 1685221.
 +
Game 2 match ID: 1685726.
 +
Game 3 match ID: 1685889.
 +
1686496
 +
1686512
 +
1686539
 +
1686570
 +
1686592
 +
1686664
 +
1686704
 +
 +
kasv vs heartlessvoid
 +
Bugging out again. Second match with kasv. (it bugs when he changes the ai)
 +
https://forum.gladiabots.com/viewtopic.php?f=6&t=1776&p=18430#p18430
 +
Game 1 match ID: 1685224. 1-0
 +
Game 2 match ID: 1685580. 1-1
 +
Game 3 match ID: 1685604. 1-2
 +
Game 4 match ID: 1685627. 1-3
 +
1685657 draw
 +
Game 5 match ID: 1685670. 1-4
 +
Game 6 match ID: 1685676. 2-4
 +
Game 7 match ID: 1685692. 2-5
 +
Game 8 match ID: 1685700. 3-5
 +
Game 9 match ID: 1685712. 4-5
 +
Game 10 match ID: 1685727. 5-5
 +
1686484 6-5
 +
 +
t0tproduction vs chilio6
 +
1685225
 +
1686485
 +
1686526
 +
1686556
 +
1686584
 +
1686645
 +
1686695
 +
1686742
 +
1686784
 +
1686480
 +
 +
+_+ vs mumpsimus
 +
1685222
 +
interesting how +_+ pushes.
 +
1686486
 +
1686500
 +
1686550
 +
1686582
 +
1686641
 +
 +
pier4r nvidia k1 vs teddy 88
 +
1685223
 +
1686489
 +
1686502
 +
1686542
 +
1686574
 +
1686633
 +
 +
stampid vs umrenato
 +
1685227
 +
1686490
 +
1686517
 +
1686545
 +
1686577
 +
1686636
 +
1686689
 +
1686725
 +
 +
savageX89 vs yours_truly
 +
1685229
 +
1686492
 +
1686504
 +
1686531
 +
1686566
 +
1686586
 +
1686655
 +
1686692
 +
 +
x50calheadshot vs ctl
 +
1685226
 +
1686494
 +
1686509
 +
1686535
 +
1686580
 +
1686602
 +
1686669
 +
1686701
 +
 +
</pre>
 +
 +
==== Round 5 ====
 +
Today I am pretty tired. Going though a lot of matches seems easy but it is not
 +
(try yourself, I listed the IDs here). So this time I really list at least the
 +
IDs trying to pick the draws from chat.gladiabots.com
 +
 +
I find resolving matches better than waiting an additional day to hope to have more energy. Otherwise it lasts too long.
 +
 +
2019-02-12 22-30. Nah. 10+ games per match with balanced performance takes too much time of my little time budget. Each game in a match is 10 minutes waiting plus at least 5 minutes overhead and resolution. So 10 games are at least 150 minutes or 2h 30m if not more. It is too much for a day.
 +
 +
Starting splitting round in multiple days. Resolving more 6 or more iterations per day is what I can really afford.
 +
 +
Also the swiss system is starting to settle. Lots of balanced matches with plenty of games.
 +
<pre>
 +
bockwurst vs gtresd
 +
1683067
 +
1683187
 +
Game 1 match ID: 1683213.
 +
Game 2 match ID: 1683237.
 +
1683730
 +
great game. Fight for the center resource but the approach of bockwurst "I go +1 and then I push" almost backfired.
 +
1683787
 +
also very nice.
 +
Game 3 match ID: 1683844.
 +
Game 4 match ID: 1683867.
 +
Game 5 match ID: 1683890.
 +
Game 6 match ID: 1684229.
 +
 +
kasv vs thecommonpidgeon
 +
Game 1 match ID: 1683070.
 +
Game 2 match ID: 1683118.
 +
1683144
 +
Game 3 match ID: 1683176.
 +
Game 4 match ID: 1683205.
 +
Game 5 match ID: 1683240.
 +
Game 6 match ID: 1683281.
 +
 +
+_+ vs umrenato
 +
Game 1 match ID: 1683072.
 +
Blue team super push but the red have a nice collecting approach
 +
Game 2 match ID: 1683798.
 +
The red team goes a bit too much for the push. The blue may punish them more often than not. We will see.
 +
Game 3 match ID: 1683862.
 +
1683862
 +
1684622
 +
1684643
 +
1684658
 +
1684699
 +
 +
savageX89 vs chilio6
 +
1683077
 +
1684605
 +
1684626
 +
1684653
 +
1684691
 +
1684738
 +
1684788
 +
1684862
 +
Tip. Don't score only in the last 30 seconds. Sometimes it works, but mostly is good to get a draw in the best case.
 +
1684889
 +
1684938
 +
1684993
 +
 +
pier4r nvidia k1 vs xcal50headshot50x
 +
1683071
 +
1684609
 +
1684627
 +
1684648
 +
1684680
 +
1684746
 +
 +
stampid vs teddy88
 +
1683074
 +
1684610
 +
1684630
 +
1684649
 +
1684684
 +
1684742
 +
1684782
 +
1684855
 +
1684894
 +
1684944
 +
1684991
 +
1685203
 +
 +
milkhunter vs mumpsimus
 +
1683069
 +
nice one. Mumpsimus dealing confusing with his scoring routine.
 +
1684612
 +
1684635
 +
1684652
 +
1684686
 +
1684728
 +
1684802
 +
 +
t0tproduction vs heartlessvoid
 +
1683073
 +
1684614
 +
leaving an alone sniper alive with a full health sg is a no. Those chances shouldn't be lost.
 +
1684637
 +
1684656
 +
1684693
 +
1684733
 +
1684793
 +
1684858
 +
1684891
 +
 +
yours_truly vs tsensiert
 +
well...
 +
 +
federico abrile vs ctl
 +
1683075
 +
1684619
 +
1684639
 +
1684655
 +
1684690
 +
1684731
 +
1684799
 +
1684849
 +
1684876
 +
1684933
 +
1684997
 +
</pre>
  
 
==== Round 4 ====
 
==== Round 4 ====
Line 19: Line 318:
 
gtresd vs +_+
 
gtresd vs +_+
 
Game 1 match ID: 1680618.
 
Game 1 match ID: 1680618.
−
Game 2 match ID: 1680820. red team pushing as it did in all the tournament but the push is not yet so refined for high rated players. The push is punished with damage and the blue team scores.
+
Game 2 match ID: 1680820.  
−
Game 3 match ID: 1680872. same pattern.
+
red team pushing as it did in all the tournament but the push is not yet so refined for high rated players. The push is punished with damage and the blue team scores.
−
Game 4 match ID: 1680910. same pattern (the assault always exploding first. Assaults alone while targeted by all are weak!)
+
Game 3 match ID: 1680872.  
−
Game 5 match ID: 1680947. In this case the red team scored but the blue team had a more effective push without too pushing (suicidal) actions.
+
same pattern.
−
Game 6 match ID: 1680975. like above.
+
Game 4 match ID: 1680910.  
 +
same pattern (the assault always exploding first. Assaults alone while targeted by all are weak!)
 +
Game 5 match ID: 1680947.  
 +
In this case the red team scored but the blue team had a more effective push without too pushing (suicidal) actions.
 +
Game 6 match ID: 1680975.  
 +
like above.
  
 
teddy_88 vs kasv (many unreported draws here!)
 
teddy_88 vs kasv (many unreported draws here!)
−
Game 1 match ID: 1680620.
+
Well it seems there are problems. https://forum.gladiabots.com/viewtopic.php?f=6&t=1776 Discussing also in the gladiabots' chat.
−
Game 2 match ID: 1681055. blue team focusing on scoring, losing ground. The red team slowly converts.
+
Game 1 match ID: 1680620. 0-1
−
1681190 fighting about equal. The red sg got heavily damaged and too much of a push is risky. Under 2 minutes the blue team goes scoring but in a confused way.
+
Game 2 match ID: 1681055. 1-1 .
−
1681233 like above, only the two teams blocked each other for long time with equal fighting. The last minute was chaotic.
+
blue team focusing on scoring, losing ground. The red team slowly converts.
−
Game 3 match ID: 1681249. This time the blue team fought the red team to standstill and then scored.
+
1681190 draw.
−
1681272 equal fight in the middle of the map. Under two minutes other resources are targeted but without decision. Also opposite side bases.
+
fighting about equal. The red sg got heavily damaged and too much of a push is risky. Under 2 minutes the blue team goes scoring but in a confused way.
−
1681294 equal fight in the middle of the map. The blue team a tad better (the red team sg as usual heavily damaged). No team really gain grounds. Under two minutes attempts to score resources were done and some were suicidal.
+
1681233 draw.
−
1681322 same pattern, the blue has the sg heavily damaged and then used to harass the reds. The red scored. But then the blue gets the upper hand.
+
like above, only the two teams blocked each other for long time with equal fighting. The last minute was chaotic.
−
1681351 this time the blue do not lose too much healt with the sg. The red try to score but are somehow unable to thanks to better fighting by the blues. Then the blue converts.
+
Game 3 match ID: 1681249. 2-1.
−
Game 4 match ID: 1681416. Both teams fighting to a standstill. The red even loses a bot, but the red converts.  
+
This time the blue team fought the red team to standstill and then scored.
−
Game 5 match ID: 1681471.
+
1681272 draw.
−
1681518
+
equal fight in the middle of the map. Under two minutes other resources are targeted but without decision. Also opposite side bases.
−
Game 6 match ID: 1681549.
+
1681294 2-2 .
−
Game 7 match ID: 1681628.
+
Equal fight in the middle of the map. The blue team a tad better (the red team sg as usual heavily damaged). No team really gain grounds. Under two minutes attempts to score resources were done and some were suicidal.
−
Game 8 match ID: 1681649.
+
1681322 3-2.
 +
same pattern, the blue has the sg heavily damaged and then used to harass the reds. The red scored. But then the blue gets the upper hand.
 +
1681351 4-2
 +
this time the blue do not lose too much healt with the sg. The red try to score but are somehow unable to thanks to better fighting by the blues. Then the blue converts.
 +
Game 4 match ID: 1681416. 5-2.
 +
Both teams fighting to a standstill. The red even loses a bot, but the red converts.  
 +
Game 5 match ID: 1681471. 5-3
 +
1681518 draw.
 +
Game 6 match ID: 1681549. 5-4
 +
Game 7 match ID: 1681628. 5-5 .  
 +
Kasv fixed the ai to take away the enemy sg. Well done!
 +
Game 8 match ID: 1681649. 5-6 .
  
 
thecommonpidgeon vs t0tproduction
 
thecommonpidgeon vs t0tproduction
Line 46: Line 361:
 
Game 2 match ID: 1680685.
 
Game 2 match ID: 1680685.
 
Game 3 match ID: 1680716.
 
Game 3 match ID: 1680716.
−
Game 4 match ID: 1680756. fighting is about equal. Red actually pushes blue back but while doing this loses always a bit of health and then with one unit down loses.
+
Game 4 match ID: 1680756.  
−
Game 5 match ID: 1681431.
+
fighting is about equal. Red actually pushes blue back but while doing this loses always a bit of health and then with one unit down loses.
−
Game 6 match ID: 1681523.
+
Game 5 match ID: 1681431.
 +
see above.
 +
Game 6 match ID: 1681523.
 +
same pattern.
  
 
HeartlessVoid vs SavageX89
 
HeartlessVoid vs SavageX89
Line 54: Line 372:
 
Game 2 match ID: 1680696.
 
Game 2 match ID: 1680696.
 
Game 3 match ID: 1680735.
 
Game 3 match ID: 1680735.
−
Game 4 match ID: 1680764. the red team pushes losing too much health and the blue team converts slowly.
+
Game 4 match ID: 1680764.  
−
Game 5 match ID: 1680828. red team scoring but for a while the red sg was at risk of explosion. It was a close call.
+
the red team pushes losing too much health and the blue team converts slowly.
−
Game 6 match ID: 1680885. same pattern.
+
Game 5 match ID: 1680828.  
 +
red team scoring but for a while the red sg was at risk of explosion. It was a close call.
 +
Game 6 match ID: 1680885.  
 +
same pattern.
  
 
stampid vs Federico Abrile
 
stampid vs Federico Abrile
 
Game 1 match ID: 1680623.
 
Game 1 match ID: 1680623.
−
Game 2 match ID: 1682236.
+
Game 2 match ID: 1682236.  
 +
lots of movements for both teams, hard to follow in fast forward.
 +
1682216
 +
1682845
 +
1682875
 +
1682906
 +
1682961
 +
1682981
 +
 
  
 
umrenato vs ctl
 
umrenato vs ctl
 
Game 1 match ID: 1680622.
 
Game 1 match ID: 1680622.
−
Game 2 match ID: 1682451.
+
Game 2 match ID: 1682451.
 +
blue scoring, red scoring too but red is too aggressive, losing units.
 +
1682819
 +
same pattern but in this case even if the more aggressive team tends to lose units it is able to convert.
 +
1682841
 +
Both scoring, the blue push too much, still in 3 vs 4 hold their ground.
 +
1682883
 +
red too aggressive, but incredibly able to convert. A win is a win, no matter how it is achieved (if legally achieved)
 +
1682927
 +
The blue having better fighting and decision ability this time.
 +
1682949
 +
almost opposite side bases. Red very aggressive, losing lots of health but somehow converting.
 +
 
 +
pier4r nvidia k1 vs milkhunter
 +
1680619
 +
interesting fighting but the red team secures the central resource.
 +
1682808
 +
red team in better control of half of the map but then it goes in the wrong direction losing the opportunity to convert while the blue team recovers.
 +
1682840
 +
opposite side bases. Battle for the center. The reds have a better fighting and convert.
 +
1682872
 +
fighting for the middle map, the red team slightly better and converting.
 +
1682926
 +
The red is subtly better in fighting and converts.
 +
1682955
 +
same pattern of before.Plus opposite side bases.
 +
1682986
 +
Interesting location of bases and resources. This allowed the weaker team, the blue, to somehow compensating for their slightly weaker fighting abilities.
 +
1683019
 +
The blue team incredibly scoring the middle resource, then scattering around confusing the red team.
 +
1683047
 +
usual pattern with the red getting a slight upper hand in fighting and then converting.
 +
 
 +
tsensiert vs xcal50headshotx
 +
one sided.
 +
 
 +
yours truly vs chilio6
 +
1680626
 +
again yours truly with long range shooting, not going to win much.
 +
1682813
 +
Yours truly fixed their AI! A real battle! red scoring early and having the upper hand in the fight, although very slowly.
 +
1682846
 +
opposite side bases. The blue team lose early the sg. The red team converts.
 +
1682874
 +
blue bugging out with the sg. Although in 3 vs 4 they still have better fighting abilities. Opposite side bases.
 +
1682914
 +
Blue team with the bugged sg (do not retreat too long with the resource!). The red this time are able to convert.
 +
1682945
 +
blue team going for aggressive scoring, almost not figghting and winning.
 +
1682995
 +
Red going aggressively scoring, blue not doing much.
 +
1683024
 +
red losing a unit and still holding 3 vs 4. Blue finally scoring.
 +
 
 +
bockwurst vs mumpsimus
 +
Game 1 match ID: 1680617.
 +
red team able to score early and control a good half of the map. Blue team scoring also but the red are well organized.
 +
Game 2 match ID: 1682777.
 +
Battle for central resource. Red team pushing a bit more. Securing resources. Blue team picking up a lot of damage over time.
 +
1682824
 +
blue team with more control over the middle resources. Slowly being able to convert.
 +
1682844
 +
battle for the middle resource. Blue fights, red tries to pick resources. The blue fight is a bit better and the blue team end up controlling most of the map. The reds are not able to push the blues back.
 +
1682880
 +
Battle for the middle part of the map. Blue team more compact, slowly getting the upper hand and converting. Red is not able to push back.
 +
1682917
 +
Same pattern as before. The blue have a subtle advantage on fighting and this pays off in more space and ease in resource collection.
 +
1682948
 +
same pattern as before.
 
</pre>
 
</pre>
  
Line 84: Line 481:
 
Game 1 match ID: 1677014.
 
Game 1 match ID: 1677014.
 
Game 2 match ID: 1677132.
 
Game 2 match ID: 1677132.
−
Game 3 match ID: 1677350. red team trying to score, blue team getting control of more than half of the map and also inflicting quite some damage and then scoring.
+
Game 3 match ID: 1677350.  
−
Game 4 match ID: 1677870. Better fighting skills on the blue side allow to control more than half of the map and then deal quite some damage to the red team near the end of the game.
+
red team trying to score, blue team getting control of more than half of the map and also inflicting quite some damage and then scoring.
−
Game 5 match ID: 1678006. see above. Notice that the blue team doesn't retreat near the border. Not recommended as it can buy time in some edge cases.
+
Game 4 match ID: 1677870.  
 +
Better fighting skills on the blue side allow to control more than half of the map and then deal quite some damage to the red team near the end of the game.
 +
Game 5 match ID: 1678006.  
 +
see above. Notice that the blue team doesn't retreat near the border. Not recommended as it can buy time in some edge cases.
 
Game 6 match ID: 1678089.
 
Game 6 match ID: 1678089.
  
Line 96: Line 496:
 
Game 4 match ID: 1677230.
 
Game 4 match ID: 1677230.
 
Game 5 match ID: 1677288.
 
Game 5 match ID: 1677288.
−
Game 6 match ID: 1677334. almost opposite side bases. Both team trying to score. Fighting almost equal. But the blue sg takes too much damage. The red team control more map and converts.
+
Game 6 match ID: 1677334.  
−
1677367 Both teams trying to score. Fighting again equal but the red eam with small advantages.  Opposite side bases. The blue team has a last second save.
+
almost opposite side bases. Both team trying to score. Fighting almost equal. But the blue sg takes too much damage. The red team control more map and converts.
−
Game 7 match ID: 1677421. Red team a bit better in fighting. Blue team snatches a resource.  Blue team sg takes too much damage. Red team converts in the last second.
+
1677367  
−
Game 8 match ID: 1677455. red team with small ground advantage. After a long fight the advantage gets converted.
+
Both teams trying to score. Fighting again equal but the red eam with small advantages.  Opposite side bases. The blue team has a last second save.
−
Game 9 match ID: 1677605. Red team snatching the central resource earlier. The blue team fights but cannot erode the small but crucial ground advantage of the reds. The reds getting better in the end.  
+
Game 7 match ID: 1677421.  
 +
Red team a bit better in fighting. Blue team snatches a resource.  Blue team sg takes too much damage. Red team converts in the last second.
 +
Game 8 match ID: 1677455.  
 +
red team with small ground advantage. After a long fight the advantage gets converted.
 +
Game 9 match ID: 1677605.  
 +
Red team snatching the central resource earlier. The blue team fights but cannot erode the small but crucial ground advantage of the reds. The reds getting better in the end.  
  
 
savageX86 vs kasv
 
savageX86 vs kasv
 
Game 1 match ID: 1677017.
 
Game 1 match ID: 1677017.
 
Game 2 match ID: 1677302.
 
Game 2 match ID: 1677302.
−
Game 3 match ID: 1677361. Red team scoring, blue team aggressive. Too aggressive.
+
Game 3 match ID: 1677361.  
−
Game 4 match ID: 1677443. see above.
+
Red team scoring, blue team aggressive. Too aggressive.
 +
Game 4 match ID: 1677443.  
 +
see above.
 
Game 5 match ID: 1677472.  
 
Game 5 match ID: 1677472.  
 
Game 6 match ID: 1677516.
 
Game 6 match ID: 1677516.
Line 114: Line 521:
 
Game 2 match ID: 1677077.
 
Game 2 match ID: 1677077.
 
Game 3 match ID: 1677200.
 
Game 3 match ID: 1677200.
−
Game 4 match ID: 1677445. both team trying to score early. Fighting is about equal. Reds have better control of the map.
+
Game 4 match ID: 1677445.  
−
Game 5 match ID: 1677503. The red team chooses a risky base to score, nonetheless the slightly better fighting skills let it convert the result.
+
both team trying to score early. Fighting is about equal. Reds have better control of the map.
−
Game 6 match ID: 1677647. Very balanced but again the blue team could convert with slightly better fighting skills.
+
Game 5 match ID: 1677503.  
 +
The red team chooses a risky base to score, nonetheless the slightly better fighting skills let it convert the result.
 +
Game 6 match ID: 1677647.  
 +
Very balanced but again the blue team could convert with slightly better fighting skills.
  
 
+_+ vs hearthlessvoid
 
+_+ vs hearthlessvoid
Line 122: Line 532:
 
Game 2 match ID: 1677078.
 
Game 2 match ID: 1677078.
 
Game 3 match ID: 1677295.
 
Game 3 match ID: 1677295.
−
Game 4 match ID: 1677345. red team pushing, blue team trying to score but being unable to. Red team has some damage but still it is aggressive. Red team then tries to score at the last moment.
+
Game 4 match ID: 1677345.  
−
Game 5 match ID: 1677389. red team pushing. Blue scoring. Quick resource collection.
+
red team pushing, blue team trying to score but being unable to. Red team has some damage but still it is aggressive. Red team then tries to score at the last moment.
−
Game 6 match ID: 1677490. Blue team scoring, red pushing. The blue team tries to catch resources to aggressively, goes down. The red eliminates the blue in time to score enough resources.
+
Game 5 match ID: 1677389.  
−
Game 7 match ID: 1677539. Blue team pushing in a different way this time, obliterating the reds very quickly. Waiting for the opponent to come in range and get damage. preemptive shooting.
+
red team pushing. Blue scoring. Quick resource collection.
 +
Game 6 match ID: 1677490.  
 +
Blue team scoring, red pushing. The blue team tries to catch resources to aggressively, goes down. The red eliminates the blue in time to score enough resources.
 +
Game 7 match ID: 1677539.  
 +
Blue team pushing in a different way this time, obliterating the reds very quickly. Waiting for the opponent to come in range and get damage. preemptive shooting.
  
 
ctl vs yours_truly
 
ctl vs yours_truly
 
Game 1 match ID: 1677023.
 
Game 1 match ID: 1677023.
−
Game 2 match ID: 1677448. The blue team tries to fight from out of range, not going to work.
+
Game 2 match ID: 1677448.  
−
Game 3 match ID: 1677655. The read teams wins but its sg is quite confused in its actions. Instead of easily scoring getting damage for free.
+
The blue team tries to fight from out of range, not going to work.
 +
Game 3 match ID: 1677655.  
 +
The read teams wins but its sg is quite confused in its actions. Instead of easily scoring getting damage for free.
 
Game 4 match ID: 1677740.
 
Game 4 match ID: 1677740.
 
Game 5 match ID: 1677942.
 
Game 5 match ID: 1677942.
−
Game 6 match ID: 1677997. The blue team with the confused sg that brings a resource to the enemy sniper.
+
Game 6 match ID: 1677997.  
 +
The blue team with the confused sg that brings a resource to the enemy sniper.
  
 
chilio6 vs x50calheadshotx
 
chilio6 vs x50calheadshotx
 
Game 1 match ID: 1677130.
 
Game 1 match ID: 1677130.
−
Game 2 match ID: 1677494. both teams trying to score. Fighting is equal (when the fighting is equal normally even in fast forward the clock proceeds very slow). Red team getting a small space advantage and then converting in the last seconds.  
+
Game 2 match ID: 1677494.  
−
1680355 blue team quickly scoring. Then it has to fight for more resources. The red team scatters to pick backrank resources. Still the read team has better fighting skills and converts.
+
both teams trying to score. Fighting is equal (when the fighting is equal normally even in fast forward the clock proceeds very slow). Red team getting a small space advantage and then converting in the last seconds.  
−
1680396 fighting about equal. Struggle for the central resource.  
+
1680355  
−
1680410 very fought battle. Equalish. Then the sudden actions done in the last seconds rewards the risk.
+
blue team quickly scoring. Then it has to fight for more resources. The red team scatters to pick backrank resources. Still the read team has better fighting skills and converts.
−
1680440 More or less equal fighting, the blue slightly better. The blue team nearer to the center resource. The blue bugs but converts.
+
1680396  
−
1680473 Fighting is about equal. The blue team is a tad better and this on the long run pays off.
+
fighting about equal. Struggle for the central resource.  
−
1680499 Fighting is almost equal. The red get a bit more space and they convert at the end.
+
1680410  
−
1680517 Fighting about equal, red a bit better. Though blue decision to score at least once was good. It is interesting that rating doesn't always tell how a battle will evolve. This because in ranked matches a player has to battle - in most cases - with plenty of variety in terms of opponents approaches. Instead in a tournament one can find nemeses even if the difference in rating is substantial (over 150 rating points of difference)
+
very fought battle. Equalish. Then the sudden actions done in the last seconds rewards the risk.
−
1680535 blue trying to score early. Being a bit not so decided in the action. Gaining little bits of space but also losing health of one unit. It is enough to convert though.
+
1680440  
−
1680563 The blue nearer to the central resource but then the red pushed better, although losing more health. The red converts.
+
More or less equal fighting, the blue slightly better. The blue team nearer to the center resource. The blue bugs but converts.
 +
1680473  
 +
Fighting is about equal. The blue team is a tad better and this on the long run pays off.
 +
1680499  
 +
Fighting is almost equal. The red get a bit more space and they convert at the end.
 +
1680517  
 +
Fighting about equal, red a bit better. Though blue decision to score at least once was good. It is interesting that rating doesn't always tell how a battle will evolve. This because in ranked matches a player has to battle - in most cases - with plenty of variety in terms of opponents approaches. Instead in a tournament one can find nemeses even if the difference in rating is substantial (over 150 rating points of difference)
 +
1680535  
 +
blue trying to score early. Being a bit not so decided in the action. Gaining little bits of space but also losing health of one unit. It is enough to convert though.
 +
1680563  
 +
The blue nearer to the central resource but then the red pushed better, although losing more health. The red converts.
  
 
stampid vs t0tproduction
 
stampid vs t0tproduction
 
Game 1 match ID: 1677018.
 
Game 1 match ID: 1677018.
−
Game 2 match ID: 1678433. blue pushing, red scoring. The blue push is too strong, reds do not retreat in time.
+
Game 2 match ID: 1678433.  
−
1680361 see above.
+
blue pushing, red scoring. The blue push is too strong, reds do not retreat in time.
−
1680400 red team scoring, blue team fighting and then scoring. Teams scattered around, the blue has initially the upper hand then it losts.
+
1680361  
−
1680416 red team scoring.Red team employing an harassing sg that loses too much health.
+
see above.
−
1680445 blue team suicidal. Pushing is a fine art between push and retreat.
+
1680400  
−
1680474 the read team scattering for scoring lead to one unit less quickly and this let the blue team convert.
+
red team scoring, blue team fighting and then scoring. Teams scattered around, the blue has initially the upper hand then it losts.
 +
1680416  
 +
red team scoring.Red team employing an harassing sg that loses too much health.
 +
1680445  
 +
blue team suicidal. Pushing is a fine art between push and retreat.
 +
1680474  
 +
the read team scattering for scoring lead to one unit less quickly and this let the blue team convert.
  
 
milkhunter vs tsensiert
 
milkhunter vs tsensiert
Line 161: Line 594:
  
 
umrenato vs mumpsimus
 
umrenato vs mumpsimus
−
1677016 red team scoring and blue team badly handling 1vs1 aggressions to resource carriers.
+
1677016  
−
1680334 blue team scoring early but losing bots so the red team, that started in a slower mode, converts at the end. For few seconds it was like the blue had a chance.
+
red team scoring and blue team badly handling 1vs1 aggressions to resource carriers.
−
1680360 red team scoring but collecting too much damage. Not going to work.
+
1680334  
−
1680398 blue team better at fighting and the red team disregarding damage, practically one sided.
+
blue team scoring early but losing bots so the red team, that started in a slower mode, converts at the end. For few seconds it was like the blue had a chance.
 +
1680360  
 +
red team scoring but collecting too much damage. Not going to work.
 +
1680398  
 +
blue team better at fighting and the red team disregarding damage, practically one sided.
 
1680412 the mg of the blue team not retreating and holding the place is not going to thelp the blue team.
 
1680412 the mg of the blue team not retreating and holding the place is not going to thelp the blue team.
−
1680444 see above.
+
1680444  
 +
see above.
 
</pre>
 
</pre>
  
Line 172: Line 610:
 
<pre>
 
<pre>
 
t0tproduction vs pier4r nvidia k1
 
t0tproduction vs pier4r nvidia k1
−
1675921 fight relatively equal for a while, then one side pick resources and the other becomes too aggressive.
+
1675921  
−
1676584 blue team scoring, red team first holding then pushing too much, suicidal. Don't push without firing support or without be compact.
+
fight relatively equal for a while, then one side pick resources and the other becomes too aggressive.
−
1676655 the red team loses ground and units when tries to push without support, or when it goes for resources.
+
1676584  
−
1676742 similar patter as above.
+
blue team scoring, red team first holding then pushing too much, suicidal. Don't push without firing support or without be compact.
−
1676776 red team scattered and mowed down while the blue scores.
+
1676655  
−
1676801 red team loses too many units.
+
the red team loses ground and units when tries to push without support, or when it goes for resources.
 +
1676742  
 +
similar patter as above.
 +
1676776  
 +
red team scattered and mowed down while the blue scores.
 +
1676801  
 +
red team loses too many units.
  
 
umrenato vs teddy_88
 
umrenato vs teddy_88
−
1675919 The fighting is equal for a while with one side flanking the other, but then one side is a bit too careless in pushing and loses a unit and then the match.
+
1675919  
−
1676610 both scoring and fighting equally until the blue team become careless with health damage.
+
The fighting is equal for a while with one side flanking the other, but then one side is a bit too careless in pushing and loses a unit and then the match.
−
1676658 blue team fighting, red team tries to score. Red team getting too much damage (better retreat is needed).
+
1676610  
−
1676744 red team tries to score but it is too aggressive and goes down a unit early in the game.
+
both scoring and fighting equally until the blue team become careless with health damage.
−
1676763 blue team scoring and pushing too aggressively, red team not properly retreating.
+
1676658  
−
1676796 red team tries to score, blue team aggressive, red team not retreating properly.
+
blue team fighting, red team tries to score. Red team getting too much damage (better retreat is needed).
−
1676833 The red team goes for scoring but loses units. The blue team pushes but not too hard. Though at the end it is enough to collect resources without problems.
+
1676744  
−
1676883 same as above.
+
red team tries to score but it is too aggressive and goes down a unit early in the game.
 +
1676763  
 +
blue team scoring and pushing too aggressively, red team not properly retreating.
 +
1676796  
 +
red team tries to score, blue team aggressive, red team not retreating properly.
 +
1676833  
 +
The red team goes for scoring but loses units. The blue team pushes but not too hard. Though at the end it is enough to collect resources without problems.
 +
1676883  
 +
same as above.
  
 
savagex89 vs tsensiert
 
savagex89 vs tsensiert
Line 194: Line 646:
  
 
yours_truly vs federico abrile
 
yours_truly vs federico abrile
−
1675927 one side attacks from out of range without pushing, not going to be effective.
+
1675927  
−
1676616 like above.
+
one side attacks from out of range without pushing, not going to be effective.
−
1676664 like above.
+
1676616  
−
1676747 yours truly having problems with fighting. The ai starts the attack too early. Likely all the rest of the matches will be similar.
+
like above.
 +
1676664  
 +
like above.
 +
1676747  
 +
yours truly having problems with fighting. The ai starts the attack too early. Likely all the rest of the matches will be similar.
  
 
x50calheadshotx vs stampid
 
x50calheadshotx vs stampid
−
1675928 one side focused on collecting, the other on fighting. The collecting side is not too careful and loses a unit, the fighting side shows also retreat weakness and then gets worn out.
+
1675928  
−
1676619 blue team scoring, red team fighting. But the blue team fighting is also good.
+
one side focused on collecting, the other on fighting. The collecting side is not too careful and loses a unit, the fighting side shows also retreat weakness and then gets worn out.
−
1676661 red team scoring, the blue retreating too much or too late.
+
1676619  
−
1676738 blue team scoring, red team fighting. The blue team using the sg to harass the red team and keep it at bay.
+
blue team scoring, red team fighting. But the blue team fighting is also good.
−
1676782 red team scoring while keeping the control of enough group with the harassing sg.
+
1676661  
−
1676804 red team going to score, its sg is too aggressive. Blue team gain grounds and resources.
+
red team scoring, the blue retreating too much or too late.
−
1676842 red team harassing the blue with the sg, but the sg goes lost.  Opposite side bases makes things harder and the blue team slowly overwhelms the red one.
+
1676738  
−
1676878 red team scoring with harassing sg extremely close to death. Somehow it managed to succeed.
+
blue team scoring, red team fighting. The blue team using the sg to harass the red team and keep it at bay.
 +
1676782  
 +
red team scoring while keeping the control of enough group with the harassing sg.
 +
1676804  
 +
red team going to score, its sg is too aggressive. Blue team gain grounds and resources.
 +
1676842  
 +
red team harassing the blue with the sg, but the sg goes lost.  Opposite side bases makes things harder and the blue team slowly overwhelms the red one.
 +
1676878  
 +
red team scoring with harassing sg extremely close to death. Somehow it managed to succeed.
  
 
chilio6 vs milkhunter
 
chilio6 vs milkhunter
−
1675925 the all assault hurts but controlling a bit more than half of a map is enough.
+
1675925  
−
1676621 red team scoring, blue team pushing, red team pushing back.
+
the all assault hurts but controlling a bit more than half of a map is enough.
−
1676653 blue team ensuring the ground advantage and that was enough to win.
+
1676621  
−
1676734 blue team holding more than half of the map while scoring.
+
red team scoring, blue team pushing, red team pushing back.
−
1676754 like above.
+
1676653  
−
1676788 like above.
+
blue team ensuring the ground advantage and that was enough to win.
 +
1676734  
 +
blue team holding more than half of the map while scoring.
 +
1676754  
 +
like above.
 +
1676788  
 +
like above.
  
 
mumpsimus vs thecommonpidgeon
 
mumpsimus vs thecommonpidgeon
−
1675922 mumpsimus slowly pushes the opponent. Notice that the opponent loses ground when he has retreated a bot and doesn't push back properly (the bot keeps dancing losing time).
+
1675922  
−
1676623 blue team near to catch the central resource. Red team scoring some resources in the back and then successfully securing the central resource.
+
mumpsimus slowly pushes the opponent. Notice that the opponent loses ground when he has retreated a bot and doesn't push back properly (the bot keeps dancing losing time).
−
1676651 the red team suffers too much damage while fighting almost equally and the blue converts.
+
1676623  
−
1676730 red team with a slightly better push, then scrambling for resources. The blue team pushed in a crucial moment (bases were on the opposite side of the resources) almost getting a grip of the red bases but then the red team hold to score the victory.
+
blue team near to catch the central resource. Red team scoring some resources in the back and then successfully securing the central resource.
−
1676758 again quite close but mumpsimus slight better push is enough to convert.
+
1676651  
−
1676795 very balanced fight for the central resources. The red team was slowly snatching them but the blue team had a surprise in the last second. To watch!
+
the red team suffers too much damage while fighting almost equally and the blue converts.
 +
1676730  
 +
red team with a slightly better push, then scrambling for resources. The blue team pushed in a crucial moment (bases were on the opposite side of the resources) almost getting a grip of the red bases but then the red team hold to score the victory.
 +
1676758  
 +
again quite close but mumpsimus slight better push is enough to convert.
 +
1676795  
 +
very balanced fight for the central resources. The red team was slowly snatching them but the blue team had a surprise in the last second. To watch!
  
 
heartlessvoid vs gtresd
 
heartlessvoid vs gtresd
−
1676089 not a bad game by void that didn't push in 3 vs 2 (difficult to detect). Gtresd having the ground advantage converts.
+
1676089  
−
1675923 the fighting was somewhat balanced until one sg bugged out losing time. Still somehow the side with the bugged sg confused the enemy team enough to convert. Well done.
+
not a bad game by void that didn't push in 3 vs 2 (difficult to detect). Gtresd having the ground advantage converts.
−
1676076 quite balanced fight but one side controlled more space without really losing organization. This while scoring.
+
1675923  
−
1676628 balanced fight for a while. The red team with ground advantage. The blue team with an undecided sg that loses time. Red team converts, blue team tries some sort of flanking but the red team holds.
+
the fighting was somewhat balanced until one sg bugged out losing time. Still somehow the side with the bugged sg confused the enemy team enough to convert. Well done.
−
1676645 Red team holding the center while the blue team scores. Then the blue team tries to scatter itself for resources and loses units in the process.
+
1676076  
−
1676662 Fighting for the middle. The red team goes for side resources, but then it becomes too scattered and the blue team is solid.
+
quite balanced fight but one side controlled more space without really losing organization. This while scoring.
−
1676699 opposite side bases. Red team not decided where to go. The blue team slowly converts.
+
1676628  
 +
balanced fight for a while. The red team with ground advantage. The blue team with an undecided sg that loses time. Red team converts, blue team tries some sort of flanking but the red team holds.
 +
1676645  
 +
Red team holding the center while the blue team scores. Then the blue team tries to scatter itself for resources and loses units in the process.
 +
1676662  
 +
Fighting for the middle. The red team goes for side resources, but then it becomes too scattered and the blue team is solid.
 +
1676699  
 +
opposite side bases. Red team not decided where to go. The blue team slowly converts.
  
 
ctl vs +_+
 
ctl vs +_+
−
1675926 one side slowly pushes the other and then has enough time for collecting resources.
+
1675926  
−
1676073 one side wants to push the other but get distracted by a flanking sg and loses too much time chasing enemies.
+
one side slowly pushes the other and then has enough time for collecting resources.
−
1676082 again one side pushing, gaining a lot of ground and eliminating enemies but not picking resources. Tip: if you have a bot advantage, send one bot to pick resources.
+
1676073  
−
1676126 red team scoring early. blue team pushing. blue team with good push and too focused on fighting although recovering in the end.
+
one side wants to push the other but get distracted by a flanking sg and loses too much time chasing enemies.
−
1676649 again pushing without scoring is nice to see but it is not productive.
+
1676082  
−
1676729 opposite side bases. This should reward the blue team pushing. It really doesn't as the pushing team is not focused enough on resources and it gets lured away by the sg.
+
again one side pushing, gaining a lot of ground and eliminating enemies but not picking resources. Tip: if you have a bot advantage, send one bot to pick resources.
−
1676799 opposite side bases. red team tries to score, blue team pushing. Blue team lured away but recovering. Last minute scoring for the blue team.
+
1676126  
−
1676835 red pushes, blue scores. Red was not able to obliterate the opponents quickly enough.
+
red team scoring early. blue team pushing. blue team with good push and too focused on fighting although recovering in the end.
−
1676872 Blue team scoring early, red team pushing the blues to death. Not enough time to score.
+
1676649  
−
1676904 same as above.
+
again pushing without scoring is nice to see but it is not productive.
−
1676926 The almost opposite side bases favoured the pushing team. After so many draws due to lack of time the match is adjudicated counting the draws.
+
1676729  
 +
opposite side bases. This should reward the blue team pushing. It really doesn't as the pushing team is not focused enough on resources and it gets lured away by the sg.
 +
1676799  
 +
opposite side bases. red team tries to score, blue team pushing. Blue team lured away but recovering. Last minute scoring for the blue team.
 +
1676835  
 +
red pushes, blue scores. Red was not able to obliterate the opponents quickly enough.
 +
1676872  
 +
Blue team scoring early, red team pushing the blues to death. Not enough time to score.
 +
1676904  
 +
same as above.
 +
1676926  
 +
The almost opposite side bases favoured the pushing team. After so many draws due to lack of time the match is adjudicated counting the draws.
  
 
kasv vs bockwurst
 
kasv vs bockwurst
−
1675920 one side gaining slowly space, securing the score advantage and then focusing on the fight. Then the other side is too reckless and loses a unit and get obliterated.
+
1675920  
−
1676160 bockwurst gaining space slowly but also being distracted on two fronts. The point of securing a +1 score advantage and then focusing on fighting helps.
+
one side gaining slowly space, securing the score advantage and then focusing on the fight. Then the other side is too reckless and loses a unit and get obliterated.
−
1676222 here one side loses units early, bockwurst strategy is even more effective against an opponent with less units.
+
1676160  
−
1676318 see above. Interesting at the end the mg was able to retreat for a while against 3 bots.
+
bockwurst gaining space slowly but also being distracted on two fronts. The point of securing a +1 score advantage and then focusing on fighting helps.
−
1676340 once again early unit loss for the weaker side.
+
1676222  
−
1676397 The assault has paper armor against focused fire, don't expose it too much without allies around.
+
here one side loses units early, bockwurst strategy is even more effective against an opponent with less units.
−
1676772 blue team scoring early, red team crushing the blues but scoring too late.
+
1676318  
−
 
+
see above. Interesting at the end the mg was able to retreat for a while against 3 bots.
 +
1676340  
 +
once again early unit loss for the weaker side.
 +
1676397  
 +
The assault has paper armor against focused fire, don't expose it too much without allies around.
 +
1676772  
 +
blue team scoring early, red team crushing the blues but scoring too late.
 
</pre>
 
</pre>
  
Line 265: Line 765:
  
 
gtresd vs stampid
 
gtresd vs stampid
−
1675483 surprisingly stampid lasted quite long, then lost a bot and the match
+
1675483  
−
1675521 one side had a good start but then was too aggressive and lost bots.
+
surprisingly stampid lasted quite long, then lost a bot and the match
−
1675552 stampid not bad but again gtresd holds more than half of the map and then picks the resources.
+
1675521  
−
1675593 one side focused on resources earlier on, but then losing the advantage.
+
one side had a good start but then was too aggressive and lost bots.
−
1675629 really the difference in rating is not visible on the map. At the end gtresd prevails as the opponent loses units, but until a certain point the weaker side holds.
+
1675552  
−
1675650 gtresd goes down but then recovers thanks to better fighting performance.
+
stampid not bad but again gtresd holds more than half of the map and then picks the resources.
 +
1675593  
 +
one side focused on resources earlier on, but then losing the advantage.
 +
1675629  
 +
really the difference in rating is not visible on the map. At the end gtresd prevails as the opponent loses units, but until a certain point the weaker side holds.
 +
1675650  
 +
gtresd goes down but then recovers thanks to better fighting performance.
  
 
savageX89 vs umrenato
 
savageX89 vs umrenato
−
1675480 one sided
+
1675480  
−
1675525 one side too aggressive, losing bots
+
one sided
−
1675554 see above.
+
1675525  
−
1675591 sides are exchanging victories. Quite interesting.
+
one side too aggressive, losing bots
−
1675622 2-2 so far. But one side takes the lead. Plenty of suicidal push.
+
1675554  
−
1675648 one side gets 2 points lead in the match.
+
see above.
−
1675675 one side is more aggressive than the other, in a suicidal way. Don't push more than you can retreat (in case of need).
+
1675591  
−
1675704 somehow one side got more coordinated over time and won consistently.
+
sides are exchanging victories. Quite interesting.
 +
1675622  
 +
2-2 so far. But one side takes the lead. Plenty of suicidal push.
 +
1675648  
 +
one side gets 2 points lead in the match.
 +
1675675  
 +
one side is more aggressive than the other, in a suicidal way. Don't push more than you can retreat (in case of need).
 +
1675704  
 +
somehow one side got more coordinated over time and won consistently.
  
 
milkhunter vs bockwurst
 
milkhunter vs bockwurst
−
1675484 highly tactical. Battle for the center. Bockwurst pushing a bit better. Milkhunter focusing on resources. Then bockwurst got split.
+
1675484  
−
1675527 complicated base positions here. Bockwurst always having some more space but the mg of milky shoots back. In a final push milky loses units but closes the gap.
+
highly tactical. Battle for the center. Bockwurst pushing a bit better. Milkhunter focusing on resources. Then bockwurst got split.
−
1675556 very high level match where micro differences determine the result. Balanced fight in the middle of the map, although Bockwurst sniper gets quite some damage. Risky. Opposite side bases do not help too.
+
1675527  
−
1675600 A map where the center is crucial. Bockwurst slowly pushing and then converting although in the last seconds.
+
complicated base positions here. Bockwurst always having some more space but the mg of milky shoots back. In a final push milky loses units but closes the gap.
−
1675630 opposite side bases. Milky pushes although strugglinh, bockwurst ignores the resource carries and milky converts. Super balanced games.
+
1675556  
−
1675653 Once again map with mostly central resources. Fighting battle. Bockwurst gets the upper hand. Notice that with heavily damaged bots pushing is hard because it is risky. Notice how a proper mg retreat is crucial otherwise it is going to absorb too much damage.
+
very high level match where micro differences determine the result. Balanced fight in the middle of the map, although Bockwurst sniper gets quite some damage. Risky. Opposite side bases do not help too.
−
16755689 And again middle map fight. May sound repetitive but there is a whole lot of small fatal details in those battles. Each small space gained is crucial. Milkhunter getting some damage that inhibits the push so bockwurst has some seconds to score.
+
1675600  
−
1675738 Bockwurst having a better push but milky snatching resources early. Then milky did not manage a push properly, loses a unit and the game.
+
A map where the center is crucial. Bockwurst slowly pushing and then converting although in the last seconds.
−
1675779 Milky going for an early score. Bockwurst trying to go aggressive. Splitting milk but then being scattered on the map. Still every second counts until the last one.
+
1675630  
−
1675802 both fighting for the center. Bockwurst with a slight advantage. Nonetheless milky with a refined resource collection under fire snatches the needed resources and makes the score of the match closer.
+
opposite side bases. Milky pushes although strugglinh, bockwurst ignores the resource carries and milky converts. Super balanced games.
−
1675836 Milky! Like the last game. From 5-2 to 5-4. Each match can be the last.
+
1675653  
−
1675851 Very close fighting battle for the center. Milky pushing but losing health. Being pushed back. Bockwurst thanks to the counterattack gets a resources but again each second counts.
+
Once again map with mostly central resources. Fighting battle. Bockwurst gets the upper hand. Notice that with heavily damaged bots pushing is hard because it is risky. Notice how a proper mg retreat is crucial otherwise it is going to absorb too much damage.
−
1675866 Battle for the center. Milky snatches a resource under fire. One more and that's it. great comeback.
+
16755689  
−
1675878 Battle for the center. Milky again snatches one resource under fire but this leaves one bot too exposed and he goes a unit down. From there winning the game is difficult. Well done to both, and Bockwurst prevails. What a battle!
+
And again middle map fight. May sound repetitive but there is a whole lot of small fatal details in those battles. Each small space gained is crucial. Milkhunter getting some damage that inhibits the push so bockwurst has some seconds to score.
 +
1675738  
 +
Bockwurst having a better push but milky snatching resources early. Then milky did not manage a push properly, loses a unit and the game.
 +
1675779  
 +
Milky going for an early score. Bockwurst trying to go aggressive. Splitting milk but then being scattered on the map. Still every second counts until the last one.
 +
1675802  
 +
both fighting for the center. Bockwurst with a slight advantage. Nonetheless milky with a refined resource collection under fire snatches the needed resources and makes the score of the match closer.
 +
1675836  
 +
Milky! Like the last game. From 5-2 to 5-4. Each match can be the last.
 +
1675851  
 +
Very close fighting battle for the center. Milky pushing but losing health. Being pushed back. Bockwurst thanks to the counterattack gets a resources but again each second counts.
 +
1675866  
 +
Battle for the center. Milky snatches a resource under fire. One more and that's it. great comeback.
 +
1675878  
 +
Battle for the center. Milky again snatches one resource under fire but this leaves one bot too exposed and he goes a unit down. From there winning the game is difficult. Well done to both, and Bockwurst prevails. What a battle!
  
 
pier4r nvidia k1 vs +_+
 
pier4r nvidia k1 vs +_+
−
1675486 one sided
+
1675486  
−
1675529 close but one side focus on the resources the other on the enemy team.
+
one sided
−
1675559 the fight is close. But one side focus on the resources and it is able to damage the enemy units enough.
+
1675529  
−
1675602 the stronger side on paper get pushed away but converts thanks to the fact that the other side doesn't care about resources.
+
close but one side focus on the resources the other on the enemy team.
−
1675633 oppsite side bases. One team is too focused on fighting. Get flanked, loses units.
+
1675559  
−
1675655 again the fighting is balanced, but one side picks resources.
+
the fight is close. But one side focus on the resources and it is able to damage the enemy units enough.
−
1675681 see above.
+
1675602  
 +
the stronger side on paper get pushed away but converts thanks to the fact that the other side doesn't care about resources.
 +
1675633  
 +
opposite side bases. One team is too focused on fighting. Get flanked, loses units.
 +
1675655  
 +
again the fighting is balanced, but one side picks resources.
 +
1675681  
 +
see above.
  
 
thecommonpidgeon vs yours_truly
 
thecommonpidgeon vs yours_truly
−
1675479 yours truly has a too conservative retreat
+
1675479  
−
1675522 one side got enough territorial advantage, then pushed for resources.
+
yours truly has a too conservative retreat
−
1675548 like above. One side is too conservative.
+
1675522  
−
1675583 one side conservative and then even losing units? Not a way to win a game.
+
one side got enough territorial advantage, then pushed for resources.
−
1675621 quick resource collection wins.
+
1675548  
−
1675647 see above. No real push for the side not collecting resources, therefore no real threat.
+
like above. One side is too conservative.
 +
1675583  
 +
one side conservative and then even losing units? Not a way to win a game.
 +
1675621  
 +
quick resource collection wins.
 +
1675647  
 +
see above. No real push for the side not collecting resources, therefore no real threat.
  
 
clt vs t0tproduction
 
clt vs t0tproduction
−
1675478 balanced until one side lost a bot. Less bots, likely defeat comes.
+
1675478  
−
1675535 quite balanced and at the end an isolated 1vs1 decided the match.
+
balanced until one side lost a bot. Less bots, likely defeat comes.
−
1675566 one side converted the small fighting advantage to victory.
+
1675535  
−
1675607 one side had a better push but then got split from a flanking resource carrier and lost. Lesson learned: focus your team in the proper direction.
+
quite balanced and at the end an isolated 1vs1 decided the match.
−
1675643 one side has a better push, and the accidental flanking from the opponent is not dangerous enough. 1vs1 the sg should be able to annoy the sniper.
+
1675566  
−
1675669 one side gets pushed and cornered but then lures away the sniper somehow. That was the chance to kill the sniper. Chance that was not used.
+
one side converted the small fighting advantage to victory.
−
1675700 the fight was close until one side lost a bot due to exceeding aggressiveness.
+
1675607  
−
1675742 close fight, one side gaining slowly terrain and having a better scoring approach.
+
one side had a better push but then got split from a flanking resource carrier and lost. Lesson learned: focus your team in the proper direction.
−
1675781 opposite side bases. Fighting is important. The sg of one side sneaks away but then has a poor 1vs1 handling vs a sniper. The side with the sniper winning on the sg is victorious.
+
1675643  
 +
one side has a better push, and the accidental flanking from the opponent is not dangerous enough. 1vs1 the sg should be able to annoy the sniper.
 +
1675669  
 +
one side gets pushed and cornered but then lures away the sniper somehow. That was the chance to kill the sniper. Chance that was not used.
 +
1675700  
 +
the fight was close until one side lost a bot due to exceeding aggressiveness.
 +
1675742  
 +
close fight, one side gaining slowly terrain and having a better scoring approach.
 +
1675781  
 +
opposite side bases. Fighting is important. The sg of one side sneaks away but then has a poor 1vs1 handling vs a sniper. The side with the sniper winning on the sg is victorious.
  
 
chilio6 vs kasv
 
chilio6 vs kasv
−
1675477 one side was able to confuse the other in retargeting terms. Lesson learned: push a bit more.
+
1675477  
−
1675537 one side doesn't really care about retreating. Too aggressive.
+
one side was able to confuse the other in retargeting terms. Lesson learned: push a bit more.
−
1675572 see above.
+
1675537  
−
1675612 same pattern as before. One side too aggressive or nto focused on resources.
+
one side doesn't really care about retreating. Too aggressive.
−
1675637 a victorious all assault approach that forgets to pick resources and gets too aggressive in the end.
+
1675572  
−
1675659 the all assault side holds, push, but doesn't score.
+
see above.
−
1675719 While matches are being resolved chilio is changing the AI. Interesting how the result changes. But kasv is too aggressive. Retreat before it is too late! Or push keeping in mind that you may need to retreat.
+
1675612  
−
1675757 chilio fighting better at first, but then losing a unit and forgetting about resources.
+
same pattern as before. One side too aggressive or nto focused on resources.
−
1675787 chilio still thinkering with the ai while the round proceeds. The tinkering produces a better fighting result but still no resources picked. Not necessarily the better fighting side wins if resources are picked too late.
+
1675637  
−
1675819 once again, one side fights better, the other gets the resources.
+
a victorious all assault approach that forgets to pick resources and gets too aggressive in the end.
−
1675843 see above.
+
1675659  
−
1675861 see above, but scoreless.
+
the all assault side holds, push, but doesn't score.
−
1675876 One side destroys the other (notice how properly coordinated and not suicidal that side is) and then had time to score. 5-4 .
+
1675719  
−
1675897 Both side equal in fighting. one also scoring.
+
While matches are being resolved chilio is changing the AI. Interesting how the result changes. But kasv is too aggressive. Retreat before it is too late! Or push keeping in mind that you may need to retreat.
 +
1675757  
 +
chilio fighting better at first, but then losing a unit and forgetting about resources.
 +
1675787  
 +
chilio still thinkering with the ai while the round proceeds. The tinkering produces a better fighting result but still no resources picked. Not necessarily the better fighting side wins if resources are picked too late.
 +
1675819  
 +
once again, one side fights better, the other gets the resources.
 +
1675843  
 +
see above.
 +
1675861  
 +
see above, but scoreless.
 +
1675876  
 +
One side destroys the other (notice how properly coordinated and not suicidal that side is) and then had time to score. 5-4 .
 +
1675897  
 +
Both side equal in fighting. one also scoring.
  
  
 
mumpsimus vs federico abrile
 
mumpsimus vs federico abrile
−
1675485 not one sided as expected. Although mumpsimus holds well with 3 bots while the 4th is scoring.
+
1675485  
−
1675539 mumpsimus quickly focusing on resources
+
not one sided as expected. Although mumpsimus holds well with 3 bots while the 4th is scoring.
−
1675575 retreating with a resources sometimes it is hurtful. But more or less same pattern of the previous games.
+
1675539  
−
1675640 one side goes for resources in a split way, then turns the table and split the opponent and then wins.
+
mumpsimus quickly focusing on resources
−
1675662 plenty of resources right around the middle of the map. The weaker side holds but doesn't push enough. The stronger side slowly converts.
+
1675575  
−
1675617 like above.
+
retreating with a resources sometimes it is hurtful. But more or less same pattern of the previous games.
 +
1675640  
 +
one side goes for resources in a split way, then turns the table and split the opponent and then wins.
 +
1675662  
 +
plenty of resources right around the middle of the map. The weaker side holds but doesn't push enough. The stronger side slowly converts.
 +
1675617  
 +
like above.
  
 
teddy_88 vs tsensiert
 
teddy_88 vs tsensiert
−
1675476 one sided
+
1675476  
−
1675546 like above.
+
one sided
 +
1675546  
 +
like above.
 
won't report more matches of this match for obvious reasons.
 
won't report more matches of this match for obvious reasons.
  
 
x50calheadshotx vs heartlessvoid
 
x50calheadshotx vs heartlessvoid
−
1675482 quite balanced but one side pushes always a bit more, the other is too conservative. Opposide side bases too.
+
1675482  
−
1675550 one side getting more than half of the map. Then gathering resources.
+
quite balanced but one side pushes always a bit more, the other is too conservative. Opposide side bases too.
−
1675585 Good fighting by heartless that gains slowly territorial advantage and then resources.
+
1675550  
−
1675623 fighting for central resources with opposite side bases. Void has a better push and converts.
+
one side getting more than half of the map. Then gathering resources.
−
1675642 void holds the middle of the map without problems.
+
1675585  
−
1675666 see above. If one controls half of the map and then some, while scoring resources, the result is clear. In a 4 vs 3 fight one has to find way to push the side with 3 units.
+
Good fighting by heartless that gains slowly territorial advantage and then resources.
−
1675697 very close fighting battle. Void wins due to better pushing ability.
+
1675623  
 +
fighting for central resources with opposite side bases. Void has a better push and converts.
 +
1675642  
 +
void holds the middle of the map without problems.
 +
1675666  
 +
see above. If one controls half of the map and then some, while scoring resources, the result is clear. In a 4 vs 3 fight one has to find way to push the side with 3 units.
 +
1675697  
 +
very close fighting battle. Void wins due to better pushing ability.
 
</pre>
 
</pre>

Latest revision as of 01:19, 16 February 2019

A page to collect annotations for tournaments organized by Pier4r.

Links

Gladiabots cup 2019.02 collection

Stage 3 Top1-3

milkhunter vs mumpsimus
Game 1 match ID: 1688573.
Game 2 match ID: 1690701.
Game 3 match ID: 1690744.
Game 4 match ID: 1690782.

bockwurst vs mumpsimus
Game 1 match ID: 1688574.
Game 2 match ID: 1689628.
Game 3 match ID: 1690638.
Game 4 match ID: 1690704.

bockwurst vs milkhunter
Game 1 match ID: 1688575.
Game 2 match ID: 1689642.
Game 3 match ID: 1690645.
Game 4 match ID: 1690709.
Game 5 match ID: 1690745.
1690785
Game 6 match ID: 1690794.

Stage 2 Top7-9 and Top4-6

### top4-6
pier4r nvidia k1 vs gtresd
Game 1 match ID: 1687565.
Game 2 match ID: 1688335.
Game 3 match ID: 1688384.
close one, gtresd went 3 vs 4 for a little bit.
1688540
super close
1688549
blue team sg bugged out

thecommonpigeon vs pier4r nvidia k1
Game 1 match ID: 1687564.
Game 2 match ID: 1688114.
Game 3 match ID: 1688143.
Game 4 match ID: 1688308.
1688537

gtresd vs thecommonpigeon
Game 1 match ID: 1687566.
Game 2 match ID: 1688113.
Game 3 match ID: 1688140.
Game 4 match ID: 1688309.

### top7-9
heartlessvoid vs stampid
Game 1 match ID: 1687560.
Game 2 match ID: 1688144.
Game 3 match ID: 1688159.
1688530

kasv vs stampid
Game 1 match ID: 1687561.
Game 2 match ID: 1688100.
Game 3 match ID: 1688118.
Game 4 match ID: 1688146.

kasv vs heartlessvoid
Game 1 match ID: 1687562.
1688104
Game 2 match ID: 1688153.
Game 3 match ID: 1688206.
Game 4 match ID: 1688346.

Stage 1

Round 6

Last round of the swiss system.

See also: https://forum.gladiabots.com/viewtopic.php?f=27&t=1765&p=18429#p18429 

bockwurst vs thecommonpigeon
Game 1 match ID: 1685220.
Game 2 match ID: 1685570.
Game 3 match ID: 1685904.
Game 4 match ID: 1685913.
Game 5 match ID: 1685936.
Game 6 match ID: 1685982.

gtresd vs milkhunter
Game 1 match ID: 1685221.
Game 2 match ID: 1685726.
Game 3 match ID: 1685889.
1686496
1686512
1686539
1686570
1686592
1686664
1686704

kasv vs heartlessvoid
Bugging out again. Second match with kasv. (it bugs when he changes the ai)
https://forum.gladiabots.com/viewtopic.php?f=6&t=1776&p=18430#p18430
Game 1 match ID: 1685224. 1-0
Game 2 match ID: 1685580. 1-1 
Game 3 match ID: 1685604. 1-2
Game 4 match ID: 1685627. 1-3
1685657 draw
Game 5 match ID: 1685670. 1-4
Game 6 match ID: 1685676. 2-4
Game 7 match ID: 1685692. 2-5
Game 8 match ID: 1685700. 3-5
Game 9 match ID: 1685712. 4-5
Game 10 match ID: 1685727. 5-5
1686484 6-5

t0tproduction vs chilio6
1685225
1686485
1686526
1686556
1686584
1686645
1686695
1686742
1686784
1686480

+_+ vs mumpsimus
1685222
interesting how +_+ pushes.
1686486
1686500
1686550
1686582
1686641

pier4r nvidia k1 vs teddy 88
1685223
1686489
1686502
1686542
1686574
1686633

stampid vs umrenato
1685227
1686490
1686517
1686545
1686577
1686636
1686689
1686725

savageX89 vs yours_truly
1685229
1686492
1686504
1686531
1686566
1686586
1686655
1686692

x50calheadshot vs ctl
1685226
1686494
1686509
1686535
1686580
1686602
1686669
1686701

Round 5

Today I am pretty tired. Going though a lot of matches seems easy but it is not (try yourself, I listed the IDs here). So this time I really list at least the IDs trying to pick the draws from chat.gladiabots.com

I find resolving matches better than waiting an additional day to hope to have more energy. Otherwise it lasts too long.

2019-02-12 22-30. Nah. 10+ games per match with balanced performance takes too much time of my little time budget. Each game in a match is 10 minutes waiting plus at least 5 minutes overhead and resolution. So 10 games are at least 150 minutes or 2h 30m if not more. It is too much for a day.

Starting splitting round in multiple days. Resolving more 6 or more iterations per day is what I can really afford.

Also the swiss system is starting to settle. Lots of balanced matches with plenty of games. 

bockwurst vs gtresd
1683067
1683187
Game 1 match ID: 1683213.
Game 2 match ID: 1683237.
1683730 
great game. Fight for the center resource but the approach of bockwurst "I go +1 and then I push" almost backfired.
1683787 
also very nice.
Game 3 match ID: 1683844.
Game 4 match ID: 1683867.
Game 5 match ID: 1683890.
Game 6 match ID: 1684229.

kasv vs thecommonpidgeon
Game 1 match ID: 1683070.
Game 2 match ID: 1683118.
1683144
Game 3 match ID: 1683176.
Game 4 match ID: 1683205.
Game 5 match ID: 1683240.
Game 6 match ID: 1683281.

+_+ vs umrenato
Game 1 match ID: 1683072. 
Blue team super push but the red have a nice collecting approach
Game 2 match ID: 1683798.
The red team goes a bit too much for the push. The blue may punish them more often than not. We will see.
Game 3 match ID: 1683862.
1683862
1684622
1684643
1684658
1684699

savageX89 vs chilio6
1683077
1684605
1684626
1684653
1684691
1684738
1684788
1684862
Tip. Don't score only in the last 30 seconds. Sometimes it works, but mostly is good to get a draw in the best case.
1684889
1684938
1684993

pier4r nvidia k1 vs xcal50headshot50x
1683071
1684609
1684627
1684648
1684680
1684746

stampid vs teddy88
1683074
1684610
1684630
1684649
1684684
1684742
1684782
1684855
1684894
1684944
1684991
1685203

milkhunter vs mumpsimus
1683069
nice one. Mumpsimus dealing confusing with his scoring routine.
1684612
1684635
1684652
1684686
1684728
1684802

t0tproduction vs heartlessvoid
1683073
1684614
leaving an alone sniper alive with a full health sg is a no. Those chances shouldn't be lost.
1684637
1684656
1684693
1684733
1684793
1684858
1684891

yours_truly vs tsensiert
well...

federico abrile vs ctl
1683075
1684619 
1684639
1684655
1684690
1684731
1684799
1684849
1684876
1684933
1684997

Round 4

Same as round 3, people where active before me (neat!) so I'll go through some of the matches and still if I have time. I also observed that the great GFX with his discord integration (see chat.gladiabots.com) reports the matches there and also the draws. Thus if it is not too time intensive I will check if there were draws in the chat and I'll write the matchid here. 

gtresd vs +_+
Game 1 match ID: 1680618.
Game 2 match ID: 1680820. 
red team pushing as it did in all the tournament but the push is not yet so refined for high rated players. The push is punished with damage and the blue team scores.
Game 3 match ID: 1680872. 
same pattern.
Game 4 match ID: 1680910. 
same pattern (the assault always exploding first. Assaults alone while targeted by all are weak!)
Game 5 match ID: 1680947. 
In this case the red team scored but the blue team had a more effective push without too pushing (suicidal) actions.
Game 6 match ID: 1680975. 
like above.

teddy_88 vs kasv (many unreported draws here!)
Well it seems there are problems. https://forum.gladiabots.com/viewtopic.php?f=6&t=1776 Discussing also in the gladiabots' chat.
Game 1 match ID: 1680620. 0-1 
Game 2 match ID: 1681055. 1-1 . 
blue team focusing on scoring, losing ground. The red team slowly converts.
1681190 draw. 
fighting about equal. The red sg got heavily damaged and too much of a push is risky. Under 2 minutes the blue team goes scoring but in a confused way.
1681233 draw. 
like above, only the two teams blocked each other for long time with equal fighting. The last minute was chaotic.
Game 3 match ID: 1681249. 2-1. 
This time the blue team fought the red team to standstill and then scored.
1681272 draw. 
equal fight in the middle of the map. Under two minutes other resources are targeted but without decision. Also opposite side bases.
1681294 2-2 . 
Equal fight in the middle of the map. The blue team a tad better (the red team sg as usual heavily damaged). No team really gain grounds. Under two minutes attempts to score resources were done and some were suicidal.
1681322 3-2. 
same pattern, the blue has the sg heavily damaged and then used to harass the reds. The red scored. But then the blue gets the upper hand.
1681351 4-2 
this time the blue do not lose too much healt with the sg. The red try to score but are somehow unable to thanks to better fighting by the blues. Then the blue converts.
Game 4 match ID: 1681416. 5-2. 
Both teams fighting to a standstill. The red even loses a bot, but the red converts. 
Game 5 match ID: 1681471. 5-3
1681518 draw.
Game 6 match ID: 1681549. 5-4
Game 7 match ID: 1681628. 5-5 . 
Kasv fixed the ai to take away the enemy sg. Well done!
Game 8 match ID: 1681649. 5-6 .

thecommonpidgeon vs t0tproduction
Game 1 match ID: 1680621.
Game 2 match ID: 1680685.
Game 3 match ID: 1680716.
Game 4 match ID: 1680756. 
fighting is about equal. Red actually pushes blue back but while doing this loses always a bit of health and then with one unit down loses.
Game 5 match ID: 1681431. 
see above.
Game 6 match ID: 1681523. 
same pattern.

HeartlessVoid vs SavageX89
Game 1 match ID: 1680624.
Game 2 match ID: 1680696.
Game 3 match ID: 1680735.
Game 4 match ID: 1680764. 
the red team pushes losing too much health and the blue team converts slowly.
Game 5 match ID: 1680828. 
red team scoring but for a while the red sg was at risk of explosion. It was a close call.
Game 6 match ID: 1680885. 
same pattern.

stampid vs Federico Abrile
Game 1 match ID: 1680623.
Game 2 match ID: 1682236. 
lots of movements for both teams, hard to follow in fast forward.
1682216 
1682845
1682875
1682906
1682961
1682981


umrenato vs ctl
Game 1 match ID: 1680622.
Game 2 match ID: 1682451. 
blue scoring, red scoring too but red is too aggressive, losing units.
1682819 
same pattern but in this case even if the more aggressive team tends to lose units it is able to convert.
1682841 
Both scoring, the blue push too much, still in 3 vs 4 hold their ground.
1682883
red too aggressive, but incredibly able to convert. A win is a win, no matter how it is achieved (if legally achieved)
1682927
The blue having better fighting and decision ability this time.
1682949
almost opposite side bases. Red very aggressive, losing lots of health but somehow converting.

pier4r nvidia k1 vs milkhunter
1680619 
interesting fighting but the red team secures the central resource.
1682808 
red team in better control of half of the map but then it goes in the wrong direction losing the opportunity to convert while the blue team recovers. 
1682840
opposite side bases. Battle for the center. The reds have a better fighting and convert.
1682872
fighting for the middle map, the red team slightly better and converting.
1682926
The red is subtly better in fighting and converts.
1682955
same pattern of before.Plus opposite side bases.
1682986
Interesting location of bases and resources. This allowed the weaker team, the blue, to somehow compensating for their slightly weaker fighting abilities.
1683019
The blue team incredibly scoring the middle resource, then scattering around confusing the red team.
1683047
usual pattern with the red getting a slight upper hand in fighting and then converting.

tsensiert vs xcal50headshotx
one sided.

yours truly vs chilio6
1680626 
again yours truly with long range shooting, not going to win much.
1682813 
Yours truly fixed their AI! A real battle! red scoring early and having the upper hand in the fight, although very slowly.
1682846
opposite side bases. The blue team lose early the sg. The red team converts.
1682874
blue bugging out with the sg. Although in 3 vs 4 they still have better fighting abilities. Opposite side bases.
1682914
Blue team with the bugged sg (do not retreat too long with the resource!). The red this time are able to convert.
1682945
blue team going for aggressive scoring, almost not figghting and winning.
1682995
Red going aggressively scoring, blue not doing much.
1683024
red losing a unit and still holding 3 vs 4. Blue finally scoring.

bockwurst vs mumpsimus
Game 1 match ID: 1680617. 
red team able to score early and control a good half of the map. Blue team scoring also but the red are well organized.
Game 2 match ID: 1682777. 
Battle for central resource. Red team pushing a bit more. Securing resources. Blue team picking up a lot of damage over time.
1682824 
blue team with more control over the middle resources. Slowly being able to convert.
1682844 
battle for the middle resource. Blue fights, red tries to pick resources. The blue fight is a bit better and the blue team end up controlling most of the map. The reds are not able to push the blues back.
1682880
Battle for the middle part of the map. Blue team more compact, slowly getting the upper hand and converting. Red is not able to push back.
1682917
Same pattern as before. The blue have a subtle advantage on fighting and this pays off in more space and ease in resource collection.
1682948
same pattern as before.

Round 3

In this round several players were active before me. That is great (less waiting time for myself and activity for all!). So several games were played and resolved. The only problem is that when a lot of games are resolved I cannot see them in the tournament tab in game (that is only 30 matches long or some similar length).

Fortunately the great GFX (gladiabots dev) used the toornament api to collect at lest the matchids of games where there was a win in toornament. In this way draws may be lost. Draws are still informative but if they aren't reported we try to make use of what we have at our hands.

Also I collect the matchids here as they are easier to find than in toornament.

I may go through some of the already reported matches to annotate them, but only if I have time. 

bockwurst vs teddy_88
Game 1 match ID: 1677014.
Game 2 match ID: 1677132.
Game 3 match ID: 1677350. 
red team trying to score, blue team getting control of more than half of the map and also inflicting quite some damage and then scoring.
Game 4 match ID: 1677870. 
Better fighting skills on the blue side allow to control more than half of the map and then deal quite some damage to the red team near the end of the game.
Game 5 match ID: 1678006. 
see above. Notice that the blue team doesn't retreat near the border. Not recommended as it can buy time in some edge cases.
Game 6 match ID: 1678089.

pier4r nvidia k1 vs gtresd
Game 1 match ID: 1677015.
Game 2 match ID: 1677069.
Game 3 match ID: 1677141.
1677185
Game 4 match ID: 1677230.
Game 5 match ID: 1677288.
Game 6 match ID: 1677334. 
almost opposite side bases. Both team trying to score. Fighting almost equal. But the blue sg takes too much damage. The red team control more map and converts.
1677367 
Both teams trying to score. Fighting again equal but the red eam with small advantages.  Opposite side bases. The blue team has a last second save.
Game 7 match ID: 1677421. 
Red team a bit better in fighting. Blue team snatches a resource.  Blue team sg takes too much damage. Red team converts in the last second.
Game 8 match ID: 1677455. 
red team with small ground advantage. After a long fight the advantage gets converted.
Game 9 match ID: 1677605. 
Red team snatching the central resource earlier. The blue team fights but cannot erode the small but crucial ground advantage of the reds. The reds getting better in the end. 

savageX86 vs kasv
Game 1 match ID: 1677017.
Game 2 match ID: 1677302.
Game 3 match ID: 1677361. 
Red team scoring, blue team aggressive. Too aggressive.
Game 4 match ID: 1677443. 
see above.
Game 5 match ID: 1677472. 
Game 6 match ID: 1677516.

federico abrile vs thecommonpigeon
Game 1 match ID: 1677019.
Game 2 match ID: 1677077.
Game 3 match ID: 1677200.
Game 4 match ID: 1677445. 
both team trying to score early. Fighting is about equal. Reds have better control of the map.
Game 5 match ID: 1677503. 
The red team chooses a risky base to score, nonetheless the slightly better fighting skills let it convert the result.
Game 6 match ID: 1677647. 
Very balanced but again the blue team could convert with slightly better fighting skills.

+_+ vs hearthlessvoid
Game 1 match ID: 1677020.
Game 2 match ID: 1677078.
Game 3 match ID: 1677295.
Game 4 match ID: 1677345. 
red team pushing, blue team trying to score but being unable to. Red team has some damage but still it is aggressive. Red team then tries to score at the last moment.
Game 5 match ID: 1677389. 
red team pushing. Blue scoring. Quick resource collection.
Game 6 match ID: 1677490. 
Blue team scoring, red pushing. The blue team tries to catch resources to aggressively, goes down. The red eliminates the blue in time to score enough resources.
Game 7 match ID: 1677539. 
Blue team pushing in a different way this time, obliterating the reds very quickly. Waiting for the opponent to come in range and get damage. preemptive shooting.

ctl vs yours_truly
Game 1 match ID: 1677023.
Game 2 match ID: 1677448. 
The blue team tries to fight from out of range, not going to work.
Game 3 match ID: 1677655. 
The read teams wins but its sg is quite confused in its actions. Instead of easily scoring getting damage for free.
Game 4 match ID: 1677740.
Game 5 match ID: 1677942.
Game 6 match ID: 1677997. 
The blue team with the confused sg that brings a resource to the enemy sniper.

chilio6 vs x50calheadshotx
Game 1 match ID: 1677130.
Game 2 match ID: 1677494. 
both teams trying to score. Fighting is equal (when the fighting is equal normally even in fast forward the clock proceeds very slow). Red team getting a small space advantage and then converting in the last seconds. 
1680355 
blue team quickly scoring. Then it has to fight for more resources. The red team scatters to pick backrank resources. Still the read team has better fighting skills and converts.
1680396 
fighting about equal. Struggle for the central resource. 
1680410 
very fought battle. Equalish. Then the sudden actions done in the last seconds rewards the risk.
1680440 
More or less equal fighting, the blue slightly better. The blue team nearer to the center resource. The blue bugs but converts.
1680473 
Fighting is about equal. The blue team is a tad better and this on the long run pays off.
1680499 
Fighting is almost equal. The red get a bit more space and they convert at the end.
1680517 
Fighting about equal, red a bit better. Though blue decision to score at least once was good. It is interesting that rating doesn't always tell how a battle will evolve. This because in ranked matches a player has to battle - in most cases - with plenty of variety in terms of opponents approaches. Instead in a tournament one can find nemeses even if the difference in rating is substantial (over 150 rating points of difference)
1680535 
blue trying to score early. Being a bit not so decided in the action. Gaining little bits of space but also losing health of one unit. It is enough to convert though.
1680563 
The blue nearer to the central resource but then the red pushed better, although losing more health. The red converts.

stampid vs t0tproduction
Game 1 match ID: 1677018.
Game 2 match ID: 1678433. 
blue pushing, red scoring. The blue push is too strong, reds do not retreat in time.
1680361 
see above.
1680400 
red team scoring, blue team fighting and then scoring. Teams scattered around, the blue has initially the upper hand then it losts.
1680416 
red team scoring.Red team employing an harassing sg that loses too much health.
1680445 
blue team suicidal. Pushing is a fine art between push and retreat.
1680474 
the read team scattering for scoring lead to one unit less quickly and this let the blue team convert.

milkhunter vs tsensiert
tsensiert ghost were not picked, it is all one sided.

umrenato vs mumpsimus
1677016 
red team scoring and blue team badly handling 1vs1 aggressions to resource carriers.
1680334 
blue team scoring early but losing bots so the red team, that started in a slower mode, converts at the end. For few seconds it was like the blue had a chance.
1680360 
red team scoring but collecting too much damage. Not going to work.
1680398 
blue team better at fighting and the red team disregarding damage, practically one sided.
1680412 the mg of the blue team not retreating and holding the place is not going to thelp the blue team.
1680444 
see above.

Round 2

t0tproduction vs pier4r nvidia k1
1675921 
fight relatively equal for a while, then one side pick resources and the other becomes too aggressive.
1676584 
blue team scoring, red team first holding then pushing too much, suicidal. Don't push without firing support or without be compact.
1676655 
the red team loses ground and units when tries to push without support, or when it goes for resources.
1676742 
similar patter as above.
1676776 
red team scattered and mowed down while the blue scores.
1676801 
red team loses too many units.

umrenato vs teddy_88
1675919 
The fighting is equal for a while with one side flanking the other, but then one side is a bit too careless in pushing and loses a unit and then the match.
1676610 
both scoring and fighting equally until the blue team become careless with health damage.
1676658 
blue team fighting, red team tries to score. Red team getting too much damage (better retreat is needed).
1676744 
red team tries to score but it is too aggressive and goes down a unit early in the game.
1676763 
blue team scoring and pushing too aggressively, red team not properly retreating.
1676796 
red team tries to score, blue team aggressive, red team not retreating properly.
1676833 
The red team goes for scoring but loses units. The blue team pushes but not too hard. Though at the end it is enough to collect resources without problems.
1676883 
same as above.

savagex89 vs tsensiert
will be all one sided (likely ais in ranked released in october 2018 are not picked,
though they are part of season 2)

yours_truly vs federico abrile
1675927 
one side attacks from out of range without pushing, not going to be effective.
1676616 
like above.
1676664 
like above.
1676747 
yours truly having problems with fighting. The ai starts the attack too early. Likely all the rest of the matches will be similar.

x50calheadshotx vs stampid
1675928 
one side focused on collecting, the other on fighting. The collecting side is not too careful and loses a unit, the fighting side shows also retreat weakness and then gets worn out.
1676619 
blue team scoring, red team fighting. But the blue team fighting is also good.
1676661 
red team scoring, the blue retreating too much or too late.
1676738 
blue team scoring, red team fighting. The blue team using the sg to harass the red team and keep it at bay.
1676782 
red team scoring while keeping the control of enough group with the harassing sg.
1676804 
red team going to score, its sg is too aggressive. Blue team gain grounds and resources.
1676842 
red team harassing the blue with the sg, but the sg goes lost.  Opposite side bases makes things harder and the blue team slowly overwhelms the red one.
1676878 
red team scoring with harassing sg extremely close to death. Somehow it managed to succeed.

chilio6 vs milkhunter
1675925 
the all assault hurts but controlling a bit more than half of a map is enough.
1676621 
red team scoring, blue team pushing, red team pushing back.
1676653 
blue team ensuring the ground advantage and that was enough to win.
1676734 
blue team holding more than half of the map while scoring.
1676754 
like above.
1676788 
like above.

mumpsimus vs thecommonpidgeon
1675922 
mumpsimus slowly pushes the opponent. Notice that the opponent loses ground when he has retreated a bot and doesn't push back properly (the bot keeps dancing losing time).
1676623 
blue team near to catch the central resource. Red team scoring some resources in the back and then successfully securing the central resource.
1676651 
the red team suffers too much damage while fighting almost equally and the blue converts.
1676730 
red team with a slightly better push, then scrambling for resources. The blue team pushed in a crucial moment (bases were on the opposite side of the resources) almost getting a grip of the red bases but then the red team hold to score the victory.
1676758 
again quite close but mumpsimus slight better push is enough to convert.
1676795 
very balanced fight for the central resources. The red team was slowly snatching them but the blue team had a surprise in the last second. To watch!

heartlessvoid vs gtresd
1676089 
not a bad game by void that didn't push in 3 vs 2 (difficult to detect). Gtresd having the ground advantage converts.
1675923 
the fighting was somewhat balanced until one sg bugged out losing time. Still somehow the side with the bugged sg confused the enemy team enough to convert. Well done.
1676076 
quite balanced fight but one side controlled more space without really losing organization. This while scoring.
1676628 
balanced fight for a while. The red team with ground advantage. The blue team with an undecided sg that loses time. Red team converts, blue team tries some sort of flanking but the red team holds.
1676645 
Red team holding the center while the blue team scores. Then the blue team tries to scatter itself for resources and loses units in the process.
1676662 
Fighting for the middle. The red team goes for side resources, but then it becomes too scattered and the blue team is solid.
1676699 
opposite side bases. Red team not decided where to go. The blue team slowly converts.

ctl vs +_+
1675926 
one side slowly pushes the other and then has enough time for collecting resources.
1676073 
one side wants to push the other but get distracted by a flanking sg and loses too much time chasing enemies.
1676082 
again one side pushing, gaining a lot of ground and eliminating enemies but not picking resources. Tip: if you have a bot advantage, send one bot to pick resources.
1676126 
red team scoring early. blue team pushing. blue team with good push and too focused on fighting although recovering in the end.
1676649 
again pushing without scoring is nice to see but it is not productive.
1676729 
opposite side bases. This should reward the blue team pushing. It really doesn't as the pushing team is not focused enough on resources and it gets lured away by the sg.
1676799 
opposite side bases. red team tries to score, blue team pushing. Blue team lured away but recovering. Last minute scoring for the blue team.
1676835 
red pushes, blue scores. Red was not able to obliterate the opponents quickly enough.
1676872 
Blue team scoring early, red team pushing the blues to death. Not enough time to score.
1676904 
same as above.
1676926 
The almost opposite side bases favoured the pushing team. After so many draws due to lack of time the match is adjudicated counting the draws.

kasv vs bockwurst
1675920 
one side gaining slowly space, securing the score advantage and then focusing on the fight. Then the other side is too reckless and loses a unit and get obliterated.
1676160 
bockwurst gaining space slowly but also being distracted on two fronts. The point of securing a +1 score advantage and then focusing on fighting helps.
1676222 
here one side loses units early, bockwurst strategy is even more effective against an opponent with less units.
1676318 
see above. Interesting at the end the mg was able to retreat for a while against 3 bots.
1676340 
once again early unit loss for the weaker side.
1676397 
The assault has paper armor against focused fire, don't expose it too much without allies around.
1676772 
blue team scoring early, red team crushing the blues but scoring too late.

Round 1

# collecting here the matchids of matches and annotations for
# other players to watch them or even stream them. Activity also in the gladiabots
# discord chat. http://chat.gladiabots.com/

gtresd vs stampid
1675483 
surprisingly stampid lasted quite long, then lost a bot and the match
1675521 
one side had a good start but then was too aggressive and lost bots.
1675552 
stampid not bad but again gtresd holds more than half of the map and then picks the resources.
1675593 
one side focused on resources earlier on, but then losing the advantage.
1675629 
really the difference in rating is not visible on the map. At the end gtresd prevails as the opponent loses units, but until a certain point the weaker side holds.
1675650 
gtresd goes down but then recovers thanks to better fighting performance.

savageX89 vs umrenato
1675480 
one sided
1675525 
one side too aggressive, losing bots
1675554 
see above.
1675591 
sides are exchanging victories. Quite interesting.
1675622 
2-2 so far. But one side takes the lead. Plenty of suicidal push.
1675648 
one side gets 2 points lead in the match.
1675675 
one side is more aggressive than the other, in a suicidal way. Don't push more than you can retreat (in case of need).
1675704 
somehow one side got more coordinated over time and won consistently.

milkhunter vs bockwurst
1675484 
highly tactical. Battle for the center. Bockwurst pushing a bit better. Milkhunter focusing on resources. Then bockwurst got split.
1675527 
complicated base positions here. Bockwurst always having some more space but the mg of milky shoots back. In a final push milky loses units but closes the gap.
1675556 
very high level match where micro differences determine the result. Balanced fight in the middle of the map, although Bockwurst sniper gets quite some damage. Risky. Opposite side bases do not help too.
1675600 
A map where the center is crucial. Bockwurst slowly pushing and then converting although in the last seconds.
1675630 
opposite side bases. Milky pushes although strugglinh, bockwurst ignores the resource carries and milky converts. Super balanced games.
1675653 
Once again map with mostly central resources. Fighting battle. Bockwurst gets the upper hand. Notice that with heavily damaged bots pushing is hard because it is risky. Notice how a proper mg retreat is crucial otherwise it is going to absorb too much damage.
16755689 
And again middle map fight. May sound repetitive but there is a whole lot of small fatal details in those battles. Each small space gained is crucial. Milkhunter getting some damage that inhibits the push so bockwurst has some seconds to score.
1675738 
Bockwurst having a better push but milky snatching resources early. Then milky did not manage a push properly, loses a unit and the game.
1675779 
Milky going for an early score. Bockwurst trying to go aggressive. Splitting milk but then being scattered on the map. Still every second counts until the last one.
1675802 
both fighting for the center. Bockwurst with a slight advantage. Nonetheless milky with a refined resource collection under fire snatches the needed resources and makes the score of the match closer.
1675836 
Milky! Like the last game. From 5-2 to 5-4. Each match can be the last.
1675851 
Very close fighting battle for the center. Milky pushing but losing health. Being pushed back. Bockwurst thanks to the counterattack gets a resources but again each second counts.
1675866 
Battle for the center. Milky snatches a resource under fire. One more and that's it. great comeback.
1675878 
Battle for the center. Milky again snatches one resource under fire but this leaves one bot too exposed and he goes a unit down. From there winning the game is difficult. Well done to both, and Bockwurst prevails. What a battle!

pier4r nvidia k1 vs +_+
1675486 
one sided
1675529 
close but one side focus on the resources the other on the enemy team.
1675559 
the fight is close. But one side focus on the resources and it is able to damage the enemy units enough.
1675602 
the stronger side on paper get pushed away but converts thanks to the fact that the other side doesn't care about resources.
1675633 
opposite side bases. One team is too focused on fighting. Get flanked, loses units.
1675655 
again the fighting is balanced, but one side picks resources.
1675681 
see above.

thecommonpidgeon vs yours_truly
1675479 
yours truly has a too conservative retreat
1675522 
one side got enough territorial advantage, then pushed for resources.
1675548 
like above. One side is too conservative.
1675583 
one side conservative and then even losing units? Not a way to win a game.
1675621 
quick resource collection wins.
1675647 
see above. No real push for the side not collecting resources, therefore no real threat.

clt vs t0tproduction
1675478 
balanced until one side lost a bot. Less bots, likely defeat comes.
1675535 
quite balanced and at the end an isolated 1vs1 decided the match.
1675566 
one side converted the small fighting advantage to victory.
1675607 
one side had a better push but then got split from a flanking resource carrier and lost. Lesson learned: focus your team in the proper direction.
1675643 
one side has a better push, and the accidental flanking from the opponent is not dangerous enough. 1vs1 the sg should be able to annoy the sniper.
1675669 
one side gets pushed and cornered but then lures away the sniper somehow. That was the chance to kill the sniper. Chance that was not used.
1675700 
the fight was close until one side lost a bot due to exceeding aggressiveness.
1675742 
close fight, one side gaining slowly terrain and having a better scoring approach.
1675781 
opposite side bases. Fighting is important. The sg of one side sneaks away but then has a poor 1vs1 handling vs a sniper. The side with the sniper winning on the sg is victorious.

chilio6 vs kasv
1675477 
one side was able to confuse the other in retargeting terms. Lesson learned: push a bit more.
1675537 
one side doesn't really care about retreating. Too aggressive.
1675572 
see above.
1675612 
same pattern as before. One side too aggressive or nto focused on resources.
1675637 
a victorious all assault approach that forgets to pick resources and gets too aggressive in the end.
1675659 
the all assault side holds, push, but doesn't score.
1675719 
While matches are being resolved chilio is changing the AI. Interesting how the result changes. But kasv is too aggressive. Retreat before it is too late! Or push keeping in mind that you may need to retreat.
1675757 
chilio fighting better at first, but then losing a unit and forgetting about resources.
1675787 
chilio still thinkering with the ai while the round proceeds. The tinkering produces a better fighting result but still no resources picked. Not necessarily the better fighting side wins if resources are picked too late.
1675819 
once again, one side fights better, the other gets the resources.
1675843 
see above.
1675861 
see above, but scoreless.
1675876 
One side destroys the other (notice how properly coordinated and not suicidal that side is) and then had time to score. 5-4 .
1675897 
Both side equal in fighting. one also scoring.


mumpsimus vs federico abrile
1675485 
not one sided as expected. Although mumpsimus holds well with 3 bots while the 4th is scoring.
1675539 
mumpsimus quickly focusing on resources
1675575 
retreating with a resources sometimes it is hurtful. But more or less same pattern of the previous games.
1675640 
one side goes for resources in a split way, then turns the table and split the opponent and then wins.
1675662 
plenty of resources right around the middle of the map. The weaker side holds but doesn't push enough. The stronger side slowly converts.
1675617 
like above.

teddy_88 vs tsensiert
1675476 
one sided
1675546 
like above.
won't report more matches of this match for obvious reasons.

x50calheadshotx vs heartlessvoid
1675482 
quite balanced but one side pushes always a bit more, the other is too conservative. Opposide side bases too.
1675550 
one side getting more than half of the map. Then gathering resources.
1675585 
Good fighting by heartless that gains slowly territorial advantage and then resources.
1675623 
fighting for central resources with opposite side bases. Void has a better push and converts.
1675642 
void holds the middle of the map without problems.
1675666 
see above. If one controls half of the map and then some, while scoring resources, the result is clear. In a 4 vs 3 fight one has to find way to push the side with 3 units.
1675697 
very close fighting battle. Void wins due to better pushing ability.
Retrieved from "https://wiki.gladiabots.com/index.php?title=User:Pier4r/tournaments&oldid=4703"