Building comparison
head to head
Emily is Away <3vsGoat Simulator
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Emily is Away <3
Variance · Light / Casual
An interactive story testing nothing mechanical - it is about the feelings.
Goat Simulator
Variance · Light / Casual
Deliberately broken physics sandbox about a goat causing mayhem.
Emily is Away <3 leans Variance (Light / Casual); Goat Simulator leans Variance (Light / Casual).
Emily is Away <3Goat Simulator
Axis by axis
Execution0 vs 1
Goat Simulator leans a little harder on execution, though the gap is small.
Emily is Away <3
Typing flavour text that autocompletes
Goat Simulator
Janky physics resist precision on purpose
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
Goat Simulator
No opposition; pure sandbox
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
Goat Simulator
Ragdoll chaos is unpredictable but stakes-free
Optimization2 vs 1
Emily is Away <3 leans a little harder on optimization, though the gap is small.
Emily is Away <3
Branch map is small and quickly solvable
Goat Simulator
Score combos exist but barely matter
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.