I love the idea of your Hot Seat Observer Module because this mimics how my gaming group plays. I'm the GM running FoundryVTT from my laptop and I use an HDMI cable to drive a TV lying on the table. My players use miniatures on top of the TV screen and I mimic their miniature movement by placing their player tokens appropriately on the VTT. I drive both the GM and Player screen. The players only interact with the real miniatures.
Your baseline functionality changes the token selection on the player screen during combat when the GM goes through the initiative order from his GM screen. This works great for when your players are in combat but I am looking for slightly different utility of this feature for either being in or being out of combat.
My request is for an optional feature that could be enabled within your module to change the behavior of player token selection.
1) If the GM selects a player token from their GM screen then that same player token shall be selected on the Player screen.
2) If the GM deselects that player token from his GM screen then that same player token shall be deselected on the Player screen.
3) If the GM selects an NPC token from his GM screen the baseline FoundryVTT behavior on the Player screen shall remain the same.
4) All other player token behavior shall remain the same on the Player screen as the baseline FoundryVTT (plus added modules) behavior.
5) The Player screen token selection shall follow the most recent command of either the baseline functionality of this module or this new GM selected player token optional behavior.
An example for #5: If the party is not in combat and a GM has a player token selected then the Player screen will show that player token selected. If the GM begins combat with that player token selected the Player screen will update the player token selection to the first character in the combat tracker. If the GM then selects a different player token the Player screen would update to that selected player token. When the next player character's turn starts in the combat tracker then the Player screen will update the token selection to that player.
The #5 requirement is being written as it is anticipated this would simplify the code change by preventing the baseline functionality of the module and this optional functionality of the module from fighting for control. If this actually ends up making it too complicated and it would be simpler to have this option be an alternative means of player token control then that would be sufficient as well.
I love the idea of your Hot Seat Observer Module because this mimics how my gaming group plays. I'm the GM running FoundryVTT from my laptop and I use an HDMI cable to drive a TV lying on the table. My players use miniatures on top of the TV screen and I mimic their miniature movement by placing their player tokens appropriately on the VTT. I drive both the GM and Player screen. The players only interact with the real miniatures.
Your baseline functionality changes the token selection on the player screen during combat when the GM goes through the initiative order from his GM screen. This works great for when your players are in combat but I am looking for slightly different utility of this feature for either being in or being out of combat.
My request is for an optional feature that could be enabled within your module to change the behavior of player token selection.
1) If the GM selects a player token from their GM screen then that same player token shall be selected on the Player screen. 2) If the GM deselects that player token from his GM screen then that same player token shall be deselected on the Player screen. 3) If the GM selects an NPC token from his GM screen the baseline FoundryVTT behavior on the Player screen shall remain the same. 4) All other player token behavior shall remain the same on the Player screen as the baseline FoundryVTT (plus added modules) behavior. 5) The Player screen token selection shall follow the most recent command of either the baseline functionality of this module or this new GM selected player token optional behavior.
An example for #5: If the party is not in combat and a GM has a player token selected then the Player screen will show that player token selected. If the GM begins combat with that player token selected the Player screen will update the player token selection to the first character in the combat tracker. If the GM then selects a different player token the Player screen would update to that selected player token. When the next player character's turn starts in the combat tracker then the Player screen will update the token selection to that player.
The #5 requirement is being written as it is anticipated this would simplify the code change by preventing the baseline functionality of the module and this optional functionality of the module from fighting for control. If this actually ends up making it too complicated and it would be simpler to have this option be an alternative means of player token control then that would be sufficient as well.