Most nights do not fail because you picked a bad game.
They fail because you picked the wrong kind of friction.
A giant library makes that harder to notice. Everything starts to blur into genre, review score, and how long the campaign is supposed to be. But those are not the signals that usually kill the session.
Sometimes the problem is not difficulty. It is the shape of the effort.
01Friction is not one thing
Players talk about friction like it is automatically bad.
It is not.
Some friction is the reason you come back. Learning a stubborn combat rhythm can feel great. Slow deduction can feel rich. Risky stealth can turn a short session into a story you retell later.
The problem starts when a library treats all friction as the same category.
A game can be brilliant and still be the wrong pick if tonight you do not want heavy note-taking, repeated failed runs, tank controls, deck math, or one more hour of setup before the real fun begins.
The shelf gets smaller fast when you stop asking what is good and start asking what kind of effort still sounds satisfying.
02Good friction and wrong friction are both taste signals
The useful question is not whether you are in the mood for challenge in general.
The useful question is which kind of challenge still feels alive to you.
Maybe you like:
- pressure that creates stories, but not precision that punishes every slip
- repetition when it teaches you something, but not repetition that feels like chores
- dread when it builds atmosphere, but not control schemes that make you fight the game itself
- complex systems when they unfold clearly, but not homework before momentum starts
Those are not edge cases.
They are the real borders of taste.
03Your second character should remember your borders
This is where Snowbll's second-character idea becomes useful.
A recommendation layer should remember more than favorite genres and top-played titles. It should remember the forms of friction you keep accepting on purpose and the ones that quietly end your sessions.
If you reliably enjoy tense stealth but bounce off crafting chores, that matters. If you love learning hard systems but hate restart-heavy openings, that matters. If you want horror atmosphere but not another game that turns basic movement into the whole battle, that matters too.
Snowbll should help make those borders visible so the next suggestion feels narrower, more honest, and easier to reject if the reason is wrong.
04Reasons beat rankings when the library gets too big
Backlog-heavy players do not need every game reduced to one line on a master list.
They need a short list with reasons they can argue with.
"This fits because it gives you dread without a huge rules load." "This fits because the friction is about pattern learning, not resource grinding." "This is probably the wrong pick because tonight you do not want another hour of setup."
That kind of language respects the player better than pretending one score can travel across every mood.
05The final call stays with the player
Snowbll's job is not to declare winners.
The job is smaller and more useful: describe the shape of the ask, compare it against your taste, and make the reason legible.
Sometimes the system will still miss. That is fine.
A transparent mismatch can teach the next recommendation something. A generic ranking only tells you what the crowd liked.
Fit gets sharper when the player can say, "No, that is the wrong kind of friction for me tonight," and the system learns from it.
Humans decide. The best recommendation is the one that makes your own boundary easier to name.