This is not a issue. More of a question of understanding. #137
Comments
|
Seems like |
Ah that's a shame that it's broken. |
|
Unfortunately it's a relic of an old version of guidebot, we intended to implement this feature but we didn't know HOW to do it, it's remained in the code for the hopeful time we do add the functionality. |
|
If you need support for this issue, you can drop by the server (link is at the top of the org page) for a more speedy support than here @KainesLaw. Bah... stupid me... I shouldn't read/code first thing in the morning... disregard what I said LOL complete misunderstanding on my behalf... I'll certainly be looking into this a.s.a.p. now that I understand the issue at hand. |
|
This has been fixed in the v13 update, which can be backported to v12. |
* Initial update to v13 Updated everything * Update guildCreate.js updated from `user.id` to `ownerId` * V13 Setup.JS fix + reboot.JS command update (#139) * Adding partials to update baseConfig * Adding logical "restart" alias * Updated commands. Updated all the commands that output codeblocks, used the new formatters. * Thread support Added a single line of code to make Guidebot auto-join any threads created, useful for moderation bots. * Guidebot will now ignore disabled commands Fix #137 * Updating invite link * Removed unused dep * Slash Commands (#143) * Slash Commands Added slash command support to the original (main) version of guidebot. Updated discord.js to version 13.0.1, updated the throw in the index to require version 16 of nodejs. Brought both versions of guidebot to the same functional level. * Fixed a small mistake The setup placed the partial array inside an array causing an error. * Minor update Updated the readme to be concise with the other version. Updated the setup script, removed the deprecated ownerId field. * Consistency fix The prefix for the bot in two files were different compared to the one in the set up script. Fixed for consistency. * The real quick fix Actually fixed the damn thing this time.
So when I change a command setting to
enabled: truetoenabled: false, I still can use the command. Or do I bypass it since I am the owner?Sorry for the trouble. I am new to having all these new features in command handlers.
The text was updated successfully, but these errors were encountered: