Conditional roles #6

New Issue

konradomen · 2022-08-10T01:41:04+02:00

myrkvi commented

2022-08-10 01:41:04 +02:00

(Migrated from github.com)

Roles that are added to or removed from users based on a certain condition.

In NLL, there's currently only one instance of this: The "in-voice" role which is given to users that are in a voice channel, giving access to the NSFW voice text channel.

Roles that are added to or removed from users based on a certain condition. > In NLL, there's currently only one instance of this: The "in-voice" role which is given to users that are in a voice channel, giving access to the NSFW voice text channel.

konradomen commented

2023-03-03 18:53:54 +01:00

Any idea how that should work?
Just listening for specific events to accure and adding roles then?

Any idea how that should work? Just listening for specific events to accure and adding roles then?

myrkvi commented

2023-03-04 00:04:12 +01:00

The bot would listen for events, then check against the database if it matches any criteria to assign or unassign a role.

On the admin side we would need commands for adding and removing criteria and their roles.

The bot would listen for events, then check against the database if it matches any criteria to assign or unassign a role. On the admin side we would need commands for adding and removing criteria and their roles.

konradomen commented

2023-03-04 15:14:51 +01:00

What format do you think? Some custom "language" for the rules?

myrkvi commented

2023-03-11 20:22:16 +01:00

Database-wise, I'd say one row per rule. Perhaps something like this

CREATE TABLE ConditionalRoles (
	id INTEGER PRIMARY KEY AUTOINCREMENT,
    guild_id INTEGER NOT NULL,
    condition_type VARCHAR(24) NOT NULL,
    condition_constraint TEXT,
);

condition_constraint will likely be some JSON data or similar?
Or we could do it the proper relational way and add another table for constraints :dogehehe:

Could be managed via commands. Could have different sub-commands if we add multiple types of conditions

Database-wise, I'd say one row per rule. Perhaps something like this ```sql CREATE TABLE ConditionalRoles ( id INTEGER PRIMARY KEY AUTOINCREMENT, guild_id INTEGER NOT NULL, condition_type VARCHAR(24) NOT NULL, condition_constraint TEXT, ); ``` `condition_constraint` will likely be some JSON data or similar? Or we could do it the proper relational way and add another table for constraints :dogehehe: Could be managed via commands. Could have different sub-commands if we add multiple types of conditions

konradomen commented

2023-03-11 22:40:37 +01:00

So sth like an enum of types and constraints as objects?

konradomen commented

2023-03-11 22:41:14 +01:00

I could read a bit more about different options. I can even make a graph database if that makes it any easier. 🤔

myrkvi commented

2023-03-13 14:56:23 +01:00

So sth like an enum of types and constraints as objects?

Yeah, something like that!

I could read a bit more about different options. I can even make a graph database if that makes it any easier. 🤔

I've been considering using SurrealDB :p

> So sth like an enum of types and constraints as objects? Yeah, something like that! > I could read a bit more about different options. I can even make a graph database if that makes it any easier. 🤔 I've been considering using SurrealDB :p

Sign in to join this conversation.