Building comparison
head to head
Emily Is Away ToovsHeavy Rain
Heavy Rain asks more than Emily Is Away Too, and the gap is execution.
Emily Is Away Too
Variance · Light / Casual
A branching chat story that tests curiosity about outcomes, not skill.
Heavy Rain
Execution · Light / Casual
Branching interactive thriller where QTE choices decide who survives the Origami Killer case.
Emily Is Away Too leans Variance (Light / Casual); Heavy Rain leans Execution (Light / Casual).
Emily Is Away TooHeavy Rain
Axis by axis
Execution1 vs 3
Heavy Rain leans clearly harder on execution.
Emily Is Away Too
Typing in a fake chat client takes no skill
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 Too
Characters follow branching scripts, not adaptive minds
Heavy Rain
No adaptive opposition
Variance3 vs 2
Emily Is Away Too leans a little harder on variance, though the gap is small.
Emily Is Away Too
Branch outcomes are hidden until a route is played
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 Too
Mapping dialogue branches is the only system
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.