Quote:
Originally Posted by Cornelius
I agree that it will create redundancies. And I agree that it is counter intuitive.
It is the way things work at the moment. And secret identities create a lot of problems.
You would need to be able to identify which alias you are using and what information has been revealed under that alias.
For instance:
Players meet Midnight crawler and get a description of him. Suppose they notice he is limping (so that information is revealed).
Later they meet Finn Sawdust. They speak with him while he sits behind a desk and so do not know if he is limping.
Now how to show this to the players?
If they look up the Midnight Crawler they will see his description and the information that he is limping. (Not that he is Finn Sawdust).
If they look up Finn Sawdust they should only get the description, but not the information that he is limping.
You may end up revealing more information than you want.
Example. If players compare the notes they will notice an exact copy of the description between the Midnight Crawler and Finn Sawdust.
|
A good point - I haven't thought of that.
Particularly valid if using the player access tools.
I didn't think of this because the way I plan to use this, is to reveal the information to the players on a screen during the session. I am not planning to give them access to the information through webaccess or player client. At least not at the moment (well, it can't be done yet anyway
).
This means that I can finetune the data revealed, switching the limping on and off as needed (for example) and even let players' characters forget things along the way.
But yes, it poses a problem - how can that be solved?
Is a second identity - eh - topic really the best solution?