When I attempt to add a ROLE that is BELOW my HIGHEST ROLE to a member who is HIGHER than me in the hierarchy, it simply won't add the role.
What I expected to happen instead is that this LOWER TIERED ROLE would be applied to the member, just like you can do on Discord.
Steps to reproduce
Create a community.
Create 2 roles, of which one has ADMINISTRATOR and is higher than the other role.
Give this admin role to an alt account.
Give the admin role to the community owner as well.
Attempt to give the LOWER role to the community owner via the alt account.
Do not use custom hoist order, that's not the order that matters for this issue.
While my video shows me trying this on a BOT, you can try this on the community owner as well which I did prior to submission and the same issue remains.
Status changed from Fixed to Awaiting confirmationStatusFixed→Awaiting confirmation
This was closed in a bulk cleanup before Fluxer V2 without being checked or fixed. It may work now, so it is waiting for someone to confirm whether the bug still happens.
Is that not how it's supposed to work..?
(edit)
I think Discord's behavior doesn't make much sense, this makes sense. Why would the owner (or members of a higher role) let members below them in the hierarchy give them roles? (edit 2: what i mean is, Fluxer just works differently and personally i think Fluxer took the logical approach)
Maybe there's a use case for that, if that's the case then I suggest Fluxer devs just add like a toggle or something to enable that, per role.
RexSystem1 voteoriginally by @Juliaxe on GitHub OP
No, that is not how it's supposed to work (unless Hampus confirms otherwise). For example, what about having a bot below you that wants to manage cosmetic roles you have where the cosmetic roles are below the bot's highest role?
Yeah but it's the roles you have and you're above the bot
Again this is just for me, but it doesn't make sense to me that someone hierarchically inferior to me would be able to manage my roles.
For example color roles. Color roles are below everything else and members with a "Colorperson" role, which has perms, can assign them. But I'm above the Colorperson role. While yes, the color roles are below both of us, should they be able to just... go and change my color, even though I'm hierarchically above them?
(edit) Maybe I'm misunderstanding and the example I gave wouldn't happen?
Either can be the bug. Either the UI or the actual role assigning. Which one is the actual bug depends on their design choice. So both of you are right there. Cause it depends how the person talking wants it to work decides which of the two is the bug for them.
I agree with JuxGD myself. Someone below you should not be able to adjust your roles if you are higher. As for your bot example. That is easy to solve by having the required bot being higher on the list. for example:
Owner
Admin
Bot
Mod
Users
Red
blue
Yellow
The bot can assign it to any users, mods and color roles (assuming here mods can't assign roles else the mods could be above the bot as well). And the other 3 can do it themselves. So there is no reason in that case for someone lower to be able to assign it to someone higher?
The bot is basically to give people functionality they normally wouldn't have to them. You dont want users to be able to update roles. So you don't give them that permission. Then have a higher role that does have that functionality and give a controlled option (bot commands) for them to use. If you want a bot that does something an admin shouldn't be able to do normally. You would put the bot above admin and make the functionality available through the bot.
Not make it so a Mod can suddenly adjust things on an admin. Just because the cosmetic is on a lower role for both.
(and yes I know discord allows it. Doesn't mean a new project needs to follow that same design choice)
6 comments
Comment by Rex
Comment by @JuxGD
Comment by @JuxGD
Comment by @Juliaxe
Comment by @JuxGD
Comment by @Kanda
- Owner
- Admin
- Bot
- Mod
- Users
- Red
- blue
- Yellow
The bot can assign it to any users, mods and color roles (assuming here mods can't assign roles else the mods could be above the bot as well). And the other 3 can do it themselves. So there is no reason in that case for someone lower to be able to assign it to someone higher? The bot is basically to give people functionality they normally wouldn't have to them. You dont want users to be able to update roles. So you don't give them that permission. Then have a higher role that does have that functionality and give a controlled option (bot commands) for them to use. If you want a bot that does something an admin shouldn't be able to do normally. You would put the bot above admin and make the functionality available through the bot. Not make it so a Mod can suddenly adjust things on an admin. Just because the cosmetic is on a lower role for both. (and yes I know discord allows it. Doesn't mean a new project needs to follow that same design choice)