You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Let's say there may be aliases that run commands that aren't meant for lower tier staff members such as the support team but are intended for moderators. The problem is, an alias is just a shortcut to run a string of commands, and I'm pretty sure those bypass permissions.
Describe the solution you'd like
It would be nice to set permissions of some kind (like how you can define certain commands to belong to a certain level) that allows for an alias to be defined to a specific permissions level. For example, a level 3 alias would send a message to the user to let them know that they've abused modmail, block them for 3 days, then close their thread silently. A supporter or lower will obviously not be able to run this, if permissions were defined at the alias level.
Describe alternatives you've considered
Short of running each command separately (which respects permission levels) it's not ideal if you want to do it quickly.
Who will this benefit
This will benefit anyone who may wish to have more granular control over who can run what alias
Additional context
n/a
The text was updated successfully, but these errors were encountered:
A general comment is, they don't bypass permissions, they use the permission the command they are imitating has, for example, eval is level 5, so level 5 is also applied if you had ?e as ?eval. And from what I've heard, permissions in aliases are not likely to come, the amount of effort and reworking isn't worth it in the long run.
As @StephenDaDev said, this already exists in some form. Perms of the command to be executed are already taken into account. The ability for custom alias permlevels will remain as a feature request though
Is your feature request related to a problem? Please describe.
Let's say there may be aliases that run commands that aren't meant for lower tier staff members such as the support team but are intended for moderators. The problem is, an alias is just a shortcut to run a string of commands, and I'm pretty sure those bypass permissions.
Describe the solution you'd like
It would be nice to set permissions of some kind (like how you can define certain commands to belong to a certain level) that allows for an alias to be defined to a specific permissions level. For example, a level 3 alias would send a message to the user to let them know that they've abused modmail, block them for 3 days, then close their thread silently. A supporter or lower will obviously not be able to run this, if permissions were defined at the alias level.
Describe alternatives you've considered
Short of running each command separately (which respects permission levels) it's not ideal if you want to do it quickly.
Who will this benefit
This will benefit anyone who may wish to have more granular control over who can run what alias
Additional context
n/a
The text was updated successfully, but these errors were encountered: