You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please elaborate.
Yes,
A while ago the bot notified the thread when a user left the server, without indicating the server he left, making confusion.
To fix it, the bot behavior is to indicate when the user left the current server. But when doing a Support server different from the main, we don't have this important log.
Having this old message indicating where he left/join would be useful and not confusing as before.
Describe the solution you'd like
When a user with a ticket opened leave/join any server in the bot jurisdiction, the bot will make a log in it, indicating the server name and if he can still talk to the user (making an update if there are a few servers left or if the bot can't reach the user to avoid any redaction of a message that can't be heard.)
Does your solution involve any of the following?
Logviewer
New config option
Describe alternatives you've considered
No,
The actual behavior is to make this log for the current server.
But the point of such log is not to track the user, but to know if we can contact him. Having the bot react that way is more logical and informative.
Who will this benefit?
Any server who use a different server to receive tickets or any bot who have multiples servers.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
The bot is not supposed to be in servers that aren’t configured. It even gives a warning when starting that other servers than configured are detected and potential errors might arise.
Sure,
We run this bot since years, and we never had an error nor any issues with it.
This is literally the only issue with multiserver capabilities. It would make the bot officially multiserver compatible.
While its not officially supposed to be, this is a configuration we have recommended publically for a few instances. Seems like this would be a good thing to implement.
Is your feature request related to a problem? Please elaborate.
Yes,
A while ago the bot notified the thread when a user left the server, without indicating the server he left, making confusion.
To fix it, the bot behavior is to indicate when the user left the current server. But when doing a Support server different from the main, we don't have this important log.
Having this old message indicating where he left/join would be useful and not confusing as before.
Describe the solution you'd like
When a user with a ticket opened leave/join any server in the bot jurisdiction, the bot will make a log in it, indicating the server name and if he can still talk to the user (making an update if there are a few servers left or if the bot can't reach the user to avoid any redaction of a message that can't be heard.)
Does your solution involve any of the following?
Describe alternatives you've considered
No,
The actual behavior is to make this log for the current server.
But the point of such log is not to track the user, but to know if we can contact him. Having the bot react that way is more logical and informative.
Who will this benefit?
Any server who use a different server to receive tickets or any bot who have multiples servers.
Additional Information
No response
The text was updated successfully, but these errors were encountered: