Building comparison
head to head
Emily is Away <3vsHeavy Rain
Heavy Rain asks more than Emily is Away <3, and the gap is execution.
Emily is Away <3
Variance · Light / Casual
An interactive story testing nothing mechanical - it is about the feelings.
Heavy Rain
Execution · Light / Casual
Branching interactive thriller where QTE choices decide who survives the Origami Killer case.
Emily is Away <3 leans Variance (Light / Casual); Heavy Rain leans Execution (Light / Casual).
Emily is Away <3Heavy Rain
Axis by axis
Execution0 vs 3
Heavy Rain leans clearly harder on execution.
Emily is Away <3
Typing flavour text that autocompletes
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.
Emily is Away <3
Scripted characters with fixed branching responses
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.
Emily is Away <3
Outcomes hidden only on first playthrough
Heavy Rain
First-run uncertainty about consequences
Optimization2 vs 3
Heavy Rain leans a little harder on optimization, though the gap is small.
Emily is Away <3
Branch map is small and quickly 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.