Senior Member
Join Date: Mar 2013
Posts: 150
|
There are some data that I would never choose to reveal to players, others that could potentially damage a campaign if I let them slip ("Hey, did you guys all know that reporter over at the Daily Planet is actually Superman? Oops!"). I would find it reassuring if there were an option in the General Tasks dropdown for individual tidbits to "lockdown" the tidbit, preventing revealing it until it is set to an "unlocked" state. This might be represented in the GUI by changing the appearance of the reveal icon to a different color or maybe something like a padlock. If a GM wanted to make regular use of this feature, he could set a default lock state for tidbits defined in the Manage Categories section (for example, tidbits under a "Dark Secrets" section in the "Individual" topic structure might be defined to be locked by default).
Alternately, maybe a global option under something like Preferences that prompts for confirmation before revealing any tidbit. |
#1 |
Senior Member
Join Date: May 2013
Location: Birmingham, UK
Posts: 459
|
What about a Tag domain with two options, locked and unlocked, followed by the info in the annotation section.
When Locked is selected the info is locked like Dr_Automaton suggested! |
#2 |
Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 691
|
I've been toying with this idea myself. Aside from just preventing accidental reveals of important stuff, I like to give myself "stage directions" that are really just for me as a GM. It wouldn't be fitting to reveal these bits to the players, but it would be helpful to have them in the same body of content in close proximity.
I can't promise we'll be implementing it this way, but consider it on my radar. |
#3 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 8,232
|
On a technical level, that's all perfectly reasonable. We just need to figure out the best way to model it and then put it on the seemingly infinitely long (and ever-growing) list of things to do.
|
#4 |
|
|