When opening tables I'm often restricting it to a group, which is my local gaming group. I also have friends on BGA I trust and would like to participate that aren't a member of that group.
I don't want to tell them to go join my local gaming group's BGA group to join my tables, but don't want to hold the slot for an invite they may not want join...
I'd like to see multiple restrictions slots controlling who is allowed.
I'm very open to how this happens; IMO it's unlikely there's a huge need for more than a couple of restrictions.
One thing to note is these would always be a logical OR, never an AND -- because that would cause confusion too easily (i.e. Always requiring someone to be a member of X OR Y and never evaluating as X AND Y)
To me at the very least I'd like to be able to restrict to a group AND allow my friends, so in the most basic iteration "My Friends" could be a tickbox element instead. Then the current dropdown has "My friends" removed as a choice entirely, and only show groups.
There are essentially two parts to this suggestion that come up
Example A2: Applying a restriction allowing a group and friends
By default each time the user selects something in a dropdown a new dropdown would be spawned, allowing the interface to remain less cluttered.
To ensure this feature is not abused to cause weird stuff it could be limited to X dropdowns being spawned
Example B: What the interface current looks like
Of course there are probably better ways to do it, such as listing ALL the users groups, and placing a checkbox next to each one.
Example F: Implemented using all checkboxes
I don't want to tell them to go join my local gaming group's BGA group to join my tables, but don't want to hold the slot for an invite they may not want join...
I'd like to see multiple restrictions slots controlling who is allowed.
I'm very open to how this happens; IMO it's unlikely there's a huge need for more than a couple of restrictions.
One thing to note is these would always be a logical OR, never an AND -- because that would cause confusion too easily (i.e. Always requiring someone to be a member of X OR Y and never evaluating as X AND Y)
To me at the very least I'd like to be able to restrict to a group AND allow my friends, so in the most basic iteration "My Friends" could be a tickbox element instead. Then the current dropdown has "My friends" removed as a choice entirely, and only show groups.
There are essentially two parts to this suggestion that come up
- "My Friends" should receive special treatment, and be listed first/seperately
- We should be able to select this AND one or more groups.
Example A: Allowing friends only.[X] represents a selected tickbox/checkbox element.
[-] represents an UNselected tickbox/checkbox element.
[Dropdown: Group selection]<User has selected "ACME Inc"> -- Represents a dropdown element, the angled brackets represent what the user has or hasn't done. When represented as "<Currently "-">" it means the user has not yet interacted with it
Restrict table to
[X] My Friends
Also allow people in this group:
[Dropdown: Group selection]<Currently "-">
Example A2: Applying a restriction allowing a group and friends
Example A3: Applying a restriction allowing a group and friendsRestrict table to
[-] My Friends
Also allow people in this group:
[Dropdown: Group selection]<User has selected "ACME Inc">
Otherwise, the more complex example is a series of dropdowns.Restrict table to
[X] My Friends
Also allow people in this group:
[Dropdown: Group selection]<User has selected "ACME Inc">
By default each time the user selects something in a dropdown a new dropdown would be spawned, allowing the interface to remain less cluttered.
To ensure this feature is not abused to cause weird stuff it could be limited to X dropdowns being spawned
Example B: What the interface current looks like
Example C: After selecting one groupRestrict table to group(s)
[Dropdown: Group selection]<Currently "-">
Example D: After selecting two groupsRestrict table to group(s)
[Dropdown: Group selection]<User has selected "ACME Inc">
(optional) Also allow members of:
[Dropdown: Group selection*] <Currently "-">
Example E: After selecting three groupsRestrict table to group(s)
[Dropdown: Group selection]<User has selected "ACME Inc">
(optional) Also allow members of:
[Dropdown: Group selection*]<User has selected "My Friends">
(optional) Also allow members of:
[Dropdown: Group selection*] <Currently "-">
* This is far more complex since each future drop down should remove previous selections.Restrict table to group(s)
[Dropdown: Group selection]<User has selected "ACME Inc">
(optional) Also allow members of:
[Dropdown: Group selection*]<User has selected "My Friends">
(optional) Also allow members of:
[Dropdown: Group selection*]<User has selected "Local Gaming People">
(optional) Also allow members of:
[Dropdown: Group selection*] <Currently "-">
Of course there are probably better ways to do it, such as listing ALL the users groups, and placing a checkbox next to each one.
Example F: Implemented using all checkboxes
Restrict table to
[-] My Friends
Also allow people in these groups:
[-] ACME Inc
[-] Local Gaming Peeps
[-] Example Group #3
[-] Example Group #4
.... etc ....