deploying the slash commands and running the bot seems to want different things out of the settings.json about discord-tts-bot HOT 8 CLOSED

um. update on the issue, the slash commands are working completely fine now (turns out i actually did have to wait an hour like the message said) but i think this still counts as a bug bc i had to rewrite config to do it, which is probably not intentional behavior

from discord-tts-bot.

Hey there, yes I'm aware of this bug, someone reported this to me earlier today. I didn't come across this myself because I rely on the default values, so I intentionally take those settings out.

I'm working on a fix right now and I expect to upload it later tonight.

from discord-tts-bot.

I'm having the same issue. I changed the code a bit for our own discord, we have some smaller channels where there is a user limit but the bot should get into them, so deleted that lines.
Maybe a new feature?
However i tried updating them, got the same error when trying to add the slash commands, i don't know if it does it automaticly if you build a docker image and run that one afterwards?

from discord-tts-bot.

Maybe a new feature?

I actually don't understand what feature it is that you were suggesting.

As for the Docker thing, technically I can't make it so that it deploys automatically because the deployer needs the discord token.

On the docker case, you should be able to deploy it by running:

 docker run -it --rm -e DISCORD_TOKEN="your_token" -e DISCORD_ENABLE_TTS_CHANNELS="true/false" moonstarx/discord-tts-bot npm run deploy

from discord-tts-bot.

Thanks will try you suggested command in a minute

For the feature i suggest is. If you give a bot or user move users it can avoid a user limit unless stated otherwise in the code.
So what i did is remove these lines.

if (channel.full) { return 'error.channel.full'; }

from discord-tts-bot.

Ah I see, I was not aware that that happened with the move users permission.

In any case you can also avoid it by making the bot join another channel then moving it to the actual channel you want to use, though I would see how it would get annoying quick. I'll think about it because I remember that feature was made by someone else.

from discord-tts-bot.

Also, if you try to run that command you'll still find the bug from this issue. I'm planning on updating this today at night so chances are you can try this tomorrow with an updated docker image.

from discord-tts-bot.

This should be fixed in #62.

You should update your bot now and expect to deploy the commands without the need to change your config as a workaround.

from discord-tts-bot.