-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
2 requests in one ask: Multiple servers support. Multiple command characters support. #232
Comments
Would being able to DM commands to the bots be sufficient? Its probably the easiest solution that doesnt involve a very convoluted configuration? I'll look into the ability to DM the bots. Multiple server support was being worked on, but the person who was looking at it gave up. I can try revive their effort, but realistically, I dont have much time to spend on this project, so its unlikely to be completed. |
See v3.11, allows DM'ing the bot directly. With that, you can have your bots on the same channel, and send commands to all bots, or use DM for individual commands. I will think about the multiple channels thing, but I cant promise any kind of prompt fix for that |
That could work nicely. My only thought is, I have 3 printers and want to
keep tabs on them all.
I'd like to extend a great thank you for developing a great, seriously
useful plugin.
Dr. Toxic
…On Wed, 4 Jan 2023, 01:57 Cameron, ***@***.***> wrote:
Would being able to DM commands to the bots be sufficient? Its probably
the easiest solution that doesnt involve a very convoluted configuration?
I'll look into the ability to DM the bots.
—
Reply to this email directly, view it on GitHub
<#232 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKAAR3DX4RJOFQAYTKXUR5LWQTKH3ANCNFSM6AAAAAATPNUEQ4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Amazing stuff.
I will take a look at the source and see if I can't work anything out. I just happen to be busy as heck at the moment. :( |
I had made an attempt at making it work for multiple channels, but it requires a bit of an overhaul to only send some responses to one channel (otherwise there are out of context responses in other channels), or to show who ran what command where in the response. I also no longer needed to have it run in multiple channels, though I could try and continue working on this feature if people want it. |
Would it be possible to have the command responses go to the person that DM'd it or would that require adding extra channel IDs? I DM'd my bot the |
That shouldn't be too hard to do, and if you want to make that change I
will definitely merge it in.
Ideally would want to keep the existing "send to main channel" behaviour
though as someone may already be using that feature.
…On Mon, 3 Apr 2023, 4:02 am Aroymart, ***@***.***> wrote:
Would it be possible to have the command responses go to the person that
DM'd it or would that require adding extra channel IDs? I DM'd my bot the
snapshot command and it posted an image to the main channel it's present
in
—
Reply to this email directly, view it on GitHub
<#232 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAK7FL2TCUHVW5BB6BA4GTDW7G5M3ANCNFSM6AAAAAATPNUEQ4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Is your feature request related to a problem? Please describe.
Multiple Servers Support
I run bots on my discord. a friend of mine would like to use his bot on both mine and his servers, partly so I can watch and debug.
Multiple Command Characters Support
It'd be pretty dope to see all bots respond at the same time to trivial commands, like !Status, however it would be irritating to, for example, start all printers printing the same file.
So have each printer reacting to it's own command character (like it is now), but also assign a second character for trivial commands, such as /Status.
Describe alternatives you've considered
Running multiple plugin instances, setting up multiple bots per printer.
Additional context
The text was updated successfully, but these errors were encountered: