Building comparison
head to head
MorphbladevsPersona 5
Neither is meaningfully harder - they pose close to the same test. The widest gap is variance, and it is a single point.
Morphblade
Optimization · Pure Optimization
A turn-based tactics puzzle about chaining weapon transforms against bug waves.
Persona 5
Optimization · Pure Optimization
Stylish JRPG where phantom thieves steal hearts on a tightly optimized school calendar.
Morphblade leans Optimization (Pure Optimization); Persona 5 leans Optimization (Pure Optimization).
MorphbladePersona 5
Axis by axis
Execution1 vs 1
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Morphblade
Turn-based movement removes any twitch demand
Persona 5
Stylish menus, not reflexes
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Morphblade
Bugs follow scripted behaviour, not modelling you
Persona 5
Palace enemies use fixed weaknesses
Variance4 vs 3
Morphblade leans a little harder on variance, though the gap is small.
Morphblade
Enemy spawn waves have randomised composition
Persona 5
Fusion alerts and negotiation rolls
Optimization9 vs 8
Morphblade leans a little harder on optimization, though the gap is small.
Morphblade
Planning movement to chain weapon transforms optimally is the puzzle
Persona 5
Confidant calendar routing and baton-pass weakness chains
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.