add channel logging

[jbasalone]

Feature Description

Ability to set preference in each command file on a channel to log command usage and an embed template

Problem and Motivation

I have to add a line to each command if I want it logged to a discord channel that the command was ran. I attached a sample.

Additional Context

Add any other context or screenshots about the feature request here. If this feature is inspired by something else, please provide references.

[lukazbaum]

Do you mean a channel Id argument that will send an embed to the specified channel as a notification when the command is executed?

[jbasalone]

yes yes

[lukazbaum]

(still working on the new version but it will take a while.)

[jbasalone]

the other thing I was thinking would be cool is to have a master config list for commands and allowed servers/channels etc.

Like a YAML file or something. Would maybe have to implement some way of tracking the command with an id or something.

Guild -
|_command-id
|__channelwhitelist:

[lukazbaum]

Like this?:

guilds:
  - guild_id: 123456789012345678
    commands:
      - command_name: "ban" # Maybe id instead of name
        channel_whitelist:
          - 987654321098765432
          - 876543210987654321
      - command_name: "kick"
        channel_whitelist:
          - 123456789098765432

[jbasalone]

OOO yes. Then I dont have to manage each individual command file

[lukazbaum]

Alright, I'll try to add this as a "plugin/addon" since it can get messy with large bots.

[lukazbaum]

Hello again. The new version will release in 1-2 weeks. I'm currently rethinking how to handle components like buttons, select menus and modals. I find the current approach a bit confusing and not suitable for all use cases.

Could you share what aspects of the current component handling you didn't like?
Additionally, if you have any suggestions or ideas for a more intuitive design, I would greatly appreciate it. ^^

And also, should the XML file just be a display, or would you like to manage stuff in there?

[jbasalone]

I thnk the button componets work fine. I havent started using the menu select but I want to very soon. I dont think I had issues with the button. I can let you know when I do the select menu if it is an issue.

Id like to manage it from the XML

[jbasalone]

actually I did remember one issue and that is handling collectors with buttons. Like here is one area it gets a little confusing. We have in the export
type: ComponentTypes.Button,

But it gets called twice if I use a collector

   const collector = reply.createMessageComponentCollector({
                ComponentType: ComponentTypes.Button,
                filter,
            });

But thats only if I use a collector and not just a singular action for a button click

[jbasalone]

oh and buttons if I use pagination dont work as components

[lukazbaum]

Okay I'll find a solution for this. Thanks for your feedback :)

[jbasalone]

One thing would be nice if I could load the button modules by choice. So if I specify buttons in the chat.ts file, then I dont get errors that components are matching because they are not specified in the button folder.