Building comparison
head to head
Fights in Tight SpacesvsMini Metro
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Fights in Tight Spaces
Optimization · Pure Optimization
A deckbuilder where positioning enemies in tight grid spaces to chain card combos is the deeply optimizable core.
Mini Metro
Optimization · Pure Optimization
Minimalist transit puzzle; route topology under spawning pressure.
Fights in Tight Spaces leans Optimization (Pure Optimization); Mini Metro leans Optimization (Pure Optimization).
Fights in Tight SpacesMini Metro
Axis by axis
Execution2 vs 2
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Fights in Tight Spaces
Slight timing element in cinematic ability triggers but minimal
Mini Metro
light real-time line-drawing
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Fights in Tight Spaces
Enemy AI is scripted with readable patterns
Mini Metro
no adversary
Variance6 vs 5
Fights in Tight Spaces leans a little harder on variance, though the gap is small.
Fights in Tight Spaces
Card draw and enemy placement add meaningful randomness
Mini Metro
station spawn pattern
Optimization9 vs 9
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Fights in Tight Spaces
Positioning combos and card chaining reward deep tactical planning
Mini Metro
line topology and routing
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.