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
An action RPG that crowns you king and tests your treasury more than your sword.

Optimization · Pure Optimization
Engineering structurally sound brick builds under physical constraints.
Fable III leans Optimization (Pure Optimization); LEGO Bricktales leans Optimization (Pure Optimization).
Fable III leans a little harder on execution, though the gap is small.
Fable III
Simplified combat rarely punishes
LEGO Bricktales
Placing bricks needs care, not speed
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Fable III
Scripted enemies
LEGO Bricktales
No opponent in a diorama
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Fable III
Largely fixed world
LEGO Bricktales
Puzzles are fixed once seen
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Fable III
Treasury management and kingdom promises drive the endgame
LEGO Bricktales
Engineering stable builds within constraints is the test
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.