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

Optimization · Pure Optimization
Managing a coin economy against escalating scripted raids with deliberately unexplained rules.

Optimization · Systems & Chaos
A card-stacking village-builder roguelite where efficient resource chain optimisation against draw randomness is the test.
Kingdom: Classic leans Optimization (Pure Optimization); Stacklands leans Optimization (Systems & Chaos).
Kingdom: Classic leans a little harder on execution, though the gap is small.
Kingdom: Classic
Riding left and right and dropping coins demands no twitch skill
Stacklands
Card dragging in real time has minimal precision demands
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Kingdom: Classic
Greed waves follow scripted escalation, never adapt to you
Stacklands
Enemies and events are scripted; no adaptive adversary
Stacklands leans a little harder on variance, though the gap is small.
Kingdom: Classic
Unexplained mechanics and map layout are hidden until mapped
Stacklands
Card pack draws control which resource chains become available
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Kingdom: Classic
Coin economy and wall timing are the solvable core
Stacklands
Resource chain optimisation and stacking sequences form the deep game
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.