You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if gatekeeper is enabled for a room all joins from non-friends are blocked even if they have the correct password. There is no message about the block and from the would-be-joiners perspective it just appears that "nothing happens".
IMO having the gatekeeper allow friends passwordless access and still accept the distributed password from non-friends would be much more useful and less confusing.
Expected Behavior
Enabling gatekeeper allows friends joining without inputting the password, while not preventing those who are not friends but have the password from joining.
Screenshots
No response
Additional context
This is a chobby PR that I am not comfortable merging while gatekeeper operates in the current way, as it is confusing why a password is given which doesn't actually allow people to join: beyond-all-reason/BYAR-Chobby#665
The text was updated successfully, but these errors were encountered:
Describe the Feature
Currently if gatekeeper is enabled for a room all joins from non-friends are blocked even if they have the correct password. There is no message about the block and from the would-be-joiners perspective it just appears that "nothing happens".
IMO having the gatekeeper allow friends passwordless access and still accept the distributed password from non-friends would be much more useful and less confusing.
Expected Behavior
Enabling gatekeeper allows friends joining without inputting the password, while not preventing those who are not friends but have the password from joining.
Screenshots
No response
Additional context
This is a chobby PR that I am not comfortable merging while gatekeeper operates in the current way, as it is confusing why a password is given which doesn't actually allow people to join: beyond-all-reason/BYAR-Chobby#665
The text was updated successfully, but these errors were encountered: