billd91
Not your screen monkey (he/him)
The second example came up recently in a game of Star Trek Adventures that my group played. We have one member of the group that is a huge Star Trek fan. We have two others who are also big fans, and then three that are moderate fans (including me). So the GM decided that the game would be set in The Next Generation era. One of the players who is a casual Star Trek fan wanted to make a Klingon character. The GM restricted that race because "there was only one Klingon Starfleet member at that time, and it was Worf". So the player wound up making another character. There was no big dustup or argument about it....but this struck me as really odd. The GM's sense of fidelity to the setting trumped the player's desire. Basically, the GM decided to maintain the unique nature of a NPC rather than allow the player to play what he wanted. As if having a second Klingon in Starfleet would somehow "ruin" the setting.
To me, this is a clear case where it's basically let the player play what they'd like. The justification to maintain the setting status quo as it relates to Worf seems a very odd decision to me. Who cares about Worf? He never even showed up in our game at all.
What if they had wanted to play another android like Data? A Klingon isn't that hard to justify even if someone wanted to keep Worf the only Klingon in Starfleet - they'd just have to be part of the officer exchange program that we saw in "A Matter of Honor" from season 2. Then, the'd still be part of the Klingon Empire as well as available on a Starfleet vessel - lots of plot hook connections both ways.
But Data really is supposed to be unique. You could come up with yet another Soong android, but that really would cheapen the chachet of being an android if you're just going to retcon more as you need them.
Of course, the most obvious alternative... if you want to be an android like Data - play Data.