Verity Mod Not Working or Not Responding

Seeing “API connection failed” or “AI connection error”?

These two chat messages are the most common reason people land on this page. On Verity JE 5.7.4 they mean:

• API connection failed. Status: 429: the AI service is rate-limiting you. Stop sending messages, wait a minute, then send one short one. Long conversations hit the limit sooner. Other numbers have other causes: 401 is a rejected key, 404 a wrong model or address.
• AI connection error. You might need to replace your API Key.: a generic message the mod shows for any failed reply. Check logs/latest.log for the [Verity AI] line with the real reason before replacing your key.

The API connection guide covers each status code, and the Groq limit calculator shows how many messages your limits allow. On 6.0.0-beta.9, also check that AI Provider is set to GROQ if you use a Groq key; the beta defaults to OpenAI.

Start with the last thing that works

“Not working” hides several different failures. A game that crashes before the title screen has a different problem from a companion that appears but never answers. Do not reinstall everything after every symptom. Find the last step that worked and test the next one.

Work down this ladder. The first step that fails is where the problem is; everything above it already works and does not need to be reinstalled.

1. Minecraft launches with the intended edition and version.No: loader, version, or dependency problem. See crashing and the Forge messages.
2. The mod or add-on is loaded and active.No: Java: check the mods list; Bedrock: both packs must be under Active.
3. The world opens without content or script errors.No: Bedrock: Beta APIs or a file for a different game build. Turn on the content log.
4. Verity appears, or the documented interaction becomes available.No: see “Java: the world opens but Verity is missing” or “Bedrock: Verity does not appear” below.
5. The dialogue accepts a typed prompt.No: Java: Require Verity and Immersive Mode; Bedrock: the project's chat trigger.
6. The cloud or local model returns a text reply.No: provider problem. Read the code with the error lookup.
7. Microphone, speech recognition, and voice output work.No: voice is a separate layer. See talking to Verity.

Record the edition, game version, loader or add-on release, exact symptom, and time. That small baseline prevents Java and Bedrock instructions from being mixed in the same support request.

Quick symptom table

What you see	Most likely layer	Start here
Crash before the title screen	Java runtime, loader, or dependency	Crash guide
Verity missing from the Mods list	Wrong profile, wrong loader, or wrong folder	Java: Verity is missing
World opens, no Verity	World content, spawn steps, or pack activation	The sections for your edition below
Verity appears, never answers	AI provider, API key, or local model	Java: Verity appears but does not answer
Bedrock shows ...	Online connection step or service	Bedrock: Verity displays ...
Text works, voice silent	Microphone permission, speech-to-text, or audio	Java: text works but voice does not
Everything broke after an update	Version mismatch	Updates section below

The table is a starting point, not a diagnosis. If two rows seem to match, test the earlier layer first; an upstream failure often looks like a downstream one.

Java: Minecraft does not launch

If the Java game crashes before a world opens, Groq and Ollama are not the first concern. Verify that the launcher profile uses the exact Minecraft version and the matching loader. The recommended setup is Verity JE 5.7.4 on Forge 1.20.1; the 6.0.0 betas (currently 6.0.0-beta.9) also target Forge 1.20.1. The NeoForge 1.21.1 file belongs to a separate legacy branch.

Remove unrelated mods and start with only Verity plus the dependencies listed for that release. Launch the empty loader profile once if you have not already. Check for duplicate project files and dependencies built for a different Minecraft version or loader. Having both a 5.7.4 jar and a 6.0.0 beta jar in the same mods folder is a common cause of confusing startup errors.

Read the earliest meaningful error in the latest log or crash report. The final exit code is often only a summary. Search the log locally for “missing,” “requires,” “failed,” and the name of the first mod mentioned near the exception. Before sharing any excerpt, remove API keys, usernames, local paths, server addresses, and personal information.

Java: the world opens but Verity is missing

Confirm that the loader’s mod list includes Verity JE and that you opened the same launcher instance where the file was installed. Create a new world with a minimal mod set. Follow the current project instructions for introducing or interacting with Verity rather than assuming a recipe, spawn egg, or key from an older video.

If the clean world works, add other mods back in small groups. If it does not, compare the exact Verity release with the game version and loader. A Forge release in a NeoForge profile, or the reverse, should be treated as incompatible even when the filename looks plausible.

Old worlds deserve extra caution. A world created with an earlier Verity version may hold saved entity data that a newer release handles differently. Test in a new world before deciding the mod is broken, and back up the original save before opening it with a different release.

Java: Verity appears but does not answer

This is the boundary between the in-game entity and the AI provider. Pick one provider for the test.

For Groq, confirm that the API key is active, entered only in the location shown by the current project instructions, and allowed to reach the service over the network. Do not post the value. If it may have been exposed, revoke it and create a replacement before continuing. In 5.7.4, also check that Local LLM > Use Ollama is off; that switch overrides the selected provider. The Groq API key guide walks through the exact menu labels.

For Ollama, first check your Verity release. Stable 5.7.4 uses a LiteLLM gateway: test Ollama and the installed model outside Minecraft, then start and test LiteLLM. Keep the ollama/ prefix before the exact installed model tag in both the gateway and Verity configuration; Ollama itself lists the unprefixed tag. Verify the gateway URL and any gateway authentication instead of bypassing it to fix a 401. The 6.0.0 beta family removed the LiteLLM requirement and changed configuration; legacy NeoForge releases need their own release instructions, not assumed 5.7.4 settings. Follow the version-qualified Ollama setup guide and use the API connection failure guide for error-specific checks.

Use a short text prompt such as Verity, say hello. Watch for a provider error, timeout, model-not-found message, or rate/service limit. Avoid repeatedly sending prompts while a first local model is still loading; a large model on a modest computer can take a minute or more to answer the first request.

Also check the conversation filters before blaming the provider. In 5.7.4, General > Require Verity means messages must include her name, and General > Immersive Mode can hide replies from chat. A working connection can look broken when one of those settings is active.

If an exact code appears, use the API connection failure guide. A 401, 404, 429, timeout, and local connection refusal require different repairs.

Java: text works but voice does not

Separate the audio path into three tests: microphone access, speech-to-text, and text-to-speech. A successful text answer proves that the model response path works, but it says nothing about the microphone or speaker output.

Check the operating system’s microphone permission for the Java/Minecraft process, the selected input device, and the current key bind. Then test whether recognized text appears. Finally, test voice output. The project page notes that AI text can support multiple languages while speech-to-text and text-to-speech were tested in English. Use simple English during diagnosis even if you intend to chat in another language later.

On Windows, check Settings > Privacy & security > Microphone and make sure desktop apps are allowed to use it. On macOS, check System Settings > Privacy & Security > Microphone for the launcher or Java process. Headsets that switch between “hands-free” and “stereo” modes can also change which device Java sees; pick the device explicitly instead of relying on the system default.

Bedrock: Verity displays ...

The Verity BE troubleshooting notes associate three dots with a connection or online service problem. The add-on loaded far enough to show a response, so reinstalling the resource pack is not automatically the right first move.

Verify the exact Bedrock build, confirm both behavior and resource packs are Active, confirm Beta APIs and cheats, and repeat the project’s current connection step once. Read the full response. Then test a new world with no other behavior packs. If multiple users report the same online service failure at the same time, monitor the project page or support channel rather than repeatedly changing a working local install.

Both Bedrock projects currently target the same game build (see the box above), which makes them easy to confuse. They are separate projects with separate steps; three-dot behavior described for one does not automatically apply to the other.

Bedrock: the dialogue box is missing

A missing interface points toward inactive behavior scripts, disabled experiments, or a game-build mismatch. Re-open the world settings and confirm Beta APIs remained enabled. Verify the behavior pack is under Active, not only My Packs. Use a fresh world created after all required settings were enabled.

Remove other behavior packs for the test. Bedrock updates can rename experiments or change creator API behavior; compare your current menu with the project tutorial and description. If your Bedrock build is newer than the listed release, the project may need an update.

Bedrock: Verity does not appear

Confirm both pack halves imported without a content error. Remove duplicate old revisions from the world and storage, restart Minecraft, and import the version listed on your chosen project page again. Follow the current project steps for spawning or activating Verity. Java key binds, recipes, and AI service instructions do not apply.

If the entity appears in a clean world but not an existing world, compare active packs and experiments. Do not keep toggling settings in a valuable save; duplicate the world first.

On consoles and mobile devices, imports can silently fail when storage is low or when the file was renamed during download. If the import notification never appeared, re-download from the project page and import again before changing world settings.

It stopped working after an update

Updates are the most common reason a setup that worked yesterday fails today. Work out which side changed:

• Minecraft updated. Bedrock updates automatically on most devices, and an add-on built for 26.40 may not behave correctly on a newer build until the author ships a fix. On Java, launchers can move a profile to a new version; pin the Verity profile to 1.20.1.
• Verity updated. Read the changelog for the new file. The 6.0.0 betas changed AI configuration, so a 5.7.4 config copied into a beta profile can leave the companion silent.
• The provider changed. Cloud models can be retired or restricted. A model that answered last month can return a model-not-found error now even though nothing local changed.
• Your system changed. New antivirus, firewall, VPN, or privacy settings can block outgoing requests or the microphone.

Change only one thing at a time while testing, and keep a copy of the last working profile or world so you can return to it.

“No purpose,” connection errors, and changed behavior

Capture the exact text, capitalization, and when it appears. A phrase shown as story content can look similar to a technical error, while an online service response can look like dialogue. The “Error: No Purpose” video linked from the project page is included here for context, but a video is not a substitute for the current changelog or support notice.

Check whether the issue reproduces after a restart in a clean world and whether it affects every prompt. If the behavior changes with the time or online service availability, record the time and current version. Do not infer malware, account compromise, or intentional surveillance from horror-themed dialogue alone; technical claims require technical evidence.

The project is missing or looks taken down

Search by exact Project ID: Verity JE is 1591438; Verity BE by Utlover65 is 1574632; Verity - Bedrock Edition by PnTMC is 1575941. Inspect the matching file history and author notes. Do not transfer rumors or troubleshooting commands between separate projects.

Avoid backups offered through chat attachments, shared drives, and link shorteners. Having an old copy does not prove where it came from or whether it is safe. Community discussions can tell you that others are confused, but conflicting explanations are not a verified removal reason.

A useful support report

Include the edition, exact game version, loader and branch if Java, project release date, device/operating system, provider choice, last working step, exact error text, clean-world result, and whether the issue began after an update. Exclude API keys, full home-directory paths, IP addresses, private server details, and account data.

That report gives the project author something reproducible. “Project ID 1574632, release 4.2.3, Bedrock 26.50, both packs active, Beta APIs and cheats enabled, connection step succeeds, then every prompt shows three dots in a new world” shows exactly where the setup fails. If the project page displays a conflicting game-version label, include that too.

A Java equivalent might read: “Verity JE 5.7.4, Forge 1.20.1, Windows 11, Groq provider, Use Ollama off, Verity appears in a new world, typed Verity, say hello. returns a 401 in the log.” Each detail removes a guess for the person helping you.