Attributes Limiting Skills

The Question

A viewer (DejaVu6196) asked: "What are your thoughts on contradictions between attributes and skills? How can a player with 1 Intelligence reach 100 in Science? Should they be allowed to, or should the attribute cap the max skill they can reach?" They cited Fallout: New Vegas as an example — the same low-intelligence character who gets "dumb dialogue" can reach Speech 100 and logically talk Legate Lanius into retreating.

It's Not a Contradiction

Tim immediately pushes back on the word "contradiction." He doesn't see it as one. His core belief, in real life and in RPG design: you don't start off amazing, you become amazing. That's the whole point. Saying otherwise implies you have to be great now to become great later — something he fundamentally disagrees with.

He references his video on learning from failure: messing up is the best way to get better at something. When you're good at something, it doesn't teach you why or how you're good. But failing teaches you what not to do.

External vs. Personal Obstacles

Tim frames RPG design around the player overcoming obstacles. Some are external — villains, monsters, dungeon traps — things the game throws at you that you figure your way past through fighting, thinking, sneaking, or talking.

But there are also personal obstacles — physical, mental, and emotional limitations — and Tim finds these even more interesting. You're making a character who is seen as lesser and has to overcome that. A low-intelligence character reaching mastery in speech or science is exactly this kind of compelling personal struggle.

Dumb Characters and Narrative Opportunity

Tim sees this as a narrative design challenge he loves. In Fallout and The Outer Worlds, they wrote entirely different dialogue lines for low-intelligence characters. He frames it as a challenge to narrative designers: "Can you write a line that a dumb person would say that would convince a smart villain?"

He points to the trope where the not-brightest person in the room says something seemingly simple — "Why aren't we just doing this?" — and someone else reframes it as brilliant. It's funny, it's fun, it gives characters their own spin, and it adds replayability. "That just hits every lever I like to have in my RPGs."

If You Do Cap Skills

While Tim personally wouldn't cap skills based on attributes, he acknowledges it's a valid design choice — as long as you tell the player upfront that attributes factor into skill caps. It satisfies the "player choice leads to player consequence" principle.

However, he raises a practical concern: capping skills requires players to plan their endgame build at character creation, which could be 20, 40, or even 100 hours away. For many players, their first playthrough is their only playthrough. That's a heavy burden.

Escape Valves: Perks and Items

If a designer does implement attribute-based skill caps, Tim recommends adding ways to overcome them:

• A perk that removes the cap — this costs a perk slot, so the player trades another potential ability for this freedom
• A rare item that removes the limitation — for example, a cap/helmet that doesn't make you smarter but removes the skill ceiling. This costs an equipment slot, so you're giving up a "helmet of heat vision" or a "chapo of invisibility" to eliminate the level cap

Both approaches maintain meaningful trade-offs while letting the player overcome their character's personal limitations.

Summary

Tim wouldn't design a game with attribute-based skill caps. If he did, he'd provide ways to eliminate them — because the fundamental promise of an RPG is making a weak character who overcomes their own personal obstacles, then external obstacles, and becomes the hero of the game.

References

• Tim Cain. YouTube video. https://www.youtube.com/watch?v=R3uFOoyrlNs