Reply to thread

Message

<blockquote data-quote="Hussar" data-source="post: 4843415" data-attributes="member: 22779">Hoo boy, this thread took off on me.&nbsp; Yay me for starting a popular thread.&nbsp; <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f600.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":D" title="Big grin&nbsp; &nbsp; :D"&nbsp; data-smilie="8"data-shortname=":D" />First off.&nbsp; ST - some fantastic thoughts there.&nbsp; Great advice.&nbsp; Definitely food for thought.&nbsp; I'll get back to this when I've done some reading.&nbsp; <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />&nbsp; Also, thanks for finding my question in the scrum.&nbsp; Well done you sir.Next, HowandWhy99.This I disagree with 100%.&nbsp; And here's why:&nbsp; I cannot change the damage output of a weapon because that fact has been established.&nbsp; The players have access to that information at character generation, and may very well have used that particular weapon in the game.&nbsp; If I suddenly change that rule, I better have a damn good reason why.However, I can &quot;raise or lower the pole vault bar&quot; at any point up until the players have tried to make the jump as it were.&nbsp; The altitude of the bar is in no way fixed until such time as the PC's have interacted with it.&nbsp; Either they've seen it, or are in the middle of trying to jump over it.&nbsp; Presumably they've investigated it first.&nbsp; If I tell the PC's the bar is 15 feet and then make it 20 feet when they attempt to jump, that's bad DMing.However, if my module says 15 feet, but I announce to the players that it's 10 feet because I want to make the challenge easier, that is entirely my prerogative as the DM.&nbsp; If there is one thing EVERY SINGLE RPG out there agrees on its that.&nbsp; The DM/GM/Referee has absolute control over every &quot;fact&quot; in the game world until such time as it is established as canon by the players.Yeah, I agree.&nbsp; There is no answer to this other than, what makes everyone happy.&nbsp; You have to build a bit of a consensus here with the group and go with that.&nbsp; It might even be a case of quid pro quo between different players.&nbsp; Maybe this session we're going to drag our heels and talk to every shop keeper, but, you turn to Bob, who's rolling his eyes, give him a nudge and a wink and let him know that next session will be guns a blazin'.&nbsp; That was the problem I ran into.&nbsp; I was Bob.&nbsp; I wanted to get going because I wanted to see where the plot of the Adventure Path was going.&nbsp; The rest of the group wanted to saunter and explore.&nbsp; Basically, a failure in coming together with play styles.&nbsp; Looking back at it, as a player, I should have let my frustration be known more constructively to the DM and the other players and tried to find a way to have my cookie without piddling in the pool.&nbsp; I'm sure we could have compromised.&nbsp; In fact, I have recently rejoined that group and that's precisely what has happened.&nbsp; The plot is advancing nicely, and we have lots of roleplay sessions as well.&nbsp; Everyone seems to be happy.</blockquote>

[QUOTE="Hussar, post: 4843415, member: 22779"] Hoo boy, this thread took off on me. Yay me for starting a popular thread. :D First off. ST - some fantastic thoughts there. Great advice. Definitely food for thought. I'll get back to this when I've done some reading. :) Also, thanks for finding my question in the scrum. Well done you sir. Next, HowandWhy99. This I disagree with 100%. And here's why: I cannot change the damage output of a weapon because that fact has been established. The players have access to that information at character generation, and may very well have used that particular weapon in the game. If I suddenly change that rule, I better have a damn good reason why. However, I can "raise or lower the pole vault bar" at any point up until the players have tried to make the jump as it were. The altitude of the bar is in no way fixed until such time as the PC's have interacted with it. Either they've seen it, or are in the middle of trying to jump over it. Presumably they've investigated it first. If I tell the PC's the bar is 15 feet and then make it 20 feet when they attempt to jump, that's bad DMing. However, if my module says 15 feet, but I announce to the players that it's 10 feet because I want to make the challenge easier, that is entirely my prerogative as the DM. If there is one thing EVERY SINGLE RPG out there agrees on its that. The DM/GM/Referee has absolute control over every "fact" in the game world until such time as it is established as canon by the players. Yeah, I agree. There is no answer to this other than, what makes everyone happy. You have to build a bit of a consensus here with the group and go with that. It might even be a case of quid pro quo between different players. Maybe this session we're going to drag our heels and talk to every shop keeper, but, you turn to Bob, who's rolling his eyes, give him a nudge and a wink and let him know that next session will be guns a blazin'. That was the problem I ran into. I was Bob. I wanted to get going because I wanted to see where the plot of the Adventure Path was going. The rest of the group wanted to saunter and explore. Basically, a failure in coming together with play styles. Looking back at it, as a player, I should have let my frustration be known more constructively to the DM and the other players and tried to find a way to have my cookie without piddling in the pool. I'm sure we could have compromised. In fact, I have recently rejoined that group and that's precisely what has happened. The plot is advancing nicely, and we have lots of roleplay sessions as well. Everyone seems to be happy. [/QUOTE]

Verification