Building comparison
head to head
SuikodenvsThe Count Lucanor
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Suikoden
Optimization · Pure Optimization
A recruitment RPG where building your 108-star army and optimizing rune strategies is the strategic spine.
The Count Lucanor
Optimization · Systems & Chaos
A pixel-art horror fairy tale where a boy explores a cursed castle to win a kobold's inheritance.
Suikoden leans Optimization (Pure Optimization); The Count Lucanor leans Optimization (Systems & Chaos).
SuikodenThe Count Lucanor
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.
Suikoden
Basic menu combat with minimal timing sensitivity
The Count Lucanor
Light stealth evasion needs only basic movement
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Suikoden
All enemies scripted; castle battles use fixed logic
The Count Lucanor
Castle monsters patrol fixed routes without adaptation
Variance3 vs 4
The Count Lucanor leans a little harder on variance, though the gap is small.
Suikoden
Random encounters and some rune drop RNG add minor chaos
The Count Lucanor
Unknown castle secrets and endings on a blind run
Optimization7 vs 6
Suikoden leans a little harder on optimization, though the gap is small.
Suikoden
108 Stars recruiting order and rune attachment optimization define efficient runs
The Count Lucanor
Candle placement, puzzles, and ending routes are solvable
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.