-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Multiple server compatibility #3245
Comments
This would literally require a complete rewrite of the entire bot. Best case this would take months, but more realistically seeing how often people are busy irl this would maybe take more like a year or 2 to rewrite and have this function. Just set up a second instance of modmail for your other server. |
This feature would remove the need to create another instance, which is really annoying and complicated. I‘ll gladly make PRs but I’m sure many other people would like to see this implemented. It makes the bot usable in almost as many servers as you want. Think about it, you can have one bot named “Support Bot” (or something) and use it in multiple servers with multiple modmail servers. The entire code wouldn’t have to be rewritten, only the basic stuff of the thread handler and how a thread is created. The guild ID where the thread was actually created, can be stored in the database. Then when the thread is fetched, you have the guild ID and the thread channel ID. |
This comment was marked as resolved.
This comment was marked as resolved.
The bot has to fetch a channel object and that channel object has an attribute |
My apologies, I missed the dropdown menu part in the first message, I'll mark my messages as resolved 👍 |
Update? |
@Nzii3 Nope. As sebkuip already told, it would require a nearly whole rewrite of the bot which would take much time. The bot is not designed for working with multiple guilds as inbox servers like you explained using dropdown etc. I guess this won´t ever be released. |
Is your feature request related to a problem? Please elaborate.
Please add the ability to have the modmail system worn across multiple servers. This could be achieved with a select menu that is sent (if multiple guild IDs are passed in the
.env
file) with a list of all the guilds by name, when a server is selected through the menu, it will fetch that guild as the modmail guild, then proceed with creating the thread as usual. The user would only be able to have 1 thread open at a time between all the servers, for obvious reasons.A dictionary could be stored in the database with a guild ID linking to a modmail category ID, for example:
Describe the solution you'd like
This would allow us to use multiple modmail servers, so you can share one modmail system with other users.
Does your solution involve any of the following?
Describe alternatives you've considered
Using one modmail server, but this isn’t an ideal solution because I’d like to have multiple servers that threads can be sent to.
Who will this benefit?
Users who want to use the bot across multiple servers with multiple modmail servers. This would decrease the hassle of having to create a new kyber modmail bot for each server we want to use this great system on.
Additional Information
I’ve created this type of thing in my own modmail bots, and I would like to see it in a widely-used and known modmail system.
The text was updated successfully, but these errors were encountered: