robus
Lowcountry Low Roller
Funnily enough the Angry GM touches on this topic in his latest article: http://theangrygm.com/winning-rpgs/ . Specifically the section titled "Don't be an a$$hole".
This is true. It is also why WotC's definition is actually useful - it's an evolution of a word that used to mean practically nothing, because it would do no more than scare people into worrying about doing a particular thing that the outcome ended up nearly almost always being that they would do that very thing (base what actions a character can take on the player's knowledge, rather than the character's) in their attempts to avoid it.
Which is what happens every time someone labels an action as metagaming that didn't actually require the knowledge the player had in order for the character to make.
It becomes policing the player's thoughts, rather than making sure the character isn't doing things they couldn't.
But WotC's new definition? It's actually clear and easy to use, and doesn't result in situations like my favorite go-to example of why the old definition of metagaming is useless to the point of the word being meaningless - the brand new player with no knowledge at all about the game can attack a monster with a flaming log because it attacked while they were tending the fire at camp and no one bats an eye, but an experienced and knowledgeable player is "metagaming" if they do so because the DM knows the player knows what a troll is and/or that this monster is a troll rather than something else.
Says you. Unless you have been appointed high arbiter of all definitions without me knowing it, I'm not seeing how you saying it's true isn't entirely countered by the evidence that this other definition is not found anywhere in the 5th edition texts.The other definition still applies to 5e, though.
What a character has done or would do in other situations is not relevant to what the character is doing in this specific situation. That's just an artificial limiter applying to the character's actions that results in an action one player could take without issue (because they are known not to have the knowledge you are worried is being acted upon, or because they've intentionally skirted your arbitrary restriction by playing a character with as little consistency to their behavior as is possible) become forbidden to another player for out-of-character reasons.And consistent with what the character has been known to do in other situations, yes.
No. Definitely not.Maybe. Maybe not.
Turn the scenario around a bit. Imagine that the DM and the Thief actually went in the other room and none of the players left at the table knew anything about the thief drowning.Try this one: Dungeon crawl in the mountains, no lakes or rivers nearby, pparty has stopped while the Thief scouts ahead. DM tells everyone* what happens to the Thief - far enough away from the party that nobody could notice (or all such rolls fail) the Thief triggers a trap that drops him into deep water, and he drowns. Ten minutes later and long past due, all the characters know is that the Thief hasn't returned; yet the players know why. If the party decide to cautiously scout ahead and look for the Thief, going slow and searching or poling for traps or hazards makes sense. I rather think everyone's on board with me so far.
But if someone says "The Thief fell into water, so I'm casting Water Breathing on myself"? That's gone beyond the pale; the player has used player-only knowledge to determine what his character does.
Mistake #2, in my opinion, would be that the dungeon has drowning traps and is completely devoid of hints at the presence of unseen water.* - this is mistake #1; the DM-Thief interaction really should have all been by note, or out of the room.
I'm not talking about having to choose between A) pull your sword, or B) pull a torch. The scenario was specifically the choice between A) go get your sword, or B) use the burning log (or torch as you put it) that is already in your hand.True enough. But if every other time said character has needed a dangerous and destructive thing in hand she's reached for her longsword it fails the smell test if just this one time she happens to pull out a torch...
Yeah, everyone has a different tolerance for how imprecise their language is. I personally wish everyone had a lower tolerance for imprecise language, because if more precise language is used less time is spent feeling out what other people mean by the words they've used, and less misunderstandings happen, so conversations are more rapidly productive and, unless hostility is the intent, less hostile.Mostly true, yes; with the difference being I largely don't mind using the same term for all of them except outright fraud-cheating as noted above.
That's not how hit points have ever worked in D&D. Cause more hit point reduction =/= causing greater damage or pain to a body if contact occurs.The greatsword/log one, however, is more interesting. The sword clearly hurts more when it connects with a foe
Says you. Unless you have been appointed high arbiter of all definitions without me knowing it, I'm not seeing how you saying it's true isn't entirely countered by the evidence that this other definition is not found anywhere in the 5th edition texts.
I am under no obligation to prove the opposite of a claim you've made. I've stated my own position and provided what evidence their is to support my position.You're the one claiming it doesn't apply here. How about you prove it?
You've provided your position, and I've asked for evidence to support it... and you are now deflecting. Me not satisfying your request to prove you wrong doesn't make you right.
At this point it is clear you attempting to "win" rather than to have a productive discussion. So rather than do something like arbitrarily insist your evidence isn't actually evidence like you've done, I'm just going to say this:Your turn.