- Code: Select all
|>Main channel (cannot be joined)
| |-->Group 1 Subchannel 1
|-->Group 2 (cannot be joined)
| |--> B
| |--> B1
| |--> C
| |--> C1
| |--> D
| |--> D1
Currently Group 1 and it's subchannel are linked. A is linked with A2, B with B2 etc.
The desired situation is that those in the subchannels of Group 1 Subchannel 1, A1, B1, C1 and D1 can talk to their parent (and hear their parent) using the usual PTT. Linking does this fine/
The other desired situation is that those in Group 1 Suchannel 1, A1, B1 etc. can talk to one another without that being broadcasted to their linked channels and without the usual PTT being broadcast across them.
Currently this is reached by everyone who needs this setting up a series of shouts set to the same shortcut key where the "Shout to linked channels" checkbox is left clear.
The problem is is that the channels we use are more extensive than above, and are likely to grow. That's a lot of shouts to setup. Those using this shout system are not always the same people (hence the client-side shout system rather than having to have admins available to constantly update group memberships or using a whisper-to-tokens system where users have to add / remove their token all the time)
Would the following work?
Same setup as above but includes a new "Group shout" subchannel for the main channel. This channel cannot be joined by anyone. It is linked to Group 1 Subchannel 1, A1, B1 etc etc. and such links are updated as new channels to be part of the structure are added.
Group 1, A, B, C etc. are setup using ACL to deny speak to @out and allow speak to @sub. Setup does not cascade to subchannels.
Anyone wanting to use this shout-structure only needs to add a shout & shortcut to the new "Group shout" channel, this time setup with "shout to linked channels".
My assumption is that Group 1, A, B etc. will not hear what is shouted to "Group shout" despite being linked-by-proxy. That the deny speak to @out set in the ACL will over-ride the shout shortcut?
Links to "group shout" can then be updated as needed and users will never need to do anything beyond a one-time setup of a shout shortcut to "group shout"