Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Topic or frequency-based Help Thread Auto-Add #77

Open
DenverCoder1 opened this issue Mar 11, 2022 · 2 comments
Open

Suggestion: Topic or frequency-based Help Thread Auto-Add #77

DenverCoder1 opened this issue Mar 11, 2022 · 2 comments

Comments

@DenverCoder1
Copy link
Contributor

The amount of threads created on Nextcord has become pretty high such that it can be annoying to get pinged in every single one.

Here are few potential solutions I have thought of:

Solution 1: Category-based Auto-Add Roles

Instead of only having an all-encompassing "Help Thread Auto-Add" role, in addition to that, there could be self-assignable roles for specific types of help (eg. Slash Command Auto-Add, Ext-Menus Auto-Add, etc. When a user creates a help thread, they could choose the closest fitting topic(s) from a select menu to categorize their thread.

Solution 2: Keyword-based Auto-Add

In addition to pinging the Help Thread Auto-Add role when the thread is opened, the bot can allow users to sign up for pings when specific keywords are mentioned in Help Threads. For example, if one were only interested in helping with ext-menus and slash, they could use a command to tell Previous to ping them when the strings ext-menus, import menus, slash, or slash_command appears in a help thread.

Solution 3: Configurable Ping Frequency

Instead of being pinged in all threads, a user could be able to sign up to be pinged for only every 1 in 5 threads or 1 in 10 threads. The amount of users with this feature should be about evenly distributed across threads, so some threads don't get significantly fewer helpers than others. (r/translator on Reddit has a system like this)

@Skelmis
Copy link

Skelmis commented Mar 11, 2022

1

This would be nice, and can tie into the pr item discussed in 2

2

Once #74 is finished and merged, solution 2 will be viable as the pr will implement a dropdown with specific categories. Although this leaves it up to the user to pick the topic

3

Lol, no. Randomly assigning people implies everyone has the relevant skills, and imo will just be messy.

@ThePrivatePanda
Copy link
Contributor

ThePrivatePanda commented Apr 1, 2022

Considering #74 has been closed, Solution 1 appears to be the best option.

  1. I can imagine at least some person sending all such keywords to force ping the roles, as they already ping individuals and crosspost their thread in general.
    Also, imagine their imports having multiple keyword arguments, but they have a syntax error, pain.

1 ) As skelmis said, it does leave the topic to be chosen by the user, but it's greener grass than 2 and 3.

A possible flow would be,
user clicks Help button in the help channel ->
a modal appears asking for relevant code/error/traceback etc - this may contain a field of the topic ->
Thread is made, relevant role is mentioned.

The topic command remains as is for help mods/helpers for it's current purpose.

On an excess note, maybe help mods could ping a role through some a command, incase the topic changes, or the user selected the wrong topic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants