If you have enable_tts_channels set to true, you will have access to the additional commands: Send an aeiou (sounds like Stephen Hawking) TTS message in your voice channel. Sets the speed to be used by the say and google_say command for yourself.ĭisplay a help message with all the available commands. Sets the language to be used by the say and google_say command for yourself. Sets the speed to be used by the say and google_say command by default.
Sets the language to be used by the say and google_say command by default. Send a Google Translate TTS message with multi-language support in your voice channel. Sets the timeout for the bot to leave the channel when not in use.ĭisplay a list of the languages supported by the Google Translate provider. Sets locale to be used by the bot in this guild. Sets the provider to be used by the say command for yourself. Sets the provider to be used by the say command for the server by default. Get the TTS settings you currently have set for yourself. Get the default TTS settings currently set for the guild. Send a TTS message in your voice channel with your own settings or the ones saved for this server. Here's a list of all the commands for the bot: Remember you can always check your bot's console if you access the View Logs in the More dropdown menu.
You can now go back to your app's Overview, make sure you disable the web dyno and enable the bot dyno. To deploy to Heroku, you can click on the image below and login to your account. Make sure to have enable_keep_alive set to true and use UptimeRobot to poll the address that shows up for your repl to make sure it stays on 24/7. Running on Dockerīefore you run this image, you should deploy your commands, you can do so by running: If you set enable_tts_channels to true, you must enable the message content privileged intent in your bot's application page. This makes it so the bot speaks the name of the author of every message. Whether the bot should prepend each TTS message with a 'User said.'. If you need to specify the port to use you should set the PORT environment variable (Heroku uses this by default). Additionally, you should use something like UptimeRobot to poll the associated address to keep the bot alive. You should only use this option if you're planning to host the bot on something like or Heroku. Whether an HTTP server should be started. You need the privileged message intent (accessible in the Bot page of your bot's application page) for this feature to work properly. With this setting, you can send TTS messages by just sending messages to a channel that you have enabled a provider for. Whether to enable the message-only TTS for specific channels. This is only required if you have set the provider type to redis. If you plan on just hosting the bot for a small server you should choose level, if you plan on sharding the client redis can be a better choice. Level is a file based key-value store whereas Redis is a cache service. You do not need to set this to anything if you're not planning on developing the bot. This setting can be customised per server and this will be used if a server has not set their own value. The time it takes the bot to leave a voice channel when inactive by default on all servers.
DISCORD TRANSLATE BOT GITHUB UPDATE
If set to null the presence auto update will be disabled. The time interval in milliseconds in which the bot updates its presence. Whether the bot should send error reports to the owner via DM when a command errors. A prefix is no longer necessary because this bot uses the all new interactions (slash commands). This table contains all the configuration settings you may specify with both environment variables and the JSON config file. The settings set with the environment variables will take higher precedence than the ones in the config JSON file. You may also configure these options with environment variables.
DISCORD TRANSLATE BOT GITHUB HOW TO
If you don't have a discord token yet, you can see a guide on how to create it here. Inside the config folder, rename the file to settings.json and edit the file with your own Discord Token and other settings.
You should send this link to anyone that wishes to add your bot to their Discord server. Then, another box should show up with more checkboxes, enable the following ones:Īt the bottom a link should show up, access this link to invite your bot. With plenty of checkboxes, enable the bot and mands checkboxes. Then, you should head over to the OAuth2 page and select OAuth2 URL Generator. Then, you should enable it as a botīy going into the Bot page and setting up your bot. Head over to Discord Application Page and create a new bot. That may affect your current installation. Make sure you check the README everytime you wish to update in case there are breaking changes
0 kommentar(er)
