I filed a support ticket and they basically said that it was working as intended, which is stupid because it says one thing but does another completely different thing. This caused one said user to assign themselves every role they could and create havoc to the point where I had to kick said user in order to reset their roles and fix everything. In the attached image( ), you can see that the 'Jakku' role is at the bottom, however when we toggle the Manage Roles permission on that role, said users were able to assign themselves roles 40+ roles above the 'Jakku' role. The permission clearly states that the user can create new roles and edit/delete roles BELOW THE CURRENT ROLE. We recently gave one of our users a role at the bottom of the list and toggled the 'Manage Roles' permission within said role. On a server I help administrate, we have 50+ roles. Because of this granting this role to any user or bot should be done with the utmost caution and on an as-needed basis. It will add the role to EVERY channel in the server.This is not the same as the "Advanced Manage Roles Permission" post below, as that one talks about splitting up the permission into other roles. The Administrator permission is a special permission on a Discord role in that it grants every Discord permission and allows users with that permission to bypass all channel-specific permissions. Note: Whenever you change a setting on a role you need to click. The first parameter is the target of the overwrite, either a Role or User object (or its respective resolvable), and the second is a PermissionOverwriteOptions object. Check if the role is added to every channel. Before understanding how Discord’s roles and permissions work, we need to explain what they are and why they are important. This is the omega role Giving this role to a user grants them all of the permissions in the permissions list They also cannot be locked out of any voice or text channel, regardless of permissions. To add a permission overwrite for a role or guild member, you access the channel's PermissionOverwriteManager and use the. for this just use perms str (.changenickname) Please use code blocks when writing code to make it easier for the OP to understand. You'll see both of these changes reflected in the Channel Permissions screen. Also, specifically adds an exception for the role (s) selected. First, denies the everyone role the 'read messages' permission to this new channel, making it inaccessible and invisible to them. ViewChannel:PermValue.Allow, readMessageHistory: PermValue.Allow) When you are sending the command into a channel, You need it to be a string and change nickname also isn't a method. Selecting a role does two things in the permissions menu: 1. OverwritePermissions.DenyAll(channel).Modify( "MuteRole", ,ĭ/*what ever color*/,false,nullįoreach (var channel in )Īwait channel.AddPermissionOverwriteAsync(mRole, if the roles doesnt exist u create it and set the perms of the channels Here the longer version: bool rExist=false įoreach(var gRole in ) Here is a shorter version: foreach (var channel in )Īwait channel.AddPermissionOverwriteAsync(role, OverwritePermissions.DenyAll(channel).Modify(viewChannel: PermValue.Allow, readMessageHistory: PermValue.Allow. Var role = await ("Muted", m圜ustomPermissions) Var m圜ustomPermissions = new GuildPermissions(false, Here is some example code: public void CreateRoleWithCustomPermissions() When making a new GuildPermissions instance, you will need to use the constructor that takes in around 20 parameters which all set a different permission. The CreateRoleAsync function has a GuildPermissions parameter (which is the 2nd parameter) which you can pass a custom GuildPermissions object into. The Permissions property in IRole only has a getter, meaning that you cannot set the Permissions objects or any of the properties within the Permissions object once it's been created.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |