Building comparison
head to head
DREDGEvsWe Went Back
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
DREDGE
Optimization · Systems & Chaos
A cosy-eldritch fishing game about hauling secrets from dark water.
We Went Back
Optimization · Systems & Chaos
A short time-loop horror testing observation and deduction across repeating corridors.
DREDGE leans Optimization (Systems & Chaos); We Went Back leans Optimization (Systems & Chaos).
DREDGEWe Went Back
Axis by axis
Execution2 vs 1
DREDGE leans a little harder on execution, though the gap is small.
DREDGE
Fishing minigames and night dodging, light demands
We Went Back
Walking a looping station needs no dexterity
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
DREDGE
Horrors follow fixed rules
We Went Back
Scares trigger on script, never adapting
Variance4 vs 4
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
DREDGE
Fish spawns and fog-of-dread unknowns until mapped
We Went Back
Loop changes are unknown until observed once
Optimization6 vs 6
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
DREDGE
Cargo tetris, routes, and upgrades reward planning
We Went Back
Noticing loop differences and deducing the exit is the game
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.