head to head
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.

Optimization · Pure Optimization
Lane defense classic about managing a sun economy against shambling waves.

Optimization · Pure Optimization
Engineering a beaver colony's water and food systems to survive scheduled drought cycles at growing scale.
Plants vs. Zombies leans Optimization (Pure Optimization); Timberborn leans Optimization (Pure Optimization).
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Plants vs. Zombies
Clicking to plant, minimal pressure
Timberborn
Construction and management require no physical precision
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Plants vs. Zombies
Zombie waves follow set compositions
Timberborn
No adversary exists; droughts are scheduled, not adaptive
Timberborn leans a little harder on variance, though the gap is small.
Plants vs. Zombies
Wave timing and lane pressure vary mildly
Timberborn
Map seed and drought timing carry moderate session-level randomness
Timberborn leans a little harder on optimization, though the gap is small.
Plants vs. Zombies
Sun economy and lane setups are near-solvable
Timberborn
Water management, district planning, and beaver worker routing are the engineered core
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.