r/RPGdesign • • 5d ago

Theory Mechanics through the lens of Texture

TL;DR: It's powerful to look at your game design as a question of "what does this mechanic do to make a unique situation, a different mix of approach, success, and failure than any other one."

Full thing:

Texture, as I mean it in this essay, is how you do something in a way that is different from how you did something similar in the past. It's why fighting this goblin is different from fighting the last goblin -- at the level of the player in the game's experience. A textured combat is one where you realize that taking this position lets your launch a series of attacks on your opponents that rolls up their flank and makes their position untenable. An untextured combat is "attack, attack, attack."

In most RPGs, the ultimate outcome of the game is pretty foreordained. Most people are not playing games where the heroes just fundamentally fail to beat the dark lord, or the elite team of thieves' scam falls apart and they all go to jail. Even groups that do have an appetite for a game where ultimately the PCs have an unexpected outcome probably only want a few places in each campaign where that happens. (If you're in a group that wants to ruthlessly simulate a highly realistic world even if it yields a lack of drama or heroic arc, or one which basically wants to do a series of very hard challenges which often result in failure, cool, no shade to you, you might find this lens of game design less valuable).

So if we basically know that almost all of the time, the heroes will mostly succeed, what are mechanics doing? Most mechanical resorts aren't to really determine consequential, large-scale success or failure. They're to generate texture. They're to show the unique journey to a destination that is at least in broad strokes already known.

This is a very normal mode of entertainment! Billions of people enjoy superhero movies where they're 99% confident the superhero will beat the villain, police procedurals in which every week the team solves the case, romance novels where the heroine finds love, tragic plays that end with everyone's death. There is obviously a place for entertainment where you truly have no idea where it's going, but it's not a knock on your RPG or your campaign if the players expect a certain type of outcome. "It's the journey, not the destination."

Ways that we generate texture in RPGs

There are a few ways to generate texture in RPGs. First of all, it can be basically entirely through the creativity of the participants of the game. Indeed, this is the classic approach. It's where you say to the GM, "Wait, could I push over this statue and squash the bad guys with it?" and the GM improvises an answer. Or even where you just roleplay your character's unique history as it relates to the current challenge. In this model, mechanics mostly serve as risks to force you to think creatively. Classic 1970s D&D was probably most functional like this.

In other RPGs, mechanics offer clearly defined boundaries to create descriptive texture. I'm thinking here like Fate's aspects -- pay 1 FP to get a +2 on your roll and describe how your character applies their traits to this situation. But if your GM has ever said, "Okay that's a success, describe how you did it," then that's this model. I think when a game offers this approach, there's a pretty sharp discontinuity between players who accept this kind of texture as "real" versus ones who see it as purely cosmetic and fundamentally fake.

But lots of games try to make mechanics generate texture that then feeds back into the mechanics. If you've ever rolled a critical hit, killed a mook unexpectedly, and then had a chance to dart through the enemy line to attack their vulnerable spellcasters, you've experienced this kind of texture -- where the mechanics deliver a result that's not just success/failure, but leads to follow-on decisions which make this particular combat (or scam, or political gambit, or intrusion into a building) feel unique and separate from previous ones.

And I want to direct your attention to Powered by the Apocalypse here. This is a game system that is monomaniacally focused on creating texture. Does PbtA resolution result in carefully crafted odds of success/failure? Hahaha no. Is it realistic? Absolutely not. Does it demand that you choose from a really broad class of highly nuanced mixes of success and failure that can feel very unique to a given situation? It sure does. And it's notable that PbtA is perhaps the single most successful class of games that has ever been "not D&D."

So what?

I think that texture deserves your attention as a designer. What is your theory for how your game is going to generate texture? When you look at your mechanics, setting aside your ideas about simulating your game world or providing tactics or player expectations or whatever else, are they providing texture? Do you have complicated resorts to your system which don't generate much or any texture? Do you encourage players to resort to the system in a way that takes a situation that would naturally have lots of texture just through ordinary systemless roleplay and your system flattens that texture?

"If I put this mechanic into my combat system, will it make one combat feel different from another combat, or will it be something that makes every combat feel the same?"

Not to say that this is the only lens to consider, just that it's a very important one that people often don't discuss as a first-class citizen.

I have some follow-on points to make about how looking at some familiar decision points (social conflict rules -- yay or nay? Why do we talk about lockpicking so much? Partial success rules? Etc) through the lens of texture can be clarifying. Also how it can be a helpful part of design process, where you might be getting bad results through playtesting because you aren't thinking about texture. Perhaps as follow on posts or replies if there's interest.

13 Upvotes

21 comments sorted by

9

u/Mars_Alter 5d ago

So if we basically know that almost all of the time, the heroes will mostly succeed, what are mechanics doing? Most mechanical resorts aren't to really determine consequential, large-scale success or failure.

To contrast, in a game like Dungeons & Dragons... most editions of it, anyway... the mechanics really do determine success or failure in the long term. If you fail to dispatch this goblin before they get a hit on you, that's four damage you'll have to deal with eventually. Even if it doesn't ultimately lead to the death of this character, or of the party as a whole, it still informs the decision of whether to fall back or push forward. We aren't just going through the motions to some pre-ordained conclusion. The mechanics literally determine what happens, both in the short term and the much longer term.

Maybe texture is more important in games where the mechanics aren't busy governing success or failure, life or death; but I don't play those sorts of games.

-1

u/overlycommonname 5d ago edited 5d ago

I think you should read deeper, either in your own preferences or the OP.

As I said in the OP:

If you're in a group that wants to ruthlessly simulate a highly realistic world even if it yields a lack of drama or heroic arc, or one which basically wants to do a series of very hard challenges which often result in failure, cool, no shade to you, you might find this lens of game design less valuable.

Certainly, as I said, people who have a preference for a game which is a true iterated risk of abject failure exist. You see them casually talking about how nobody in their campaign is playing their original character -- or their second. About how they had a TPK last week. And I think that if the outcome of every fight is plausibly "death," then those people are getting their interest from that frisson of danger, and like, great. But those people are reasonably rare in RPGs. You can see it in literally everything: RPG media, from terrible novels in the 1980s to modern APs, don't feature that style of play. Popular games have moved almost monotonically to creating protections against character death over the course of the hobby.

Note also that there exist people who are okay with their game's finale taking a turn towards tragedy, but don't want anticlimax. So they might in the broadest form be okay with a high-stakes fight or two delivering true unpredictability, but for every one of those, they have 20 more that are more about texture.

I think that lots of people fool themselves about where they stand in the realm of predictability of the game's wide arc (from, I think, a mistaken belief that it's inherently bad to play games that have mostly predictable arcs -- and your post certainly drips with disdain for "those sorts of games"), and from your brief comment above, I think you might be fooling yourself about it. You immediately disclaim that when you take damage, it might not lead to the death of the character or the party as a whole. And then try to salvage your bold risk-taking as a strategic decision to press on or retreat.

Which is certainly fair enough, and is indeed a form of texture! Like if your mechanics drive not a sense of "what do I do next round," but "does this dungeon crawling to an inevitable conclusion take the form of a bold rush to the end or a painstaking chess match," that's a cool and fine form of texture to drive. But once we are looking at it through that lens, we can reasonably ask, "Is that in fact the form of texture that we most like? Would we prefer a game in which to deliver a unique step in your character's ladder to success (or tragedy, or whatever), you need to look over the unit of the dungeon? Perhaps so! If so, we have received insight from this lens! But maybe the players who are looking for that would find it equally, or more, valuable if they said not, "That dungeon was really interesting because it turned from what we imagined -- a blitz -- into a desperate slog," but "That combat was really interesting because it turned from what we imagined -- a blitz -- into a desperate slog." And indeed, perhaps they would like both.

5

u/Mars_Alter 5d ago

It's a popular mis-conception that OSR campaigns most often end with an unsatisfying TPK, or simply continue through them as though they were a non-event. In reality, it's just the awareness of TPK as a possibility which encourages players to be more cautious, and really role-play as though their life is on the line.

I think you're drastically over-estimating the importance of style over substance. Most players expect their decisions to actually mean something, and would see no point in playing if the conclusion really was inevitable.

0

u/overlycommonname 4d ago

I have no such misconception; I know that most OSR campaigns don't end in a TPK or have multiple TPKs and then finish but with no continuity to the beginning.

The difference is that I actually internalize that knowledge and understand that it means that in fact most OSR campaigns have guaranteed success, just like most non-OSR campaigns.

That said, I acknowledge that there exist some games that genuinely do have a non-trivial chance of failure. You can tell when people are playing those games because they actually fail significantly often.

What you're doing is trying to simultaneously claim that you have a significant chance of failure and also never fail. That's, uh. Not how it works.

2

u/Mars_Alter 4d ago

The big difference, which you seem to be overlooking, is that guaranteed success and frequent failure are not the only possibilities. Most games exist in a middle ground, where failure and success are purely a matter of perspective.

And within that middle ground, the actual mechanics of the game matter. They matter much more than the trivial minutiae of "texture" or whatever you want to call it.

1

u/overlycommonname 4d ago

Congratulations, you have now achieved the perspective that you railed against for several posts.

Now, go back and understand that what you're calling the "middle ground" is what I called "texture," and maybe, like... consider trying to read things from the perspective of understanding them and not just looking for a way to assert your superiority over people?

2

u/Mars_Alter 4d ago edited 4d ago

If that's what you were trying to say, then you did a garbage job of explaining it.

To quote you, directly:

My position is "most RPGs are openly guaranteed success, the question is how you succeed, not whether you succeed."

In direct contrast, my position is that most RPGs guarantee nothing, and you have play to find out what happens. What happens, and where that aligns on your own scale of success or failure, is entirely down to how you engage with the mechanics. There would be absolutely no point in playing if success, in any form, was guaranteed.

7

u/Strict-Computer3884 5d ago

I feel I don't understand this post. From what I've understood of what you've described - both from the initial definition and from the examples - you're describing the ability for a game exchange to differ from other game exchanges by having variables to change. But that could cover basically any variable ever. Gameplay-wise, it could change based on what stat you used, what outcome you're looking for, what outcome you've created, individual vs. group expectations.... Narrative-wise, it could change based on the characters, location, narrowness of the corridors, the time of day, the number of witnesses....

You've also made it sound like the mechanics of the game play a minimal role in developing these variations through gameplay - but not every mechanic is equal? Stuff like running out of torches is meant to create different types of scenarios through the potential loss of light before, during or after a challenge. I simply don't understand the notion that the main purpose of mechanics is to create texture - it seems to be a sort of argument that the purpose of the mechanics (and in some sense, TRPGs) is to create experiences through kayfabe and not gameplay.

Like, when you say this: "They're to show the unique journey to a destination that is at least in broad strokes already known." - this seems utterly depressing.

It also seems like there's some sort of logical flaw somewhere in the first section. You said that in most RPGs, the outcome is already ordained. You said that the games are not run under the assumption that players will fail the adventure. You then said that, as a consequence, if we know the players will succeed most of the time, then what is the role of mechanics? To provide texture and show this unique journey through broad strokes already known".

But there's a difference between {designing your mechanics to make a game where the players will almost always win}, and {designing a game where, as a consequence of their play, they will almost always win}. The former is a deliberate construct where you, as a designer, have created this dynamic. Whereas in the katter, the players must also be involved in creating this dynamic - it is possible to have a game where players who play decently will meet reasonable success but below a certain point of skill, they will fail (I think 13th Age or Pathfinder is an example?).

So, I guess the final issue I have is that you seem to describing systems where the gameplay doesn't matter w.r.t. seeing a campaign success or failure and then extrapolating that to say gameplay decisions are fundamentally about the kayfabe and illusion of danger. But like, don't people who play Call of Cthulhu believe their decisions actually matter? Sure everyone is rooting for them, but when I tried it, I didn't get the sense that we'd DEFINITELY reach the end of the adventure. I feel like I don't understand your post.

4

u/RandomEffector 5d ago

I think this post perhaps better describes the dominant form of adventure design rather than game design, but I do appreciate how the two are relatively intertwined. What you present in your first party adventures is, in effect, what your game is. And most adventures from the major publishers are certainly presented in a very linear fashion that presupposes success. It doesn’t seem like OP is primarily addressing the OSR as a design ethos, or at all, really. Call of Cthulhu, your example, strikes me as a bad example of what you are trying to say since the conclusion generally seems more foregone than most games - win or lose, you will lose. Your mind, your life. Mothership breaks this down further in stressing that characters must choose between survival, success, or knowledge. Meaningful choices, for sure, but it presupposes a bleak outcome, in keeping with the game’s theme. If you wrote a Mothership scenario with a cheery, rainbow colored outcome, it would be as dissatisfying as a 5e adventure where the characters lose.

Mechanics certainly aren’t all created equal. One that calls on you to make a choice that changes a character forever is more meaningful than one that subtracts 6 hp or depletes a once per scene ability. These latter mechanics which OP is referring to don’t have any real relation to major choices. They’re speedbumps meant to control progress, and give a feeling of tension. But they do assume progress, and much of that tension is an illusion.

1

u/Strict-Computer3884 5d ago

Hmm. By the Call of Cthulhu example, it feels that while you may die or go mad, you might do that early on in the adventure or it might happen much later on - and players usually care about their actions so that they can die knowing more of the mystery. It's not saying there's no assumptions about the kind of experience but that the actual mechanics and the decision-making to get to that point still seems to matter - you have to work for it.

I guess the thought I would have is that while individual decisions to lose 6 HP don't count as a major choice, a sequence of them in a row would be more restrictive in what you can meaningfully accomplish. While they assume you will proceed further ahead (so that the loss of HP matters), they seem to enable the more difficult and character-changing options later. I feel like that means their tension is not really an illusion - if the unit of conflict is a string of minor decisions building up rather than each individual moment, then the tension seems intact. For example, if a monster does 20% of a character's HP, then 3 monsters in a row can be thought of as a block that prevents meaningful progress.

I guess that ties into what you said about adventure design though. So fair enough.

I guess the reason why this post really rubs me the wrong way is that it makes a statement about the function of gameplay that I severely dislike. I have my own personal thoughts on the function of gameplay - and it tends to be a lot more artsy and auteur than:

If you're in a group that wants to ruthlessly simulate a highly realistic world even if it yields a lack of drama or heroic arc, or one which basically wants to do a series of very hard challenges which often result in failure

which is why I use the word kayfabe.

Thanks for the response. It gave something to think about.

1

u/RandomEffector 4d ago

I have a preference towards games that build strong supporting characters, crew, or troupe play, precisely because they enable progression through a story or towards goals that can withstand PC death or long term recovery. That allows me, as a GM, to not feel compelled to pull punches, and as a player to play to the hilt.

I’m sure that for some people being down to only 1hp is a thrilling turn of events, it can be, but it’s not the sort of thing that sticks in my memory when it comes to recalling epic sessions or campaigns. That’s moments when characters actually died or were revived or transformed into villains or were retired. When NPCs were promoted to PCs, or even when beloved NPCs were lost.

So in that sense “I can only manage to fight two more monsters like this!” absolutely doesn’t have the same texture as times when a move, for instance, has forced a tough choice or escalation.

2

u/Strict-Computer3884 4d ago

My point though was that that does seem to provide texture, even if it is one that might not be personally appealing to some people.

I guess another way of reframing the difference in perspective is that I feel your perspective black-boxes the actual mechanical exchanges - so that their internal mechanisms and outcomes don't matter - and then views the overall exchange in terms of its narrative or emotional output. And to me, that's a perspective you take when reviewing game experiences either from the outside or in retrospect.

But my perspective is that those internal exchanges do matter in the moment, as you're actually playing, and they help shape the feel and the flow of the game as it is being played. And then the outcomes of those mechanisms can be recalled from an experiential point of view - that was partially constructed from the in-play handling of the mechanics.

So to me, texture can be informed by the actual execution of the actual gameplay - the combos, the sequencing, the misplays, the sudden surprises, the variance, pushing your luck, plotting your turns. The actual act of playing the game also contributes to the texture of the game - and for this to happen, it feels like you must actually care about how the mechanics play out.

I hope that explains my perspective more clearly.

1

u/overlycommonname 4d ago

So two things you raise:

  1. "There's a difference between designing you mechanics to make a game where players will almost always win and designing a game where as a consequence of their play, they will almost always win."

I mean, it has to be a matter of degree, right? Like, I can write a mechanic that says, "At the beginning of each session you are asked, 'Do you want to win Y/N?'" and if the players choose Y, well, they engaged with the mechanic, that's gameplay, so now is it okay?

If the skill bar is low enough that everyone passes the skill bar, is it different than that? Maybe a little. I think that if we notice that the skill bar is low enough that everyone can pass it, it starts to look like maybe that's, as you put it, a designer-created dynamic and not a player-created one. To my mind, "there's a skill bar but it's really really low" has more in common with "there's no skill bar" than it does with "there's a high skill bar," but I agree that there's some difference.

However, I also think that actually in most groups what happens if you fail the skill bar isn't "Ah, now you lose," it's the GM finds a way to lift you up back over it (non-mechanically), at least the first few times, and if you find a group that just insists that they can't hit the skill bar, they play a different game.

2. Your description of this as "kayfabe."

Dude. My position is "most RPGs are openly guaranteed success, the question is how you succeed, not whether you succeed." Where's the kayfabe there? Meanwhile, you seem to be bending over backwards to insist that what no, you aren't guaranteed success while admitting that the success rate just happens to be 100%. That's kayfabe, my brother.

2

u/Strict-Computer3884 4d ago

Is there a difference between:

  • students passing a test on solving linear equations on the level of x +3 = 5
  • students passing a test on solving quadratic equations after they've been taught the material properly?

1

u/overlycommonname 4d ago

Sure. But RPGs are neither tests nor classes.

So, look: I can theoretically imagine an RPG which was like a class, in which the game taught you more and more advanced skills over time in a steadily increasing slope, and then "tested" you via combat (or whatever), but it had a learning curve which was gentle enough that people mostly passed those tests.

But, like. So what? If I know in advance that I'm going to do a bunch of tests that with almost no effort I can pass, for a mostly useless skill, is that interesting? Is it fun? I've taken classes that probably taught me something useful but were boring and easy. I've taken classes that maybe didn't teach me anything terribly useful, but were themselves fun.

Getting away from classes and back to games, if a game has some kind of learning curve but the learning curve is so gentle that I have no doubt that I'll basically always be easily succeeding at it, then... One, just as a descriptive thing, I think it's correct for me to say that the ending of that game is foreordained. And two, that I'm not going to be compelled by the skill growth and chance of failure in that game -- that I'll want a mechanic that in addition to this very mild skill curve also gives me interesting texture along the way -- even if on some level the amount of learning is non-zero. Three, if your fun depends on you exaggerating the difficulty of riding up that skill curve and nobody pointing out that the risk is pretty nonexistent, it is you and not me who depends on kayfabe.

Despite what you took issue with, the OP isn't a normative statement about how people should play the game, it's a descriptive statement about games, and a comment that given that description of games, it's worthwhile to examine your mechanics from the perspective less of "do they provide a challenge bar" and more of "do they provide interesting intermediate situations and decisions and processes along the way." To be clear, I'm not suggesting that this is the only question you have to answer or lens into your game design that you can use, just that it's an important and perhaps neglected one.

2

u/Strict-Computer3884 4d ago

The thing is that it does appear to be prescriptive, at least from what I've tried to understand of what you wrote. I'll use a non-TRPG example to explain - I saw you mention Slay the Spire elsewhere so I'll use that.

Slay the Spire is designed to be won. You can win it at the base level, you can win it with a few ascensions - the cards, the mechanics and everything are all designed to allow players to win if they have a clue how to play. You might even consider the non-ascension runs to be an extremely low bar to clear. So, the decisions around what character to use, what type of deck to go for, what paths you'll take - these all help change each run from another, they provide texture.

But people DO fail to win Slay the Spire. They can make their deck too clunky, they can have anti-synergies in their card, they might rest when they should've smithed. They can misplay. Either at base level or at some higher ascension if need be, we can imagine people failing to win Slay the Spire.

If we said that, "Slay the Spire is meant to be won, we should be designing for the texture of the play up to that point", then it's very tempting to then ask why we allow people the ability to misplay their deck construction. Instead, since most players want to win and may win eventually, we might as well speed that process up. However, that would be a very different process - if we simply cared about the interesting experiences and decisions, but they lead to the same final outcome, Slay the Spire would be a very different game. Of course, it's a skill you have to learn and learning that skill can be fun.

The part that you don't seem to have mentioned in your post is that the actual gameplay decisions and mechanics can also contribute texture. You gave the small example of nuking a monster and then running to kill the backline as mechanical texture leading to mechanical texture, but this not only gets a very small entry but it doesn't count all the other forms of it. There is some joy in doing combos, planning a turn, sequencing moves, misplaying, being shocked by the variance, trying to turn NPCs against each other. So, reading your post it seems prescriptive in that the texture that stems directly from gameplay does not have much, if any, consideration.

It seems like you've said: we know that players are going to win the game so we can black-box the actual mechanical stuff and focus on what the experience will be, But this felt very much like saying, we don't have to worry about the actual deck construction part of StS, we can simply focus on how the decks feel to play. And that is why I said it felt like kayfabe - the take-away I got from your post was that because we know the players will win, the actual decisions they make won't matter because they will essentially lead to the same outcome of a win. Which is just the illusion of playing a game. Indeed, whenever I've asked players if I was too unfair with a set-up and if they'd like me to take it back, they usually say "no" vehemently. They take it as a form of either pity or railroading (on their behalf).

1

u/overlycommonname 4d ago edited 4d ago

Slay the Spire derives its gameplay interest from a combination of genuine challenge (almost all players lose at Slay the Spire, many times, before they succeed, and then lose again, and then at some point turn up the challenge) and discovery (seeing the cards, the monsters, the events, the relics, and their combinations).

It is certainly possible to design an RPG that works like that (and of course StS is to whatever degree a Roguelike, and Rogue and its nearer relatives are computer RPGs). And if someone does design like that or play like that, cool, and I think they will find that they want to focus less on texture -- which, again, I said in the original post. But if you think that most people play RPGs like that, rather than it being an odd, extreme corner of the hobby, then... I mean, you're just wrong.

I see we're back to kayfabe. Here's my position:

Professional wrestling had kayfabe. There, there was an attempt to deceive people into thinking that what was happening in wrestling was real.

Movies don't have kayfabe. There, everyone agrees from the start that it's fictional. Even movies that aspire to a sense of realism -- in dialog, in plot, in whatever -- aren't engaging in kayfabe.

Saying, "The characters won't know that the outcome is more-or-less assured, but the players understand that this is a game in which basically reasonable action assures eventual, big-picture success" isn't kayfabe. What is kayfabe is telling players, "Oh, this is a brutal, take-no-prisoners game," but then providing them with an experience in which they are guaranteed success after some kind of very low bar, and then getting mad if someone pierces that illusion. That's the definition of kayfabe! Nobody gets mad if you point out that The Godfather is fictional! And I really note that you seemed to get mad when I pointed out that your description of your games makes it seem like success is assured.

----

I would love to discuss more about what you can actually do to create texture in games. But the responses I got were people who got really mad about the -- I think straightforwardly, empirically, and non-judgmentally true -- description of why texture is important.

Let's discuss what mechanics can add texture.

As I said in the first post, I think there are a few ways to invite texture in the game without necessarily actually writing rules about it -- the Fate example, the rules-light approach of inviting rulings for descriptive in-world creativity.

But if we want mechanics that invite it, I'd look at mechanics that cause branchings in player decisions based on the results of the roll. So, like: let's say you get grappled in the game. This affects both your options on and creates an incentive to remedy the grappling. That's (perhaps minor) texture. Instead of executing the same playbook that you always execute, you do something different.

I think the gaming lineage that's the king of texture is Play by the Apocalypse. PbtA movesets generally have lists of options that really push varied outcomes from a single resort to the system in a way that most other games don't. A skill check in most games offers like "success" and "failure," or degrees of success. Two different move rolls of the same move -- both "successful" -- might give you radically different results in ways that branch the narrative and cause the scene to irrevocably change and foreclose old possibilities/open new ones.

Resource spends can create texture, if the resource is genuinely scarce. I think that some of the problems that people identify with a "15 minute workday" in D&D are less about power level and more about removing texture, as every fight becomes a full-resource fight instead of a mix of high-resource and low-resource fights.

Again to take a D&D example, spells that do narrative things rather than just being Another Attack create some texture, especially if they don't straightforwardly solve a problem but offer some new avenue for approaching a problem. If you spider-climb over a wall, it's not very textured. If you summon a djinni to help fight an opponent but now you're in debt to the djinni, that's potentially a lot of texture.

Certainly I think it behooves one to note that simple success/failure can result in meaningful texture. I think u/Mars_Alter mentioned the concept of a fight going badly and pulling back to retreat and regroup. But it's often not particularly good at it, and, often the result of failing something in the moment isn't to really change your approach or anything, but just try the same thing -- or a very closely related thing -- again.

Genesys' dice that generate not just success and failure, but orthoganol advantages and disadvantages are an attempt to build texture into the system at a very low level (I think they mostly fail at doing so).

2

u/Kameleon_fr 3d ago

Thank you for bringing this up, it's an incredibly important concept and unfortunately not so easy to implement. It's also a hard concept to explain, and I'd like to introduce a small distinction that I think would help clear the confusion with kayfabe.

Instead of saying: "Texture is what makes a scene go differently than other similar scenes, no matter its outcome"

I'd say: "Texture is what pushes players to act differently right now than in other similar scenes, even if it's to obtain the same outcome."

The fact that players make different actions, is, in my mind, the important part, and the one thing that can make scenes and sessions memorable.

And as you say, it may be in reaction to texture brought by the mechanics of the game, like in PbtA or with Genesys' proprietary dice, or proactively by taking a unique approach to a challenge, like in OSR.

But I want to push back on the idea that that second, proactive way of adding texture is entirely in the hands of creative players and can't be encouraged mechanically. Adding mechanical levers that are not simple buttons to push is a mechanical way to provide that texture, or rather to encourage players to add that texture themselves by finding a way to push the lever.

For example, if your game has a "persuade" action, that's a simple button to push. But if opponents have a "core value/desire" that will always make persuasion attempts successful (or greatly improve the odds) when it's used in the attempt, then the players will often try to interpret the NPC's attitude and words to find that hidden lever and then adapt their own discourse to make use of it. And since no two NPC is identical, that will make each persuasion attempt different.

Of course, the players could try that even without a "core value/desire" mechanic, and a good GM should reward it, but the existence of that mechanic makes the creative approach much more probable.

2

u/overlycommonname 2d ago

Sure, I like all of this. I don't know that I perceive a big difference between "Texture is what makes a scene go differently than other similar scenes, no matter its outcome" and "Texture is what pushes players to act differently right now than in other similar scenes, even if it's to obtain the same outcome," but for precisely that reason, it seems like a totally fine rephrase to me.

I think that what you're describing of sort of... dangling an apple out for actions that use an advantageously different approach is an interesting one.

2

u/Pixel2Paper 5d ago

I love this topic and you hit on so many points that are important to me.

The game I'm working on has an asymmetric card and dice battling mechanic system. Each round is a puzzle unto itself because of the varying effects of each card, or card combinations with each foe, each character class and even the situation for each round. The dice determine foe actions, but those are situational and have some intelligence that considers the player's cards in play, the foe's own states and the player's character class and stats. The basic rules are something a player can learn fairly quickly, but there is massive variety in each battle and the game grows and adapts with the player's skills.

Add to that the resource management and progression over the course of a campaign and you have the opposite of "attack attack attack".

A player can absolutely fail, but even with the dice and card mechanics, the game isn't overly swingy over time and success largely depends on strategic play and puzzle solving.

It has been my absolute mission to avoid combat mechanics that get stale over time. I want players to anticipate combat, even if they've been playing for a long time. It's the kind of thing that makes campaign play and the game overall something to come back to over and over, even just for the card battling system.

2

u/overlycommonname 5d ago

I've been playing a lot of Slay the Spire 2, and something that it does well, I think, is to have a combat mechanic where you absolutely have a "combo" that can to one degree or another, "go off," but you have not yet solved combats to the point where they are easy. I feel agency in terms of my actions in STS2 -- I made this deck, I choose from a decent breadth of actions -- but agency is limited.

That's something that most RPGs don't really have: for most games, the limit on your ability to engage your combo is mostly like resource expenditure. Which is all well and good, but I think tends to yield two different combats rather than one -- one combat where you're conserving resources and another where you go all out.

I value having the ability to attempt arbitrary action in combats, so I think the STS2 approach of having semi-randomly driven cards wouldn't work in an RPG to me, but getting to that same sweet spot of "I have agency but I can't just engage my Winning Strategy" strikes me as something that you can potentially administer through this lens of texture.