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

💡 Allow the choice of autothreading on only messages from a certain user, bot, or role #61

Closed
DMFriends opened this issue Feb 3, 2022 · 12 comments
Labels
improvement 💡 Improvement suggestion

Comments

@DMFriends
Copy link

DMFriends commented Feb 3, 2022

Describe the solution you'd like
I think it would be nice to be able to choose which user or bot in my server to automatically create threads on.

@DMFriends DMFriends added the improvement 💡 Improvement suggestion label Feb 3, 2022
@MarcusOtter
Copy link
Owner

MarcusOtter commented Feb 3, 2022

I think this would be pretty cool, we could add a mentionable parameter to /configure auto-threading so one could pick a certain role or user.

@ririko5834
Copy link

Yes that threads will be created just from messages from some user/role. This should also allow that threads will be made from bot's messages.

@DMFriends
Copy link
Author

DMFriends commented Feb 4, 2022

Yes that threads will be created just from messages from some user/role. This should also allow that threads will be made from bot's messages.

That's exactly what I was going for. Roles could actually be cool too, in addition to regular users and bots.

@MarcusOtter MarcusOtter changed the title 💡 Improvement: Allow the choice of autothreading on only messages from a certain user or bot 💡 Allow the choice of autothreading on only messages from a certain user or bot Feb 6, 2022
@DMFriends
Copy link
Author

DMFriends commented Feb 7, 2022

@MarcusOtter Just wanted to mention that the include-bots parameter would probably not be needed if we were to implement this.

Also, in case it isn't clear: I don't know TypeScript very well, but I looked at the configure.ts and configHelpers.ts files, and I have a rough idea of what we would need to do to implement this, but again, I don't know TypeScript well, so I was hoping you would be able to implement this yourself. Thanks again!

@MarcusOtter MarcusOtter added the good first issue 💚 Good for new contributors label Feb 8, 2022
@DMFriends DMFriends changed the title 💡 Allow the choice of autothreading on only messages from a certain user or bot 💡 Allow the choice of autothreading on only messages from a certain user, bot, or role Feb 8, 2022
@DMFriends
Copy link
Author

@MarcusOtter Any updates on this? (Not urgent, just wondering where you're at with this.)

@MarcusOtter
Copy link
Owner

I've had a fever for a week but still think this is a good idea :)
It's not of the top of my priorities in this project (and this project is not my top priority among my projects) but I'll happily start looking at it after #60

@DMFriends
Copy link
Author

I've had a fever for a week but still think this is a good idea :) It's not of the top of my priorities in this project (and this project is not my top priority among my projects) but I'll happily start looking at it after #60

Oh, that's too bad, hope you are well now :)
That's totally fine, again not urgent. Thanks!

@RenidJBS
Copy link

RenidJBS commented Mar 3, 2022

This is exactly what I need for my discord server as well. If it could thread in one channel based on mentions and allow bots, this would be perfect! I have YAGPDB reacting to specific mentions, but I need it to create a thread and it’s unable to. Yours would fill that gap! Very excited for this feature!

@DMFriends
Copy link
Author

Hey @MarcusOtter , looks like #60 is done, have you started working on this? (No worries if you haven't.)

@MarcusOtter
Copy link
Owner

No updates on this right now, but it might be closed in favor of #93 in the future as that would cover more use cases (including this one)

@DMFriends
Copy link
Author

No updates on this right now, but it might be closed in favor of #93 in the future as that would cover more use cases (including this one)

I see, thanks!

@MarcusOtter MarcusOtter removed the good first issue 💚 Good for new contributors label Aug 31, 2022
@MarcusOtter
Copy link
Owner

Closing in favor of #93 which will accomplish the same thing

@MarcusOtter MarcusOtter closed this as not planned Won't fix, can't repro, duplicate, stale Aug 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement 💡 Improvement suggestion
Projects
None yet
Development

No branches or pull requests

4 participants