When the server whitelist is enabled, people who got into the server in time should be kicked. It does not seem reasonable to want to enable whitelist without kicking everyone already online not in the whitelist.
This changes behaviour and may be appropriate in major.next.
We already depend on this current behavior that prevent more players from
joining without kicking everyone, especially when we're whitelisting the
server in the middle of the day to host "last man standing" games/events.
I suppose there should be an optional Boolean toggle /whitelist on
[kick=false] to kick existing non-whitelisted players if this were to be
implemented?
On Fri, Oct 9, 2020, 16:35 Chan Kwan Yin notifications@github.com wrote:
When the server whitelist is enabled, people who got into the server in
time should be kicked. It does not seem reasonable to want to enable
whitelist without kicking everyone already online not in the whitelist.This changes behaviour and may be appropriate in major.next.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pmmp/PocketMine-MP/issues/3868, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEHQQFF7PALQRCAQP7VKPWDSJ3DOVANCNFSM4SJY7VLA
.
If we add toggles for this, nobody will use them and it'll still be a circus of users asking why players don't go away when using /whitelist. You should implement your own logic instead of depending on the built-in whitelist.
no
Most helpful comment
We already depend on this current behavior that prevent more players from
joining without kicking everyone, especially when we're whitelisting the
server in the middle of the day to host "last man standing" games/events.
I suppose there should be an optional Boolean toggle
/whitelist on [kick=false]to kick existing non-whitelisted players if this were to beimplemented?
On Fri, Oct 9, 2020, 16:35 Chan Kwan Yin notifications@github.com wrote: