Discord Tts Bot

The pitch here is unusually concrete. Discord's built-in /tts has three documented failure modes, and the bot's own docs name all three: /tts may be disabled for certain users, it requires everyone to have the source text channel open, and its settings are per-user OS-level, so everyone hears something different. If your server has ever had someone type /tts into a voice channel and get silence from half the room, that is the problem this solves. What you actually get: four providers behind one command set. Google Translate gives you 46 languages, Amazon Polly gives 45 voices across 22 languages, Microsoft Azure gives 73 voices across 47 languages, and Aeiou gives the DECTalk/Moonbase Alpha voice via /aeiou_say. Per-user settings are persisted, which is the detail that matters most in practice — a server where a dozen people each keep their own voice while sharing one /say command is a genuinely better experience than a server where everyone gets the default. TTS Channels are the sleeper feature. Point /google_set_channel or /channel_settings at a text channel and the bot reads every message posted there automatically, no command needed. For accessibility use — a member who cannot read along, or a room listening along to a busy text channel — that is the difference between a novelty and a utility. /channel_settings, /set_channel_provider, and /delete_channel_provider let you run different providers per channel. Where it hurts: deployment is entirely DIY. Node (normal), Docker, Repl.it, and Heroku are the four documented paths, each with its own updating procedure — and Repl.it and Heroku's free-tier story has changed a lot since 2022, so expect to do your own legwork there. The docs site itself says it is still under development and may contain incomplete information, and the last update stamp reads March 26, 2022. The bot is localized to English, Spanish, and French via /set_locale, which is narrower than the 46-language speech support underneath. And note what this is not: there is no hosted or invitable version described anywhere in the docs — you host it, you own it, you fix it. Compared with a single-engine Discord TTS bot, you trade simplicity for provider breadth and per-user voice memory. Compared with cloud TTS services you'd wire up yourself, you trade control for a working set of slash commands. If your server has a maintainer who is comfortable with Node or Docker, this is the most flexible free option in its category. If it doesn't, look elsewhere.