Getting Started with Mewdeko - Setting up the permissions system

Описание: In this video I will show you how to use mewdekos permissions system.

Website: https://mewdeko.tech
Discord:   / discord  

Transcript:

Hi and welcome to another Mewdeko Tutorial!

In this video i will be discussing how to setup the permissions module on mewdeko.

So you just invited mewdeko, and want to set some rules on who can use the bot and where. Before we do that, there a few basic things to know about the permissions system:

There are 2 permissions systems, one can change the actual permissions required to run a command (such as say requiring manage messages) and one that can set whether a user/role can use it in a channel/category.

For the second permissions system, the permissions stack. So if you set one permission then added another, the one you just added takes priority.

With that out of the way, lets begin. First off lets get the simple permissions system out of the way. The first permissions system works as follows:

Run .dpo say for example, along with the permission you want to require, so lets say we want say to use the banmembers permission, we do .dpo say banmembers, now if we look at .h say, the permission required has been updated, and the regular permission is crossed out. If you want multiple permissions you can do for example .dpo say managemessages banmembers. Now to change the command back to default, just run .dpo with the command name, without specifying any other permissions. SO now let me return .say back to its default permissions by doing .dpo say, and its back to normal! If you want to list every command that has a different permission setup, you can use .dpol, itll spit out a list of commands that had their permissions changed. If you want to reset all commands back to their default, you can do .dpor. And before I forget, do note that the permissions also apply to the slash command versions of the command you update. Pretty neat eh?

Now, lets get to the second permissions system, but first we need to review the commands.

We have:
acamd: Enables/Disables all modules in a category
acm: Enables/Disables all modules in a channel
arm: Enables/Disables all modules for a role
asm: Enables/Disables all modules in this server
aum: Enables/Disables all modules for a user/role
cac: Enables/Disables a command for a category (By the way category means the things that text channels are under)
cam: Enables/Disables a module for a category
cc: Enables/Disables a command for a channel
cm: Enables/Disables a module for a channel
lp: Lists your current set perms
mp: Lets you move a perm above/below another
permrole: Lets you set a role that can adjust perms without needing admin
rp : Removes a perm using its number
resetperms: Always works regardless of perms in case you massively fuck something up
rc: Enables/Disables a command for a role
rm: Enables/Disables a module for a role
sc: Enables/Disables a command for the entire server
sm: Enables/Disables a module for the entire server
uc: Enables/Disables a user to use a certain command
um: Enables/Disables a user to use a certain module
v: Toggles whether you get permission errors when someone cant run something

Some things to note:

As said before, resetperms can be used to reset all perms in case you fuck something up
If you are trying to allow a user to be able to use a command using uc when they dont have proper perms, it wont work. You need to disable it for the server, set its perms to sendmessages using dpo, then you can use uc/rc to enable it for the role/user without them needing the actual perms.


Now, a few demonstrations:

Say we dont want anyone to use the nsfw module in the server even though we have an nsfw channel. We can simply do .sm nsfw disable and it disables it for the entire server. Now, you're going to see a red error saying you cant use commands in this module because of so and so permission number, this prompt can be disabled with .v

Or what if we have a user that is spamming a command nonstop after being told to stop? We simply do .uc say (as an example) disable user, now the same works for roles but you can use the id for a user to avoid pinging them, as well as the username.

As of a new update, we added an entirely new way to edit permissions that is much more finger friendly and doesnt end up adding 2 thousand characters to your daily word count. An admin can do .h say (yes i keep using say as an example), then they can click the manage permissions button which takes them to this little menu here. This menu can be used to configure both the first and second permissions system, thanks to my codev, cottagedwellingcat for making this awesome addition!