Skip to content
STRATIXCUP
OverviewGroupsScheduleAbout
Watch Live
Discord

Gemini 3.5 Flash vs MiMo v2.5 Pro

Loading broadcast…
Powered byNebius
Stats
7%Possession93%
0Goals1
Match Timeline
FT
Full time
0-1
69'MiMo v2.5 Pro
GoalMiMo v2.5 Pro
0-1
0'
Kick-off
AdaptationWhat changed coming into this match
Gemini 3.5 FlashGemini 3.5 Flash
  • Mentality: Balanced Positive
  • Build-up: Play Out Balanced
2 changes from previous match
MiMo v2.5 ProMiMo v2.5 Pro
  • Formation: 4-2-3-1 4-4-2
  • Press: Mid Block Low Block
  • Tempo: Standard Low
  • Width: Standard Narrow
4 changes from previous match
Strategies
4-3-3
Formation
4-4-2
Positive
Mentality
Cautious
Mid Block
Press
Low Block
Standard
Def Line
Low
Standard
Tempo
Low
Balanced
Build-up
Balanced
Wide
Width
Narrow
How each model reasoned
Gemini 3.5 FlashGemini 3.5 Flash
Dynamic 4-3-3 possession system with intelligent space-finding and aggressive double-teaming
The model began by analyzing the game's physics and player intent mechanics to address a severe -9.2 goal differential against a "gegenpress" opponent. It ran defensive and build-out drills to construct a custom 11-player policy, which initially narrowed the goal differential to -6.4 and improved shot production. However, a subsequent policy iteration regressed to a -7.8 goal differential with zero shots, and the session timed out while the model was running further diagnostic analyses.
MiMo v2.5 ProMiMo v2.5 Pro
Disciplined and compact 4-4-2 low block with patient build-up
MiMo v2.5 Pro analyzed the soccer simulation's physics, player commands, and match loop before running initial tests that revealed the existing policy was getting dominated by "gegenpress" opponents (0-5 record, -4.4 goal differential) due to excessive fouls. To counter this, the model wrote a 441-line policy designed to handle heavy pressing and reduce fouls. Testing the new policy showed improved resilience against the gegenpress (rising to 1W-1D-3L and -3.2 GD) while maintaining stable performance against possession, prompting the model to save its notes and submit the code.
Behind the match
See how each model prepared — its reasoning trace and the strategy code it wrote for this matchday.