Verity Mod Java Edition Setup Guide

Recommended Java path

The recommended starting point is stable Verity JE 5.7.4 for Minecraft 1.20.1 with Forge. On September 5, 2026, CurseForge still lists it as the main release, alongside 6.0.0-beta.9 for Forge and the older 3.4.1 for NeoForge 1.21.1. Choose the beta only for a separate test profile with a backup. Check the maintainer’s file listing.

Match the tutorial to the release

• 5.7.x: the earlier Java setup video and Ollama walkthrough titled “up to 5.7.3” are older references. The 5.7.4 changelog records a missing Groq model fix, not a new setup tutorial.
• 6.0.0 beta: CurseForge’s Setup link now opens Full Verity JE Mod Setup | 6.0.0+. The beta.9 changelog specifically records an AI config rework. A field shown in an earlier video may no longer match beta.9.
• Legacy NeoForge: the independent macOS installation record describes 3.4.1 on July 14, 2026, and says its in-game AI screenshots were still pending. It is not a completed 5.7.4 conversation test.

Verity JE is a client-and-server mod according to its project details. That means a multiplayer setup may require compatible installation on the server and participating clients, not only on the person who wants to see Verity. Begin in single-player or a private test environment so other mods, server permissions, and network policy do not hide the first problem.

Prepare a clean profile

Create a separate launcher profile for the exact Minecraft version. Install the matching loader into that profile: Forge for 1.20.1 or NeoForge for the legacy 1.21.1 branch. Launch that empty loader profile once before adding Verity. A successful empty launch proves that Java, Minecraft, and the loader can start together.

Keep the first test profile small. Do not add a large modpack, shaders, performance patches, and Verity all at once. Every extra mod expands the number of possible conflicts and makes logs harder to read. After Verity works by itself, add other mods in small groups and test between each group.

Back up existing worlds before opening them with a new loader or mod set. A separate test world is preferable because a failed experiment should not become a world-recovery problem.

Install from the maintained project

Begin with the download guide and open Verity JE by VarmiteYT, Project ID 1591438. For the stable route, select the 5.7.4 file details: filename verity-5.7.4.jar, Minecraft 1.20.1, loader Forge, release type R. These links open the maintainer’s pages, not a mirrored package.

Open the Verity JE CurseForge project and confirm these four details:

1. Project title: Verity JE.
2. Project author: VarmiteYT.
3. Project ID: 1591438.
4. File target: your exact Minecraft version and loader.

Use the dependencies listed for the specific release at the time you download. Dependency requirements can change, so this guide does not freeze an old list copied from a video. Place the selected project file and required dependencies in the clean profile’s mods directory, not in a different launcher instance that happens to have a similar name.

Launch once and stop at the title screen. If Minecraft fails before a world opens, the problem is not the AI setup: check the Java runtime, loader, missing dependencies, duplicate mods, or incompatible mods. Read the first meaningful error in the latest log instead of focusing only on the final “exit code” line.

Choose one AI path

Verity JE supports a cloud path using Groq and a local path using Ollama. They solve the same core need in different ways.

Groq is usually simpler when your computer should not run a local language model. It requires a GroqCloud account, an active API key, and network access from the game. In 5.7.4, open Mods > Verity > Config from Minecraft’s title screen. The screen is titled Verity Configuration. Under AI Settings, set AI Provider to GROQ, paste the secret into API Key, and leave AI Intelligence Level at FAST for the first test. Under Local LLM, keep Use Ollama off: enabling it overrides the cloud-provider choice. Apply the changes and reopen Config to check them without exposing the key.

Ollama keeps model inference on your own machine, but stable 5.7.4 uses a LiteLLM gateway between Verity and Ollama. In the same config screen, Local LLM contains Use Ollama, LiteLLM URL (default http://127.0.0.1:4000/v1/), and Ollama AI Model (default ollama/qwen2.5:1.5b). The gateway prefix ollama/ is intentional; Ollama itself lists that model as qwen2.5:1.5b. Follow the service and gateway checks before enabling this option.

These labels and defaults were checked in the maintainer’s published 5.7.4 artifact. The 6.0.0 betas have a different configuration flow.

Choose one provider for the first successful conversation. Configuring both at once makes it unclear which provider produced an error. Follow the Groq setup or Ollama setup guide, then return here.

First world test

Create a new world with default rules unless the project instructions require a specific setting. Confirm that the Verity entity or interaction appears before testing voice, text-to-speech, or horror progression. Test one input method first. The project page says AI text can support multiple languages, while speech-to-text and text-to-speech were tested in English; if voice fails in another language, test simple English text before assuming the whole mod is broken.

After Verity appears, press Minecraft’s chat key (T by default), type Verity, say hello., and press Enter. Stable 5.7.4 handles ordinary Minecraft chat; no separate conversation command is needed. Including Verity also satisfies General > Require Verity if that option is enabled. Keep General > Immersive Mode off during diagnosis because its purpose is to hide Verity’s UI and chat.

Allow time for the first response. A local model may need to load into memory; a cloud request may be delayed by network or service limits. If the game remains responsive but Verity does not answer, check the provider connection. Once text works, hold V, speak, and release V to submit speech; M cycles available microphones. These are the defaults in 5.7.4, so check Options > Controls > Key Binds for remapped or conflicting keys.

Once typed text works, use the conversation and voice guide to test microphone permission, speech recognition, language, and audio output separately. If Verity shows a numeric provider error, use the API connection guide instead.

Failure order that saves time

Work from the bottom of the stack upward:

1. Minecraft does not launch: verify Java runtime, game version, loader, dependencies, and duplicate files.
2. World opens but Verity is absent: verify the mod is listed as loaded, use a fresh world, check spawn or interaction instructions, and remove conflicting mods for a clean test.
3. Verity appears but has no dialogue UI: in stable 5.7.4, try ordinary Minecraft chat and turn off General > Immersive Mode. Check key conflicts before testing voice.
4. UI appears but no response arrives: verify one selected provider, API key or local service, exact model name, network access, and rate or service errors.
5. Text works but voice fails: separate microphone input, speech recognition, and text-to-speech from the language-model response. Test English text first, then one audio direction at a time.

Never publish an unredacted log until you have searched it for API keys, usernames, local paths, server addresses, and personal information. A log can be useful without becoming a secret leak.

Forge 1.20.1 versus NeoForge 1.21.1

Do not mix loaders. A Forge profile does not become NeoForge because a file is placed in its mods folder, and a release built for one loader should not be expected to initialize on the other. If you are troubleshooting 1.21.1, reproduce the issue with the recommended 1.20.1 Forge setup before concluding that the whole project is broken. That comparison separates a version-specific defect from a general setup problem.

Here, “legacy” means the older 3.4.1 NeoForge release listed on June 30, 2026. The current CurseForge description does not display the earlier “deprecated and buggy” warning. Do not treat that historical wording as a current maintainer statement or transfer Forge 5.7.x settings to this older build.

Before adding Verity to a real world

Confirm that the game launches repeatedly, the same provider answers more than once, restart behavior is stable, and your world backup can be restored. Then add other mods gradually. Keep a record of the working Minecraft version, loader build, Verity release date, dependencies, provider, and model name. That short record is more useful than “latest everything” when a future update changes one part of the chain.