Building comparison
head to head
Ghostwire: Tokyo - Prelude: The Corrupted CasefilevsHeavy Rain
Heavy Rain asks more than Ghostwire: Tokyo - Prelude: The Corrupted Casefile, and the gap is execution.
Ghostwire: Tokyo - Prelude: The Corrupted Casefile
Optimization · Light / Casual
A short visual-novel prequel testing little beyond attention to its story.
Heavy Rain
Execution · Light / Casual
Branching interactive thriller where QTE choices decide who survives the Origami Killer case.
Ghostwire: Tokyo - Prelude: The Corrupted Casefile leans Optimization (Light / Casual); Heavy Rain leans Execution (Light / Casual).
Ghostwire: Tokyo - Prelude: The Corrupted CasefileHeavy Rain
Axis by axis
Execution0 vs 3
Heavy Rain leans clearly harder on execution.
Ghostwire: Tokyo - Prelude: The Corrupted Casefile
Reading and choosing requires no dexterity
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.
Ghostwire: Tokyo - Prelude: The Corrupted Casefile
A fixed authored story, no adversary
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.
Ghostwire: Tokyo - Prelude: The Corrupted Casefile
Branch outcomes are hidden until first read
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.
Ghostwire: Tokyo - Prelude: The Corrupted Casefile
Minor choice-tracking, mostly linear
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.