Here’s something I’ve seen way too many times, both when running games and admittedly when designing them…
Many systems, almost all the most popular systems, never realize they’re slowly training players to stop trying interesting things.
It doesn’t happen all at once. It’s subtle. It builds over time. A player throws out an idea, the table pauses, everyone flips through abilities, and the situation usually goes one of three ways.
Either someone says, “You don’t have that feat/talent/feature,” or someone says, “I don’t think you can do that.” Not because it doesn’t make sense in the fiction, but because there isn’t a clean mechanical hook for it.
Or the GM and table just wing it. A ruling is made on the fly, patch something together and say, “Yeah, you can do it this time.” Yep, in the moment, the game keeps moving, awsome. But now you’ve either accidentally created a new rule you have to remember, and balance, forever, or you’ve set the expectation that this was a one-off exception that may or may not be allowed again.
And that’s where things get weird.
Because now players don’t just have to think about what they can do; they also have to consider what the GM will allow this time. That uncertainty doesn’t encourage creativity; it makes players cautious. They start second-guessing ideas before they even say them out loud.
After a few of those moments, players adjust. They stop leading with ideas and start leading with what’s on their sheet.
That’s the shift. And once it happens, the game feels different.
A lot of that comes from what I’d call restriction-based design. You can do X, but only if you have Y. You want to disarm someone, there’s probably a feat for that. You want to trip them; there’s an ability somewhere that covers it. You want to do something weird, cinematic, or just slightly outside the lines… now everyone starts looking for permission in the rules instead of just playing it out.
And to be clear, this approach didn’t come out of nowhere. It solves real problems. It keeps things balanced, it keeps rulings consistent, and it makes it easier for tables that don’t want to negotiate every action. There’s a reason so many systems lean this way because it just works.
But it also comes with a cost that doesn’t show up on the character sheet.
Defining abilities isn’t the problem.
In fact, when you clearly define something, disarming, tripping, or a specific maneuver, you’re giving players a reliable way to do it. That’s good design. It creates clarity, consistency, and something players can build toward.
The issue shows up in everything outside those definitions.
What happens when a player tries something that isn’t cleanly covered?
If the answer is “no,” or “you don’t have the ability for that,” or even a hesitant “I don’t think that’s allowed,” then the system and the game master has effectively drawn a line in the sand.
And players adapt fast.
They stop exploring the edges. They stop pitching ideas that don’t map neatly to what’s written. Not because they can’t do those things, but because they don’t trust that the system—or the table—will support them when they try.
That’s where the restriction really creeps in. Not from what’s defined, but from how everything undefined is treated.
The alternative is not throwing out the structure and letting the whole thing descend into chaos. That’s not a system; that’s a free-for-all. And it breaks just as quickly for entirely different reasons. The sweet spot, at least in my experience, is giving the player permission to try anything within the framework of the system.
Instead of asking whether or not the player is allowed to do something, the system asks how difficult it is and what it’s going to cost them. It’s a shift in perspective from access to risk. The player doesn’t have to unlock the ability to do something; they have to decide whether or not they’re willing to pay the price when things get uncertain.
That’s the space where tension lives. That’s where players lean forward instead of leaning back.
In Rotted Capes, that idea shows up in a few different ways, but they all follow the same philosophy. If you want to attempt a maneuver you don’t know, nothing is stopping you. You can go for it. But it costs you a Plot Point, and now you’re on the hook for a Power Challenge or an Ability Challenge to pull it off. You can bring in a Skill Set if it applies, but you’re still pushing beyond your training. You’re taking a real shot, not executing a guaranteed option.
The same thing applies to Power Stunts. If the situation calls for something bigger, something messier, something that isn’t neatly written on your sheet, you can reach for it. The system doesn’t shut you down; it just makes you commit. You pay for it, you roll for it, and you accept that it might not work, but when does works, it feels earned. When it doesn’t, it still moves the story forward in a way that a safe, pre-defined action never would.
This approach alters the manner in which players play. Rather than reviewing their abilities for the “right” action, they now think in terms of what they actually want to accomplish in that scene. They take risks that they wouldn’t normally take. They try things that aren’t necessarily optimal, but are completely in character. This leads to more improvisation, more momentum, and quite honestly, more things that people remember after the session is over.
With restriction-heavy systems, players tend to default to safe choices. They play tight. They optimize. They treat their character sheet as if it’s a button panel, and every turn is about figuring out which button to push. There’s nothing wrong with that style of play, and it’s perfectly valid. However, it’s very different from playing in a system that allows for that extra push.
However, permission-based design is not an excuse to do nothing. If the costs do not matter, then the players will simply abuse the system. If the difficulty is not real, then there is no tension. And if the rulings are not consistent, the players will no longer trust the system, and we are back where we started, but now we are messy. The structure must still be there; we simply need to support risk, not eliminate it.
Ultimately, the debate is not about which system is good or bad but about how the mechanics affect the players, encouraging risk and creativity, not waiting for permission.
If your system teaches players to wait for permission, they will. And once they do, you’ve already lost a piece of what makes tabletop games special in the first place.
Give them permission to try.
Then make them earn it.