cbwjm
Seb-wejem
Assert what?This is written assuming that PC -> NPC. Since that is the entire point of this thread, you can't just assert that without any support.
Assert what?This is written assuming that PC -> NPC. Since that is the entire point of this thread, you can't just assert that without any support.
What you wrote assumed that PCs become NPCs, without saying anything in support of that. Since that's the whole point of this thread, making that assertion without support undermines anything else said since that's not agreed on.Assert what?
The game and the work in total both belong to the group, not the DM. Specific elements may be yours, but the game is not.Sure, your character is your creation, but once they're part of my game now they're a part of my creative work.
Yeah the idea of any of my characters being "former" in any way is absurd, to me. They're my character.I have a friend who got a tattoo of his favorite character. He's recreated him across multiple campaigns and even multiple systems. The idea that it is his "former" character is bizarre to me. It's his character, nothing former to it.
I'm not the person you were asking, but I don't bring up if we're going to use d20s at Session 0 even if I have strong feelings that 2d10 bell curve isn't right for D&D. Why? Because it's the default to use d20s and unless we hear otherwise we don't need to chase every possible non-standard thing down to ensure that it isn't being surprised on us.Soo.... What is the typical reaction when you bring all of this up im session zero? You did make sure to have the group do a session zero so you could get these rather strong feelings that you seem to have out right? It seems like a player bringing up all of this would immediately present as a major red flag even if I was another player at some other GM's table.
There is a leap here caused by a false boolean.That said, the specific example this conversation spun off from was of a character choosing not to participate in the activity the game is explicitly about and thereby becoming an NPC. And this is a different beast entirely. Every player at the table has a responsibility to make a character that is going to participate in the game. This is a pretty non-controversial statement, in general. If you make a character that is antagonistic, antisocial, and decides to wander off away from the rest of the group to solo adventures, the DM is entirely within their rights to go "Congratulations, you're an NPC now. Now either make a character that will be a part of the group, or find another table" rather than running a separate solo adventure for you while the rest of the group sits around doing nothing. This applies equally to "I'm going to sail away to a new continent without the rest of the group," "I'm going to retire from adventuring to start a quaint little B&B," or any other form of choosing not to participate.
I said what can happen in my games. I don't need to write an essay in support of what can happen in my games.What you wrote assumed that PCs become NPCs, without saying anything in support of that. Since that's the whole point of this thread, making that assertion without support undermines anything else said since that's not agreed on.
If they’re not being played by the player, they’re an NPC in that campaign to be used by the DM as the situation necessitates. I don’t see that as particularly controversial. If the PCs are never in a position to encounter that character again, fine. If they do, however, the character is now the DM’s responsibility since the player who used to play them is either gone or has moved on to another character that now serves as their PC. Giving up playing a PC, as I see it, automatically relegates them to NPC status for as long as that situation persists.Sure, but they don't automatically become an NPC, that needs to be transferred by the player.
This thread demonstrates that the default is not as defaulty as some think it is. For an issue as important to some players as "ownership" of a character is, it behooves the player not to leave it as an unspoken default.Why would I address the default that the player owns the character?