The “tiny” CRPG peeves I can’t unsee anymore

The little CRPG annoyances that aren’t actually little

Across a couple of decades of playing CRPGs, the stuff that really sticks in my brain isn’t the big, headline-grabbing failures. Broken quests get patched. Janky animations fade into the background. What actually changes how I play – and sometimes whether I replay at all – are the “tiny” design decisions you’re supposed to just live with.

I’m talking about the boring menu choices and mechanical quirks: save file screens that turn into archaeological digs, stealth systems that make you feel like you’re piloting a forklift through a porcelain shop, main-character death rules that hard-erase interesting tactics, character options that are either obvious traps or so powerful they invalidate everything else.

On their own, none of these are dealbreakers. But stacking them across a 60-100 hour game? That’s how you end up with what I’d call real CRPG peeves – small, recurring design decisions that quietly corral you into specific playstyles. And once you notice the patterns, they’re very hard to unsee.

Save file chaos: UX that punishes people who actually play your game

Let’s start with something aggressively unsexy: save systems.

I keep an actual offline archive of CRPG saves. Partly because I cover games, partly because I like jumping back into specific builds or story branches years later. For a long CRPG, that usually means hundreds of saves per run. Add multiple characters and you’re staring down four-digit numbers.

Now drop that into a game that just gives you one endless vertical list of saves, with no per-character separation, no meaningful filters, and timestamps as your only real anchor. It’s not just mildly annoying – it actively discourages experimentation. You start saving less. You stop branching your playthrough. You think twice before trying a weird build because you know that if you want to resurrect that experiment later, you’ll have to scroll through an ancient tomb of “QuickSave 87” and “AutoSave 42”.

The irony is that CRPGs, more than almost any genre, benefit from frequent, granular saving. They’re about trying things – different dialogue approaches, combat tactics, builds, quest outcomes. But then the UX turns basic save management into suffering.

Some modern titles have finally gotten the memo and separate saves by character or campaign. Others at least give you naming tools and sorting that don’t feel like a 2004 mod tool. But far too many still treat save management like an afterthought, when it’s core to how this genre is actually played by people who care about it.

This is the theme that’s going to keep coming back: “small” systems are not small when your game is measured in dozens of hours and multiple runs.

CRPG stealth: two different flavors of bad

Stealth in CRPGs tends to fall into one of two categories, and both are their own special kind of pain:

• Games with no real stealth system that suddenly demand a stealth mission
• Games with actual stealth mechanics that collapse the moment a party is involved

The first one is almost comical. You get something like Warhammer 40,000: Rogue Trader asking you to complete a stealthy segment in a game where stealth is barely even a systemic concept. You’re basically playing “don’t walk into the red cone” with tools that were never designed for it. It’s not tension; it’s choreography, and the slightest misstep means you reload and go through the exact same dance again.

The second flavor is more subtle, and more common: there is a stealth system, and maybe even a character who’s actually built for it… but you’re commanding a full party in an isometric space. Now you’re wrestling a camera and an AI leash while trying to sneak exactly one shadowy rogue through a level full of detection checks that often seem to be firing on the whole party anyway.

You see attempts to solve this. Pillars of Eternity II does reasonably well with individual scouting – you can send one character ahead and get some actual value out of it. Larian’s games go further: the way Divinity: Original Sin 2 and Baldur’s Gate 3 handle splitting parties, verticality, and individual positioning makes stealth feel like a tool rather than a liability. You can scout, pickpocket, set up ambushes, and then rejoin without feeling like you’re waging war on the UI.

But in too many CRPGs, “we have stealth” really means “we have a stat called Stealth that you will use exactly three times before deciding it’s not worth the micromanagement tax.” That’s not real choice. That’s a trap option wearing a trench coat.

Main character death = party wipe is lazy design

If there’s one design decision I wish would just die, it’s this: your main character drops to zero HP, and the game immediately slaps you with a hard game over, even though your cleric could clearly just res them like any other companion.

From a story perspective, I sort of get it. The protagonist is “you.” Losing “you” is meant to be failure. But in practice, in party-based CRPGs with resurrection, what this does is warp the entire tactical layer around baby-proofing one specific body on the field.

If I know that the wizard in the back getting crit is annoying but fixable, while my PC getting crit is an instant reload, guess who I’m building like a paranoid tank? Suddenly I’m making suboptimal or boring decisions in character creation because I know the game has a special, arbitrary rule for this one character’s mortality.

That cascades into:

• More defensive stats and “boring but safe” feats on the main
• More bodyguards and buffs funnelled toward them
• Less willingness to try risky melee builds for fear of random crits

Throw in games where enemies can alpha-strike you before you meaningfully act, and now your entire encounter pacing is held hostage by one bad roll aimed at exactly the wrong health bar.

Party wipes when the whole party goes down? Fair. Permanent death in an Ironman or hardcore mode? Also fair. But in a system where necromancy, resurrection, or post-combat stabilizing are already baked in, main-character-unique death rules feel less like drama and more like a vestigial design habit that nobody had the courage to cut.

Party wipes when the whole party goes down? Fair. Permanent death in an Ironman or hardcore mode? Also fair. But in a system where necromancy, resurrection, or post-combat stabilizing are already baked in, main-character-unique death rules feel less like drama and more like a vestigial design habit that nobody had the courage to cut.

Trap options and underused builds: false promises in character creation

Character creation is the candy shop moment of any CRPG. Classes, archetypes, backgrounds, skills – it’s the page where the game promises you, “All of this matters. Pick your fantasy.” And sometimes that’s true. Other times, the game is lying to you through omission.

One obvious version is the pure “trap build.” Pathfinder: Wrath of the Righteous inherited a lot of archetypes from Kingmaker. Some of them were balanced around fighting specific creature types. Fine in theory. But when you drag a “Defender of the True World” druid – stacked with bonuses against fey – into a game whose entire premise is “You are waging war against demons,” that’s not a quirky niche; that’s a fundamentally mismatched design.

Owlcat has patched some of the worst offenders. Assassin went from laughably useless to actually relevant once they changed how poison interacts with demon immunities. But the fact it shipped like that at all tells you something: the character option grid is bigger than the design team’s ability (or time) to ensure each path has meaningful expression in the actual game.

It’s not always raw power. Sometimes it’s just visibility. Pillars of Eternity II lets you pick a cultural background, and if you pick Deadfire Archipelago – the region the game is actually set in – suddenly you’re tripping over unique dialogue hooks. Other backgrounds? Far, far less so. If you’re only ever going to play once, the “correct” choice is obvious if you care about reactivity. Everything else is technically supported, but they’re diet options.

This is the kind of thing that only really reveals itself after hours of play or multiple runs. By then, it’s too late. You either restart or just swallow the knowledge that a good chunk of the cool-looking stuff in the character creator is, functionally, decorative.

And again, this all pushes you in a direction: toward the safest, most obviously reactive or broadly useful choices. Not because you’re obsessed with min-maxing, but because the game is quietly rewarding you for guessing what the designers actually supported, rather than what they pretended to support.

Overweighted stats and the tyranny of action economy

If underused options are one half of the problem, the other half is the stuff that’s so obviously strong it stops feeling like a choice at all. And in CRPGs, that usually orbit around two things:

• Stats that snowball progression (extra XP, extra skill points)
• Anything that explodes your side of the action economy

This isn’t a new issue. Older CRPGs routinely made Intelligence or its equivalent the “god stat.” More skill points, faster levelling, often better dialogue checks – you were basically roleplaying an idiot if you didn’t pump it. Pair that with whatever attribute granted more attacks or turn actions, and you’ve just drawn a big neon arrow that says, “Build this or enjoy the poverty line of effectiveness.”

Modern games still trip over this. Take Wasteland 3: Intelligence once again pulls more than its fair share of weight by boosting skill points and critical damage. If you care even slightly about combat efficiency or build flexibility, you’re going to feel silly not favoring it heavily.

Then there’s action economy – how many actions, bodies, or turns you can bring to bear. This is where you see some truly wild imbalance. Divinity: Original Sin 2 is the perfect example. The summoning skill tree is just flat-out overweighted. Give nearly any character the ability to drop a durable summon on the field and you’ve effectively increased your party size and flooded the fight with distractions that burn enemy turns.

Once you understand that, it’s almost irrational not to build around summoning. Two summoners on your team turns every engagement into a manageable slog of meat shields and opportunistic strikes. Even years after release, when I go back, I still catch myself defaulting to that pattern because the game so clearly rewards it over more fragile, direct-damage builds.

Single-player games don’t need perfect balance, and I genuinely don’t want them to standardize every edge off. But when a handful of stats or mechanics so clearly dominate that anything else feels like self-imposed hard mode, that’s not “interesting asymmetry”; it’s warped incentives.

And just like the main-character death rule, this bleeds down into everything else. If Intelligence is king, you design encounters and checks around the assumption that players will have decent Intelligence. If summoning trivializes one-on-many fights, you either let the game be easy for those who discover it or start cranking enemy HP and damage in a way that punishes anyone who didn’t read the meta first.

Why these “petty” CRPG peeves actually matter

None of this sounds dramatic on paper. We’re not talking about catastrophic bugs or missing endings. We’re talking about:

• Mediocre save file UX
• Awkward stealth implementations
• Harsh main-character death rules in party games
• Trap archetypes and under-served backgrounds
• Overcentralized stats and overpowered mechanics like summoning

But if you care about CRPGs as more than just content to chew through once and forget, these are exactly the things that shape your long-term relationship with the genre.

They dictate what builds you feel comfortable trying. They decide whether you reload after a “death” you know is just a bad rule firing. They quietly narrow the space of viable roleplay and tactical expression. They turn some characters into permanent benchwarmers because the systems don’t give them appropriate stages to shine.

And they compound. A slightly clumsy stealth system might be tolerable. A slightly over-tuned summoning school might be tolerable. A slightly annoying save UI might be tolerable. Stack all of them in the same game, then stretch that over 80 hours, and suddenly you’re not being “picky” for noticing; you’re just awake.

The hopeful side is that some studios are clearly paying attention. You see newer games experiment with better save filtering, more party-aware stealth, and more honest tooltips about what a stat or archetype is actually good for. You see patches that nerf the most outrageous action economy exploits or buff ignored options instead of letting them rot.

But as long as CRPGs lean on sprawling systems and long runtimes – which they should, that’s why they’re good – these “peeves” will never actually be minor. They’re the friction points you feel on hour 3, hour 30, and hour 130. They’re the difference between a game you love enough to replay and one you finish once, file under “pretty good,” and never touch again.

So no, I don’t think it’s nitpicking to call this stuff out. I think it’s the only way we stop pretending they’re just quirks and start treating them as what they really are: core design choices that deserve as much attention as the big cinematic story beats everyone puts in the trailers.