For more context: one player who wants to join likes a current player who wants nothing to do with him romantically(one’s gay, one’s not) and the issue is arising with player one who wants to https://mobdro****/https://vidmate****/ join creating characters that almost exactly match the current players.(also player two has no idea about player one’s interest and I obviously plan to keep that a secret sense we are all friends)
I would ignore the “context” as irrelevant and simply say no duplicate PCs allowed. They can play the same race, but must choose a different class, or they could play the same class, but must choose a different race and subclass. Simply explain that it’s healthier for the game if each character gets to stand out from the group in their own way, and that duplicate characters make that difficult. There’s nothing wrong with two PCs of the same race, or the same class, but not both and definitely not the same subclass. It’s all about the game, not the context, so keep it all about the game and you’ll be fine.
I'm not sure if your game has already been in progress for a while and this is a late joiner or not. If you haven't had a session zero with your group yet now is absolutely the time. That's the opportunity for them to collaborate on backstories and/or set boundaries for any "my character knows their character" type stuff. In that scenario it's up to the other player to consent if they're okay with this player wanting to tie their stories together, or refuse if they don't like the idea. If this person is joining after the campaign has already been in progress for a while, then you're going to have to sit them down for a one on one crucial conversation.
There isn't a reason not to allow two even identical builds are the table mechanically, unless the build itself has issues you don't want to deal with. Unless there's concern about the players being upset over being great at the same things. It can be fun on running for a group that has zero idea how to pick a lock, and believes the mighty sledge hammer IS a lock pick.
Honest discussion always beats guessing at players feelings and thoughs for why people want to do X character, or even Y they play, I'm sure you Z my point.
Puns aside, if this is a new character joining (or a new player) redoing a ZERO is a good idea. Speaking as someone that's made the mistake of adding a new player, and having a one on one ZERO - don't end it there - get the group involved., new character? REMINDERS time! New player? Reminders! Why? Because maybe someone forgets that *this* story is a no-nonsense organized structure game where the PC's are in a para-military organization, and the new player, while aware of this, doesn't really understand there are consequences for refusing direct orders (rare though direct orders are), and the established players - they forgot.
Take the time - get everyone on the same page again, it's worth it.
Yeah, if the other player consents to having their PC cloned, then I suppose it’s alright, but as a player I wouldn’t be okay with it. I played a Goblin Battle Master in a party with two other Fighters once, but one was a Half-Elf Echo Knight, and the other was a Dragonborn Eldritch Knight. Three Fighters was fun, but if we had all played nigh-clones of one another’s characters it woulda got real old real fast. I’ve frankly never met anyone who didn’t immediately switch up their character when they realized someone else was playing the same subclass. 🤷♂️
Ideally, players shouldn't be too similar. Not because of weaknesses, but because of strengths. If you have two people that are great at picking locks, then there are only so many locks to pick and therefore give spotlights to a given character. There's a good reason why the four Hobbits wwre split up, Boromir (rather than Legolas or Gimli) was killed, why Glorfindel didn't come along. I'd allow it if players wanted to, with the above warning that it might not be as fun as they think.
That being said, that's off topic. If it concerns you, just do as the above advice says. Get them all together, explain the ground rules, mention that you don't want characters that are too similar to make it easier for you to make each one integral to the party. Let someone volunteer to change characters. The late comer being the obvious choice if there is one.
Rollback Post to RevisionRollBack
If you're not willing or able to to discuss in good faith, then don't be surprised if I don't respond, there are better things in life for me to do than humour you. This signature is that response.
I think you have a few questions, the first player V player romance, PC V PC romance and like PC's.
I think people have answered the like PC's above the other two "can/could or not" be very problematic and should be talked about with the group. I agree that RP is social but in my opinion there are other better ways to instigate romance and it should not be a "game thing".
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
For more context: one player who wants to join likes a current player who wants nothing to do with him romantically(one’s gay, one’s not) and the issue is arising with player one who wants to https://mobdro****/ https://vidmate****/ join creating characters that almost exactly match the current players.(also player two has no idea about player one’s interest and I obviously plan to keep that a secret sense we are all friends)
I would ignore the “context” as irrelevant and simply say no duplicate PCs allowed. They can play the same race, but must choose a different class, or they could play the same class, but must choose a different race and subclass. Simply explain that it’s healthier for the game if each character gets to stand out from the group in their own way, and that duplicate characters make that difficult. There’s nothing wrong with two PCs of the same race, or the same class, but not both and definitely not the same subclass. It’s all about the game, not the context, so keep it all about the game and you’ll be fine.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I'm not sure if your game has already been in progress for a while and this is a late joiner or not. If you haven't had a session zero with your group yet now is absolutely the time. That's the opportunity for them to collaborate on backstories and/or set boundaries for any "my character knows their character" type stuff. In that scenario it's up to the other player to consent if they're okay with this player wanting to tie their stories together, or refuse if they don't like the idea. If this person is joining after the campaign has already been in progress for a while, then you're going to have to sit them down for a one on one crucial conversation.
ltgrunt has it right.
There isn't a reason not to allow two even identical builds are the table mechanically, unless the build itself has issues you don't want to deal with. Unless there's concern about the players being upset over being great at the same things. It can be fun on running for a group that has zero idea how to pick a lock, and believes the mighty sledge hammer IS a lock pick.
Honest discussion always beats guessing at players feelings and thoughs for why people want to do X character, or even Y they play, I'm sure you Z my point.
Puns aside, if this is a new character joining (or a new player) redoing a ZERO is a good idea. Speaking as someone that's made the mistake of adding a new player, and having a one on one ZERO - don't end it there - get the group involved., new character? REMINDERS time! New player? Reminders! Why? Because maybe someone forgets that *this* story is a no-nonsense organized structure game where the PC's are in a para-military organization, and the new player, while aware of this, doesn't really understand there are consequences for refusing direct orders (rare though direct orders are), and the established players - they forgot.
Take the time - get everyone on the same page again, it's worth it.
Yeah, if the other player consents to having their PC cloned, then I suppose it’s alright, but as a player I wouldn’t be okay with it. I played a Goblin Battle Master in a party with two other Fighters once, but one was a Half-Elf Echo Knight, and the other was a Dragonborn Eldritch Knight. Three Fighters was fun, but if we had all played nigh-clones of one another’s characters it woulda got real old real fast. I’ve frankly never met anyone who didn’t immediately switch up their character when they realized someone else was playing the same subclass. 🤷♂️
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Ideally, players shouldn't be too similar. Not because of weaknesses, but because of strengths. If you have two people that are great at picking locks, then there are only so many locks to pick and therefore give spotlights to a given character. There's a good reason why the four Hobbits wwre split up, Boromir (rather than Legolas or Gimli) was killed, why Glorfindel didn't come along. I'd allow it if players wanted to, with the above warning that it might not be as fun as they think.
That being said, that's off topic. If it concerns you, just do as the above advice says. Get them all together, explain the ground rules, mention that you don't want characters that are too similar to make it easier for you to make each one integral to the party. Let someone volunteer to change characters. The late comer being the obvious choice if there is one.
If you're not willing or able to to discuss in good faith, then don't be surprised if I don't respond, there are better things in life for me to do than humour you. This signature is that response.
I think you have a few questions, the first player V player romance, PC V PC romance and like PC's.
I think people have answered the like PC's above the other two "can/could or not" be very problematic and should be talked about with the group. I agree that RP is social but in my opinion there are other better ways to instigate romance and it should not be a "game thing".