D&D General What is "mechanical complexity" doing?

I understand what you mean. But it's not complexity as it's defined in the realm of design. That's where the term depth is used (in some fields of design). Complexity leads, amongst other things, to something being hard to understand, and that's almost never a good thing. Now, again semantics, some will say "No but I enjoy bashing my head against a hard puzzle to solve it, or I enjoy having a complex system to toy with and try and find an outcome". And that's where the separation is very important. The fun part is solving the puzzle, not understanding what the puzzle is. It's inevitable, every user will have a moment where they analyze what's in front of them. But a puzzle fails almost systematically if the user doesn't understand it well. Same thing with the complex system, you enjoy toying with the parts once you have understood them, understanding them is rarely the goal or the pleasant part.

And the reason why I'm drawing pretty sharp lines is that people will often confine talks about design by limiting it to game design. But design as a whole is a discipline, and designing a shoes, designing a car, designing an onboarding process for a business, designing a game; they're all not that different and just have some subtleties and other disciplines that come and mix with design.

So concepts like complexity being undesirable is a very well known and established principle in design, and has been for decades.

Now, I'm not saying there aren't some thought experiments, or indie games or niche exploration that are not turning the concept on its head. You might have a game that's so ludicrously complex that it becomes funny, or you have some puzzle games that are so obstuse in their complexity, and yet have a very simple solution once you do, and the contrast between the two can be really funny afterwards.

But if you sit at a table with other designers. And one of them says "Well the game is very fun, and I think we have an appropriate amount of depth for what our users want. But I think it should be more complex", you have a problem.

I don't want to agree to your jargon carte blanche here, but for the sake of this post let's let that pass.

I still fundamentally disagree that the complexity you speak of is generally undesirable. Learning to understand what the puzzle is can be the most fun part of the puzzle. The puzzle does not fail systematically because the user doesn't understand it. In fact, I would go as far as saying that a DM giving players a puzzle they don't understand can be one of the most important hallmarks of a TTRPG. Sometimes that puzzle is a literal puzzle in a dungeon. Sometimes that puzzle is an emergent narrative that no one at the table understands when the game starts. Sometimes that puzzle is part of the gameplay between players as they learn to interact with each other, and as they make choices leveling up. Sometimes that puzzle is figuring out character builds or strategic combat. And all of those complexities can be part of the mechanics of the RPG itself.

I can give examples if needed, but suffice to say I do not write these "sometimes" off as thought experiments or niche games. Going back to the OP, I believe Mearls' 20% figure was an off the cuff estimate rather than a hard value, but is much closer to accurate level of desirability than your assertion that players with who enjoy complexity can be handwaved away as outliers.
 

log in or register to remove this ad

You can't have depth and no depth at the same time. There is no way to do "complexity for the players who want it." That isn't a design task, that's a broken design goal.

You can, somewhat, but it must be siloed - typically by class in D&D.
 

So, here's an interesting bit. From my perspective, you're sliding around what is meant by "complexity".

In my professional life, we use two different terms: We can refer to something as complicated, or complex, or both, or neither.
It's all semantics. If we were having a debate, I'd be fine with agreeing on these terms so we could talk about it. I've heard that distinction in other contexts and I don't disagree with it. We're using different words for different things. For example, I know complexity means something a bit different in terms of system complexity when it comes to programming.

Then, the question actually becomes - where are we making our games complicated, and to what end do we do so?
Exactly. The question I ask myself (and see other designers around me ask themselves) the most through iteration is "Is this worth the complexity (or complications in your case?) that I'm introducing?".
 

Since this whole thing is about d&d and I folks are tying themselves in knots to discuss complex complicated depth and so on with real world example I figured that I would Igive a d&d example.

Take 3.5's flat resist #/element and flat Dr #/exception vrs 5e's 50% resistance for both. The 3.5 pair both have totally different mechanics with resistance subtracting the number from each instance damage of that type (or fire acid cold etc) while dr subtracted from each instance not of the indicated type or source meeting the condition (ie fire silver a good aligned wilder etc). In 5e they replaced both of them with resistance=half damage of that type.

Ignoring the fact that division is generally considered more work and more difficult than subtraction there is the fact that the two mechanics served different purposes with dr mostly using small numbers targeting weapon users who tended to make many attacks each round and resistance mostly∆ using larger numbers targeting spellcasters who made few attacks (usually just 1) per round with a large number. The new system is absolutely easier to remember, but the result is too crude to fill either need and even runs counter to the original purpose by creating a few problems. The gm no longer has the mechanical hooks to target the pallylock or that one oopsie+5holy avenger that felt like a good idea at the time differently from Bob's kid playing a barbarian to that sounded cool while associated mechanics like SR:yes/no that pushed spell selection away from save or die type stuff towards spells that made everyone else in the party shine like a star. Sure it's "elegant" in it's simplicity, but it serves no one and adds nothing that a bunch more hit points wouldn't.



∆most weapon users made many attacks and could benefit from not being an all or nothing attack but others like rogue's and certain charges builds embraced the all or nothing risk in order to make an attack that gave the 🖕to DR with a much larger but singular attack.
 

Complexity is not neutral. Complexity is undesirable. A design being more complex than it needs to be is rarely a good thing.

In game design, what people refer to when they use the word complexity for something desirable is depth. Everyone loves design that have depth. Because depth doesn't mean complexity. Some very simple games have a lot of depth, but very little complexity. Some games can be very complex, but have very little depth.

Complexity is one of the parameters that designers have to handle, and it relates to the cognitive capacity of your users. Every time to add complexity, you chip away at the cognitive capacity of your users and when you reach it, they'll either disengage, engage partially or engage fully but risk leaving the experience feeling negatively about it.
Whether you or I like complexity is irrelevant to the fact that there are some people who do like complexity just for the sake of complexity. The massive skill tree and gem setups of Path of Exile is a draw for some gamers and it's not always just about strategic depth.
 



Several other game sub-cultures don't need a rule for everything - indeed, most of narrative gaming doesn't need a rule for everything, either. The OSR doesn't own this and didn't invent it.
It is unnecessary to invent something I did not say and then argue as if I supported your invention. I said something which is true and I didn't add anything more to it.
 

It is unnecessary to invent something I did not say and then argue as if I supported your invention. I said something which is true and I didn't add anything more to it.

Yes, but your truth wasn't actually sufficient to the discussion at hand. That left me needing to point out why, and what truths we should really be looking for.
 


Remove ads

Top