Building comparison
head to head
Everlasting SummervsHeavy Rain
Heavy Rain asks more than Everlasting Summer, and the gap is execution.
Everlasting Summer
Optimization · Light / Casual
A branching visual novel that tests little beyond exploring choice routes.
Heavy Rain
Execution · Light / Casual
Branching interactive thriller where QTE choices decide who survives the Origami Killer case.
Everlasting Summer leans Optimization (Light / Casual); Heavy Rain leans Execution (Light / Casual).
Everlasting SummerHeavy Rain
Axis by axis
Execution0 vs 3
Heavy Rain leans clearly harder on execution.
Everlasting Summer
Reading and clicking choices, nothing physical
Heavy Rain
QTE prompts under tension
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Everlasting Summer
No opponent - characters follow fixed branching scripts
Heavy Rain
No adaptive opposition
Variance2 vs 2
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Everlasting Summer
Route outcomes are hidden only until first playthroughs
Heavy Rain
First-run uncertainty about consequences
Optimization3 vs 3
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Everlasting Summer
Mapping choice branches to endings is trivially solvable
Heavy Rain
Branch knowledge fully solves outcomes
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.