Feature Request: Don't act on users with a role named "RoVer Bypass" about rover

[evaera]

@SignallerRBLX I believe you can achieve this by creating a "RoVer Bypass" role that's just above the "RoVer" role hierarchically, then RoVer shouldn't be able to change their roles. If this isn't the current behavior (it may only work with nicknames...) then I'll add it in manually

[SignallerRBLX]

@evaera Problem is that role is being used for a rank so people can automatically get it. The person who I assign the role manually, does not have enough group space to join the side group so it will keep taking it away.

[suufi]

@SignallerRBLX 👀 That's why she said create a role called RoVer Bypass that's above RoVer. When you give the person the role you want to manually give, also give them RoVer Bypass.

[SignallerRBLX]

@suufi Does not work, thought I inferred that.

[suufi]

Try making the role itself you're giving higher than `RoVer`.

…

On 7 November 2017 at 12:11, SignallerRBLX ***@***.***> wrote: @suufi <https://github.com/suufi> Does not work, that's why I explained it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMKxJBcODxi03INdljZio8KI7PErm01vks5s0I9JgaJpZM4QQMG1> .

[SignallerRBLX]

@suufi Then the bot cannot give the role out to others.

[evaera]

If I add a special case for users with a roll called "RoVer Bypass" to be ignored, it will ignore them entirely, meaning they won't get verified. Maybe it would make more sense to only make it bypass group bindings. That distinction doesn't seem intuitive for server owners though.