Building comparison
head to head
Siren: Blood CursevsStarbound
Neither is meaningfully harder - they pose close to the same test. The widest gap is optimization, and it is a single point.
Siren: Blood Curse
Optimization · Pure Optimization
A PS3 reimagining of Siren where American visitors evade undead villagers using sight-jacking stealth.
Starbound
Optimization · Pure Optimization
A 2D sandbox of procedurally generated planets driven by crafting progression.
Siren: Blood Curse leans Optimization (Pure Optimization); Starbound leans Optimization (Pure Optimization).
Siren: Blood CurseStarbound
Axis by axis
Execution3 vs 3
Same score on execution - which means the number cannot separate them. The difference is in what each one asks of you.
Siren: Blood Curse
Stealth and occasional melee need only moderate precision
Starbound
Light platforming and combat, generous margins
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Siren: Blood Curse
Shibito behaviour is scripted patrol logic, not adaptation
Starbound
Procedural NPCs follow simple fixed behaviours
Variance4 vs 4
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Siren: Blood Curse
Hidden patrol routes and triggers until sightjacked and learned
Starbound
Procedural planets and loot keep early exploration unknown
Optimization8 vs 7
Siren: Blood Curse leans a little harder on optimization, though the gap is small.
Siren: Blood Curse
Episodic missions reduce to learnable route-and-timing puzzles
Starbound
Gear tiers, farming, and progression routes dominate
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.