You are not eligible for roles from that message дискорд

Discord Roles Not Working: 2 Ways To Fix

One of the many great features associated with Discord that make it such a great and favored application for chatting with people is the role system. This role system is pretty self-explanatory thanks to its name. It allows mods of a server to assign a specific role to each and every single person.

Upon further settings, these roles determine what the exact permissions of every person in a group is depending on their role. While the feature is quite great, it isn’t of much help to anybody at all if it doesn’t work. Here’s what you can do if you aren’t able to get the role system to work.

How to Fix Discord Roles Not Working?

Discord’s role feature is only used to decide which role every single person in the group has. This role then allows mods to make it much easier to manage their servers. But the only thing that might be going wrong in your case is that you haven’t set up the permissions for each role.

As mentioned above, further settings are required to determine the permissions of each role. If these permissions aren’t set, everyone will be able to do the same things on a server regardless of their role. This could be happening in your server right now which is why you might be thinking that the role system isn’t working.

What to do next is pretty obvious. You have to go into the Discord settings and determine the permissions for every role you wish to assign. Once all these permissions have been set to your liking, reassign the roles of every member of the server. Now the roles that you set should be working the way that you originally intended them to work.

The next most important course of action is to check the roles that you’ve assigned to the people inside your server. Roles are meant to differentiate between all the members and give them all their specific permissions and even their duties.

If everyone has the exact same role assigned to them, there isn’t really much of a point in using the feature at all. That’s because everyone will have the same permissions and you won’t find any differences from usual.

That being said, if you’re using the role feature in your group but can’t see any differences, it’s likely because you’ve assigned a similar role for every user. Double-check the roles and make sure they aren’t the same for everyone. If they are, simply change them to exactly how you wish for them to be.

Conclusion

This problem isn’t exactly common and Discord itself isn’t really responsible for the issue, as it is likely a problem with the way you’ve set up the feature. Try both of the solutions given above and one of them should definitely be able to help you get the Discord roles feature working again.

How to know which rights my roles on a discord server have?

For example, how do I know if my @everyone or @here in a discord channel is actually annoying people, even if the server doesn’t have emotes especially designed to be used to express this sort of discontent?

Or any of the other rights you can assign to certain roles in the «Roles» management tab inside the «Server Settings» of a server without being the admin and being able to open these settings?

Also, from the flip side, how can I acquire which roles may be eligible for a certain action I want to take on a server, for example joining a channel, without being a moderator with insights into the management system?

2 Answers 2

@here notifies all non-idle users currently online

@everyone notifies all users, even if they are offline

. both are global by default so yeah it’s annoying people if overused. Server owners can enable or disable the option for specific user roles in their server settings. To set permissions on a server:

click the small arrow next to the server name.

open Server Settings

then click a role to customize that role’s permissions

Mentioning roles

When mentioning a role, every user that has access to the channel will get a notification and the channel will be highlighted as if mentioned directly. To allow a role to be mentioned by anyone, enable it for that role under Server settings > Roles > Allow anyone to @mention this role. Many server owners like to enable this for a short time when wanting to mention all users of a role once and then disable it again when making announcements to a specific role.

I wasn’t sure a user actually could view their Roles on a server, but I found it in Discord’s user list.

Note: The roles displayed looked like self-identified roles only. If the server has other roles and they have selected the option for «Display role members separately from online members», you can check the Member List for your main role. You can always assume your just an «everyone», but if you’re not, then there doesn’t seem to be any way to find those hidden roles. This is probably because Moderators might need hidden roles to keep track of antisocial behavior. You also might be able to ask the Moderator Bot what your roles are.

403 Forbidden (error code: 50001): Missing Access when adding role | discord.py

I am trying to ass different roles to people rapidly to give users the impression of their name being rainbow ( yes I know its against TOS ), and I am starting by adding roles to people before I remove them. However, when adding roles I get the error in the title of this post. I have looked into this and tried quite a few ways to fix it. The bot has a higher role than the roles being give out. Here is my code and the output:

3 Answers 3

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

Best practice for verified bots is to make a role called BOT with all the permissions and give it to all the bots you have in the server

I’m just leaving this for any others struggling with this b/c I spent 3 days trying to debug a 50001 error and found nothing and this thread comes up as one of the first on google.

Apparently, if the Discord server your Bot / integration mandates multi-factor authentication, the developer account associated with your Bot MUST have MFA enabled. I enabled it on my discord developer account, and the 50001 errors immediately resolved.

Please please please please check twice that in your bot, you really use the correct:

In my case, I was using a token from a different bot on the same server. After changing the token to the correct token, everything worked.

Morale of the story is: always check the dumbest and simplest things first!

MANAGE_ROLES/MANAGE_PERMISSIONS does not implicitly grant MANAGE_MESSAGE #487

Comments

napstr commented Jan 19, 2018 •

Hi,
the docs say

Permissions in Discord are sometimes implicitly denied or allowed based on logical use.

According my understanding a user that may manage roles/permissions, can end up giving themselves the permissions to manage messages, so that permission should be granted implicitly. However, in reality, it is not.
Informally, this was verified with a chat with Jake/binzy (sorry I don’t remember who exactly it was anymore, and can’t find it in DAPI anymore :^) ) that this is indeed the desired behavior. It has now been almost 6 months and the behavior has not been changed, so I’m opening the issue here, to make this a bit more formal. JDA already supports this behavior, which leads to 50013s unless a ton of explicit checks are done. They basically said they do not intend to change the behavior as long as there is no official stance that this implicit permission grant is wrong.
Please let us know what the plans are with regards to this issue, so this discrepancy can be resolved soon.

The text was updated successfully, but these errors were encountered:

z64 commented Jan 19, 2018

a user that may manage roles/permissions, can end up giving themselves the permissions to manage messages, so that permission should be granted implicitly.

Please correct me if I’m misunderstanding, but you’re saying that a person with Manage Roles can and needs to explicitly grant themselves Manage Messages in order to do so, so everyone with Manage Roles should just always have Manage Messages because they might grant it to themselves? I’m not sure I see the problem, as it’s so much easier to check for explicit permissions granted in the permissions bits than it is to figure out implicit permissions.

Furthermore, as a bot, if your library were to assume that just because you have Manage Roles that it has Manage Messages, that would lead to further errors, unless it were to do something like catch the exception and grant itself permission and retry (which, would be awful)

Permissions in Discord are sometimes implicitly denied or allowed based on logical use

napstr commented Jan 19, 2018

Please correct me if I’m misunderstanding, but you’re saying that a person with Manage Roles can and needs to explicitly grant themselves Manage Messages in order to do so, so everyone with Manage Roles should just always have Manage Messages because they might grant it to themselves?

Yes. A user with Manage Roles permissions can create a permission override for themselves or anyone else or any role, giving them Manage Messages (interestingly, they cannot create or edit a role granting Manage Messages).

I’m not sure I see the problem, as it’s so much easier to check for explicit permissions granted in the permissions bits than it is to figure out implicit permissions.

That’s not really the point. The point is that there appears to not be a clear documentation of whether Manage Messages should be implicit to Manage Roles, or not. There are other implicit permissions already.

Furthermore, as a bot, if your library were to assume that just because you have Manage Roles that it has Manage Messages, that would lead to further errors

That’s exactly what’s been happening for at least the past 6 months in the JDA lib.

I don’t really care whether there is a logical connection or not (I think there is, but I’m fine with any decision by the developers, as long as they make an official one and follow through with it), I just want the lib and Discord to agree to treat this similarly.

TypeError: message.member.roles.some is not a function

What do I need to change? for it to work?

the error is if (message.member.roles.some(role => role.name === ‘Red’)) return message.channel.send(`You already has that role `) TypeError: message.member.roles.some is not a function

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

I am assuming you are using discord.js v12 and that’s why your code won’t work.

Try using message.member.roles.cache.some(role => role.name === ‘Red’) instead of message.member.roles.some(role => role.name === ‘Red’)

It seems that message.member is undefined, you might want to check if this is done in a guild or not. If it is in a guild it will return the member property, while if it isn’t, it won’t. What you want to do is check if the message was sent from a guild or not, try the code below:

Not the answer you’re looking for? Browse other questions tagged discord.js or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.