Building comparison
head to head
Coffee TalkvsLake
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Coffee Talk
Optimization · Light / Casual
A cosy late-night cafe story where listening to fantasy-world patrons is the experience.
Lake
Execution · Light / Casual
Cozy slice-of-life game about delivering mail in a 1980s lakeside town.
Coffee Talk leans Optimization (Light / Casual); Lake leans Execution (Light / Casual).
Coffee TalkLake
Axis by axis
Execution0 vs 1
Lake leans a little harder on execution, though the gap is small.
Coffee Talk
Brewing is a simple icon selection
Lake
Just driving a mail truck calmly
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Coffee Talk
Customer stories follow scripted beats
Lake
No opposition exists
Variance1 vs 1
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Coffee Talk
Occasional recipe choices affect endings but space is tiny
Lake
Story beats authored, nothing hidden that matters
Optimization2 vs 1
Coffee Talk leans a little harder on optimization, though the gap is small.
Coffee Talk
Learning correct drink combos for good ends is a minimal optimisation layer
Lake
Dialogue choices, no systems to solve
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.