Prove text works first
Send a text prompt and confirm a response appears. If there is no text response, this is an AI/provider failure. If text works, rotating the language-model key can destroy a valid configuration without repairing audio.
Project voice support
Verity JE states that AI text supports multiple languages but its speech-to-text and text-to-speech were tested only in English. Revamped lists Groq voice, ElevenLabs, operating-system narrator, and a local TTS URL with narrator fallback. Use only the options documented by your project.
Audio output checklist
Check Minecraft master/voice sound levels, the operating-system output device, muted application state, Bluetooth device switching, and whether another application holds the audio device. Test a normal Minecraft sound before changing Verity settings.
Narrator and TTS fallback
If the selected cloud voice fails, select the project's supported narrator or local fallback and confirm the operating system can speak outside Minecraft. A working narrator isolates the failure to the cloud voice path.
Microphone checks
Microphone input and voice output are separate. Confirm the correct input device, operating-system permission, project push-to-talk binding, and toggle state. Use text chat to preserve a working baseline while testing the microphone.
Evidence for support
Record project ID, release, selected provider, selected voice backend, language, operating system, audio output, whether text works, and whether narrator fallback works. Never include provider credentials.
Questions
Why does Verity use the default narrator voice?
The project may be using its narrator fallback because the selected cloud or local TTS backend failed or was not configured.
Does microphone failure explain silent output?
Not necessarily. Input and output are separate. Test text input and narrator output independently.