search

GreyWolfDev / Executrix

Here you can address issues or feature requests for @ExecutrixBot on Telegram. There is no code, Executrix is closed source at this moment.
2 stars 0 forks source link

Make a more versatile elevate system #59

Open kommandantredundant opened 4 years ago

kommandantredundant commented 4 years ago

With discord's roles system as a model, extend the bots elevate system to have different levels of elevation. Add a /menu point to define, which lvl can do which actions, eg. warns only, no bans, etc. There could be either an option to add a new level or a predefined set of x levels, that can be edited.

OlgabrezelPrivate commented 4 years ago

Ugh. I see few usecases for this in contrast to a high efford it would take to code... Is it really needed?

kommandantredundant commented 4 years ago

Is it really needed?

What's ever really needed? As an admin I would like to have more options at assigning competences throughout my team. Starting with a small role that can warn endlessly without banning and solving issues for new admins that I'm giving a "trial period" to see how they do. Then there could be roles that can do all those mostoccuring admin jobs and maybe already configure some minor settings of the bot. Up to someone who can do anything a full admin can do (including fully configuring the bot), but not having to set them as group admin as that might give them permissions on other bots that I want to keep closed.

OlgabrezelPrivate commented 4 years ago

@kommandantredundant I doubt anyone besides you really has so many different persons that should have different rights.

I am completely against the infinite warning thing - it totally misses the point of a warning. If you have 2 out of 4 warns, that means you are halfway banned (or tempbanned or whatever). If you give a warning without any practical impact, you could just do nothing at all. I mean, what is the difference whether your low-permission-admin gives the final warning and tells a high-permission-admin to review it in contrast to just telling the high-permission-admin to ban the user?

Other than that, having such a role system requires saving those different roles in the database and checking each time someone issues a command, as well as having a nice way to see all users and their respective roles, which is... just not worth it. I can sense how nobody will use that feature. Remember admin groups? Out of more than 25k groups that added Executrix, exactly 78 use an admin group. That is 0.3%. And they are something I would really consider useful for many groups, whereas this suggestion probably only applies to group owners who want a complete and individual control over who can do what. What elevateds are originally supposed to be is not admins that are blocked from other bots or admins that cannot access recent actions, but rather users from the group who temporarily get a banhammer in case of need.

As a compromise: What about a setting "ElevatedBanhammer" just like "AllAdminsBanhammer" that you can use for your kind of elevations?