🔊 Bozos TTS Troubleshooting

Connect vs Speak: the voice permissions a Discord TTS bot actually needs

A TTS bot can be online and respond to commands while still being unable to join or speak in a voice channel. Voice access is controlled separately from ordinary text-channel access.

Connect and Speak do different jobs

Connect allows the bot to enter a voice channel. Speak allows it to transmit audio after it has joined. If Connect is denied, the bot cannot join at all. If Speak is denied, it may appear in the channel but users will not hear generated speech.

Permissions Bozos TTS commonly needs

  • View Channel so the channel is visible to the bot.
  • Connect so the bot can enter the voice channel.
  • Speak so generated TTS audio can be played.
  • Normal text permissions in the channel used for commands and eligible messages.

Why server permissions can look correct but still fail

Discord channel overrides can replace the permissions inherited from a server role. A Bozos TTS role may have Connect globally while a specific voice channel explicitly denies Connect. The channel-level deny wins for that channel.

How to fix a missing Connect permission

  1. Open the affected voice channel's settings.
  2. Choose Permissions.
  3. Select the Bozos TTS role or the bot member.
  4. Allow View Channel, Connect and Speak, or remove an unnecessary explicit deny so the role can inherit the correct permission.
  5. Run /join again from that voice channel.

Check category overrides too

If several voice channels are affected, inspect their category permissions. A category-level deny can propagate to every synchronized child channel. Fixing the category is often cleaner than editing each voice channel separately.

Do not confuse command access with voice access

A successful /help or /language response proves that the bot can interact in Discord, but it does not prove that it has voice permissions. Test the exact voice channel where TTS should run.

Complete Bozos TTS setup →TTS documentation →