• NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.

Fighters vs. Spellcasters (a case for fighters.)

In other words, every time we talk about players who are trying to create a bad experience for everyone at the table, we also talk about how easy the solution is.

If anyone ever started a thread about players who can behave, you'd see it differently then. Most of the time, players try to do things that aren't abusive, which creates a rather different dynamic.

I think they would if you tried them (and generally understood them). But we certainly can't make you.

Thing is, I do understand your way of doing it. I've done your way for years. Throughout 1e and 2e and early 3e, I certainly played this way.

The solution may be easy if your players are amenable. I and my players no longer are. My players are not out to abuse things. Never were. That's why I implicitly trust my players to make the game better and don't feel that it's my job as the DM to do that. I supply the scenarios and adjudicate the rules. I don't have to play hall monitor on their actions to make sure that they stay within the limitations that your DMing style creates.

IOW, trust your players. They will make your game better.
 

log in or register to remove this ad

In other words, every time we talk about players who are trying to create a bad experience for everyone at the table, we also talk about how easy the solution is.
This is a complete red herring. The player of an enchanter who tries to charm the Chamberlain isn't trying to create a bad experience for everyone at the table. That player is trying to engage the scene and resolve the confrontation.

The solution to players who try to create a bad experience is to exclude them from the group. But I've personally never really seen this come up, because in my experience most people have better things to do with their leisure time than to try and create bad experiences for themselves and others.

I also don't perceive a challenge between the PC's and their desired goals as deliberate obstructionism on the part of the GM, but as part of the challenge, and the fun.
Sure, but that leaves open all the questions being discussed in this thread - what is the basis on which challenges are posed (thematic or procedural) and what is the basis on which action resolution unfolds (GM force or not)?

Long story short, for player-driven play, don't set the scene before the players arrive. I know there's years of orthodoxy that says "Oh, the campaign world totally functions without the PCs, it's like it's really there!" is the defacto best way to play. Player-driven play doesn't give two figs about that. The campaign world is there to be a stage for the PCs to be awesome and interesting.
This - although the awesomeness resides primarily in the struggle - the PCs might lose, but their loss is itself an awesome event.

I think we might have different definitions of what constitutes curtailing protagonism, and some of it likely goes back to game philosophy. It sound to me like you think consequences for PC actions should always come from within the mechanics, not from within the storyline.
As [MENTION=205]TwoSix[/MENTION] suggested, I don't really feel the force of this contrast. The point of mechanics is to generate the plot, in roughly this way: the GM frames a scene; the players, via their PCs engage it by declaring actions; those actions are resolved; now we have some plot (what happened) plus some new threats/complications/possibilities (the outcomes of resolution + new material injected by the GM) and the process continues.

you do not think NPCs serving as antagonists to the PCs works to make the PCs better protagonists.
Of course NPCs serve as antagonists to the PCs. The key issue is the nature of the antagonism, and how it is overcome. [MENTION=6681948]N'raac[/MENTION]'s example of the Chamberlain is not just an NPC serving as an antagonist to the PCs. As desribed, (i) it has no prior motivation or thematic heft (contrast: part of the thematic point of the game is to address the degradation of the nobility), and (ii) it is not amenable to being overcome via the players engaging the action resolution mechanics.

(i) and (ii) are the key features of the Chamberlain example that make me (and, I believe, [MENTION=22779]Hussar[/MENTION]) hostile to it. Not the fact that it is an instance of antagonism.

I do recall when I suggested this a few pages (or more) back, that I was derided for somehow putting down your playstyle.
The way I play is a version of what I characterised way upthread as the "indie" style. At that time I suggested that the various comment that you, [MENTION=6681948]N'raac[/MENTION] and others were making about spellcaster balance were viable for other styles (eg storyteller style) but not for indie style. Nothing in the intevening 100s of posts has changed my mind on that.

You are suffering from a preconceived idea of what others mean and its coloring your interpretation of their words. One does not need to have some "script" being followed to recognize that the play experience is suffering. Maybe even the DM has a "script," if he recognizes its not going well and changes it on the fly so it turns out different, we again alleviate any contradiction.
I see. You are putting a weight on the word "preconceived" that I didn't intend it to bear - a better word might have been "chosen independent of the process of action resolution".

In the sort of game play that I very strongly prefer, the GM has no conception of how the situation will resolve that is independent of the process of action resolution.

If the play experience is suffering, that tells us that we need to do something outside the context of play to sort it out. That's not something to be addressed from within the game itself. (But as came up in reply to [MENTION=6701124]Cadence[/MENTION] upthread, I play a system which reliably produces a desired play experience without the need for GM force.)

I want my player's character to make an impact on the game world, but I want there to be meaningful opposition to their doing so. Being a protagonist does not preclude that someone might not notice the wizard using charm, or the possibility that Diplomacy may not work on everyone.
First, I am talking primarily about player protagonism - whereas your response is framed by reference (I think) to PC protagonism. I don't want to put undue weight on terminological choices, but I think it might have some significance here. In paticular, player protagonism does require approaching action resolution in a certain way. The player has to have a meaningful chance of determining the outcome of any confrontation.

I like DMing, in part because I like the world-building.
OK. But this sort of world-building tends to be in tension with thematic play (because there is a temptation to resolve the thematic questions already in the world history), and with an absence of pre-planning (because there is a temptation to push on with the pre-established dynamics of the pre-written gameworld) and with player protagonism (because there is a temptation to stop the players running rougshod over and imposing their will upon the gameworld).

For instance, perhaps the DM knows the Chamberlain is suffering from dementia. There are no rules in the rulebook for this, so he makes something up and goes with it, deciding the Chamberlain is going to act childlike and diplomacy is impossible while the Chamberlain is so afflicted.
So there is your problem, from my point of view. First, your action resolution mechanics aren't robust enough to frame a dementia scene withou fiating, which then causes problems like the GM ruling that Diplomacy can't work (fine as far as it goes,if incling a little towards the heavy-handed) but not having the techniques or scope within action resolution to inform the players of what other action resolution options (like Insight + Heal) are open to them.

The idea of curtailing the player by having his/her wizard detected by an NPC scryer is - as presented - an even greater burden on protagonism, because the outcome of the confrontation between PC and NPC is determined by a factor over which the player had essentially no control and no engagement via action resolution.

if you, because of your desire to give your PCs great latitude, choose to ignore parts of the rules which might make things more challenging for your players, then you are doing the exact same thing as someone who is enforcing only those parts of the rules which provide challenge, though in reverse.
Again, to focus on challenge is to focus on something that I think does not differ much over playstyles. The issue about GM force is not about challenge, it's about resolution. My objection to a Chamberlain who can't be talked to, or can't be charmed without being detected, isn't that these are challenges - it's that they're deprotagonising challenges, because as presented the player has no way to engage the scene and thereby impose his/her will upon the fiction.

Protagonism isn't aways about successfully imposing one's will - sometimes action resolution mechanics deliver success to the players, sometimes failure - but protagonism requires the possibility of imposing one's will.

Perhaps the DM actually wants the PCs to see the king, but the story demands, because of ingame events, that they deal with the Chamberlain first and the DM's actions actually hinder his desire to have the players get to the king
And here we have (i) a GM's preconceived plan, and (ii) GM force - in the Chamberlain encounter - to give effect to that plan.

As I said upthread and earlier in this post, in my game there is not preconceived story. There is no "the story demands" that event (A) occur before event (B). The playes are invited to impose their wills upon every confrotation that is framed.

The Chamberlain is either crazy before the PCs arrive or he is not crazy. A botched roll on the part of the PCs resulting in the Chamberlain being possessed is a foreign sorta concept to me, but seems exactly what I mean by saying the consequences come from within the mechanics (ie. a botched roll) instead of the story-line (a demon trying to take over the kingdom via driving the Chamberlain crazy).
You are drawing a distinction here between fiction and mechanics that is somewhat foreign to the way I play the game.

Why would I, as GM, frame a scene with a crazy Chamberlain? Because it speaks to something that matters to the participants in this game, as expressed through PC build and past play. Upthread I've given the example of the degradation of the nobility.

Suppose I don't frame the Chamberlain as crazy, but have the Chamberlain become possessed in response to a player's failure in action resolution - why would I do that? Because the player is a demon hunter; or, perhaps, a demon summoner whose magic misfired. Why does my actual game feature a lot of undead? Because half the party are Raven Queen devotees.

I challenge you to try to envision a game in which the DM strives both for a thematic sort of framing and resolution and maintains an in-game verisimilitude through the use of NPC reactions (both short and long term) to PC choice.
I didn't say anything about verisimilitude. I said "the causal logic of the gameworld". These are very different things - verisimilitude as a constraint on introducing events into the fiction is barely a constraint at all, because nearly anything can be rendered verisimilitudinous with the right backstory.

But challenging me to envision a game in whicht the GM strives for both thematic and causal-logical-constraind framing is like challenging you to envision a ruler-and-compass process for squaring the circle. It can't be done. If you are going to resolve events by reference to the causal logic of the gameworld you will sacrifice thematic framing. The illustrations are too numerous to list in a single post, but here are two (and [MENTION=6696971]Manbearcat[/MENTION] has given more upthread, a page or so above your post, with his discussion of Action vs Transition scenes): (i) causal logic requires that ammunition tracking, and encumbrane, be real constraints on action resolution, but I can imagine almost no game in which these have any thematic weight whatsoever; (ii) causal logic requires attending to the details of travel over great distances on foot, and in a game adjudicated by reference to causal logic the ability to teleport therefore serves as an important way to avoid all those elements of action resolution, whereas in many games overland travel has little to no thematic significance.

Upthread I used the contrast between "prodedural" and "thematic" obstacles to capture this distinction.

Long story short, the idea of player-driven play, where the DM always says "yes," if possible
Not "if posible". Rather, "if nothing thematically interesting presents itself". And a GM who regularly has trouble thinking of thematically interesting challenges is a bad GM for this sort of play. (Likewise their is an onus on players to build PCs who have thematic heft. Luckily 4e mostly - not completely = takes care of this through the story elements that come into play via PC build.)

I think PCs are more awesome and interesting when they do awesome things and make interesting choices, not merely because the mechanics dictate they are awesome.
What does this even mean?

The PCs are fictional constructions within an imagined world. Anything awesome in that fiction only becomes part of the fiction because the participants put it there. What is the basis on which people get to put awesome things into the fiction? Primarily via the mechanics. If you are playing a game in which the mechanics impede rather than engender interesting choices (for instance, because they make choices about encumbrance and inventory management more important than choices about what to say to the demented Chamberlain) then that would seem to me to be a problem with your game's mechanics.

Conversely, if your game has mechanics that engender interesting choices, what do you think you are contrasting in the passage I've quoted.

For instance, in a fairly recent episode, First AP of the Shattered Star campaign to be exact, while the PCs were visiting an informant, the 1st level rogue sees some people dicing, and decides to pick their pockets. This was not anything I had planned. He attempted it, and through the use of the resolution mechanics was spotted. The hoodlums gave chase, the rogue ran and hid, and discovered his attempt had netted him only a few coppers.
I may be missing some context, but as I read it this instance of play seems to have almost no relevance to the overall dynamics of the campaign or the story development. In fact, while I'm not that familiar with the details of adventure path play, my general understanding is that the basic plot of the campaign has already been preconceived and written up by the adventure path author. That's pretty much the opposite of the sort of play I'm talking about.

When I'm talking about "thematically driven play" and "no preconception", I'm meaning events like this:

The PCs include servants of the Raven Queen and other undead hating gods, but one who also has an ambiguous relationship to Vecna. They promise to the baron, who is an ally of theirs and their host, to track down his missing niece. They find her, but discover that she is a Vecna-ite necromancer who is inadvertantly rousing Kas from dormancy. They therefore do battle with her, and in order to save her from Kas swear an oath to Kas to track down his nemesis from 100 years ago, who also happens to be a wizard whom, as an apprentice, they rescued from a magical trap when they were in the past on a time-travelling adventure.

(Writeups here and [urlhttp://www.enworld.org/forum/showthread.php?299440-Exploration-scenarios-my-experiment-last-Sundayhere[/url].)​

In other words, whether the PCs are allies or enemies of Kas and Venca, and how that will play out in the game, is up for grabs to be resolvd through actual play. The whole point of play is to discover, through play, what is worth struggling for and what not, which cosmological beings need to be opposed and which aided.
 

D&D is by default a DM-driven game, is written as such (with the possible exception of 4e), and is played as such.
I agree with your points. It's why I find all this talk about Charm Person a little trivial. Don't play 3.X games as player-driven! They suck at it! That's pretty damn obvious.
It may be that 3E is a GM-driven game. But 1st ed AD&D is not written as a DM-driven game. Have a look at Gygax's discussion, in the final pages of his PHB before the appendices, of what is involved in preparing for an adventure. That's not about DM-driven play.

For instance, Gygax presupposes that players can equip their PCs out-of-session, presumably by dedcuting gp from their PC sheets and adding gear to their equipment lists: that is player authority to change the content of the fiction. He assumes that the players, not the GM, decide what the adventure will be - goals, targets, methods, etc. (The GM's role is simply to have prepared a location - a dungeon for the PCs to plunder.)

Speaking purely for myself, I began to develop my current GMing style playing Oriental Adventures in 1986. This contains many of the key elements of player-driven gaming - a thematically-laden backstory (the classic Celestial Bureaucracy trope, familiar to Australian players at least through watching many episodes of the TV show Monkey, plus the classic samurai/obligation/loyalty/mysterious martial arts master tropes that are ubiquitous in samurai and kung fu fiction), together with PC generation that locates the PCs within that thematically-laden backstory, and that makes coming up with engaging scene very straightforward.

It's true that the action resolution is a bit rudimentary - out of combat we're talking about CHA rolls on the old AD&D reaction charts, plus the OA non-proficiency system - but it's not utterly hopeless. (No game had anything fundamentally different until the mid-90s, I would say.)

In other words, nothing in 1st ed AD&D points particularly towards GM-driven play, and key features of Oriental Adventures point strongly in the other direction.

It is 2nd ed AD&D that marks a significant shift in the direction of D&D play towards being DM-driven. To the extent that 3E relies upon the same sort of approach to be playable, that's an interesting upshot of this thread which I have not appreciated before. 3E certainly doesn't present itself as 2nd ed AD&D redux, at least in my memory of its rulebooks.
 

IOW, trust your players. They will make your game better.
Fair enough. I certainly do. I was basically named DM by the group by force, and spent several years experimenting and aggressively soliciting feedback to develop what I do.

This is a complete red herring. The player of an enchanter who tries to charm the Chamberlain isn't trying to create a bad experience for everyone at the table. That player is trying to engage the scene and resolve the confrontation.
Maybe. Maybe not. Without context, it is unclear in this generic example what the player's intentions are.
 

I think that's true, with two important caveats:

One, D&D is by default a DM-driven game, is written as such (with the possible exception of 4e), and is played as such.

That I will largely agree with. Certainly the Dming advice would seem to lean heavily in this direction.

Two, it's a lot easier to find one DM good enough to run a game than to find an entire group of players who are all good enough to run a game.

[/quote]

This, on the other hand, I don't agree with. Heck, the last time I posted a poll on EN World about this, over a third of the respondents said that the majority of their DM's were bad, and about two thirds said that at least half their DM's were bad. Only a very small minority (about 20%) said that the majority of DM's that they'd played with would qualify as good.

There are a LOT of poor DM's out there. Being a good player is a heck of a lot easier than being a good DM.
 

There are a LOT of poor DM's out there. Being a good player is a heck of a lot easier than being a good DM.
That may be, but even if being a player is easier, if you're running the game collectively, it only takes one bad player to drag everyone else down. Conversely, if you're running the game in a more authoritarian fashion, it's easier to mitigate the effects of one problem player, as long as he isn't a bad guy (and if he is, he needs to go regardless).
 

Fair enough. I certainly do. I was basically named DM by the group by force, and spent several years experimenting and aggressively soliciting feedback to develop what I do.

Maybe. Maybe not. Without context, it is unclear in this generic example what the player's intentions are.

I complained about this before. People had taken pretty minor corner cases (the King has ordered no interruptions on pain of death etc) and tried to claim that players should always take any fiat decision by the DM to ignore the mechanics as always based on some in game element that the players don't know about.

To me, I don't see the point of adding to all this corner case stuff. The players want to see the king. They talk to the Chamberlain to see the king. Straightforward. But the DM doesn't want the players doing that, so, he c-blocks the group by fiat. Pure DM force. And then the DM justifies himself afterwards by saying that there's some in game rationale for why things don't work.

Yeah, no thanks. If you don't want me to do something, just tell me. I'm a big boy. I'll accept that. Being frustrated by DM's trying to protect their precious scenarios is far, far more common, IME, than not.

That may be, but even if being a player is easier, if you're running the game collectively, it only takes one bad player to drag everyone else down. Conversely, if you're running the game in a more authoritarian fashion, it's easier to mitigate the effects of one problem player, as long as he isn't a bad guy (and if he is, he needs to go regardless).

Meh, don't play with jerks. Seems pretty straightforward to me.

Again, being able to stop jerks is a pretty basic function of the group, not the DM. And, generally, one bad player won't harm the game anywhere near as much as a bad DM.
 

Look, all this back and forth is great and all, but, the bottom line is, your solutions won't work for me.

I've been told, repeatedly, that I should interpret the game in a fairly specific way (choose rule interpretations for casters which are strictest (or pretty close to the strictest) interpretations possible), choose to play the in-game fiction in such a way that it disadvantages casters as much as possible (always target the caster whenever possible in combat, always have any caster actions come back and bite them on the ass, limit item creation, etc)

I haven't read the intervening posts, so my response mightn't go with the general flow, but I wanted to say that I don't believe this thread is about telling you that your game style is incorrect. Just consider for a moment, removing all speculations about motivations, if rule interpretations for casters were strict and the caster targeted only half the time, and caster actions only cane back to bite them in the ass half the time, would the caster be as effective as one who didn't have these limitations?
 

TwoSix said:
Long story short, for player-driven play, don't set the scene before the players arrive. I know there's years of orthodoxy that says "Oh, the campaign world totally functions without the PCs, it's like it's really there!" is the defacto best way to play. Player-driven play doesn't give two figs about that. The campaign world is there to be a stage for the PCs to be awesome and interesting.
I couldn't disagree more.

The campaign world is what it is, and in player-driven play the players do what they like within it; as opposed to DM-driven play where the DM leads them by the nose. But in either case there is way way more to the game world than just the PCs; either that, or you're using a woefully incomplete setting. :)

Lan-"has anybody ever posted the stats for "strawman" as a monster?"-efan
 

Every time someone steps up and tells me that they use the game world to limit power, it's always the same - every single reaction of the game world is in opposition to the players.

I think that game world used to limit power was a legitimate and deliberately engineered power check, given that wizards were designed in this way, "great power, great risk" kinda thing. If its a question of using it every single time to frustrate characters, that's not condoned by anyone here. But its not. Its a question of should its fair application be completely ignored.
 

Into the Woods

Remove ads

Top