Verity Mod Updates: What Changed and Should You Update?

Before you update anything

Most “Verity stopped working” reports after an update come from one of three things: the new file is for a different game version, the old file is still installed beside it, or the settings format changed. Two minutes of preparation avoids all three.

1. Check the game version on the new file. It must match the Minecraft version you actually run, not just be newer.
2. Back up first. Java: copy the world folder and the instance’s config folder. Bedrock: Export World from the world’s settings.
3. Remove the old version. Java: delete the old Verity jar from mods. Bedrock: remove the old packs from the world and from Settings > Storage.
4. Test in a new world before opening your main save.

If an update fails, restore your backup and the previous file rather than mixing old and new. The rest of this page is newest first for each project.

Verity JE (Java), Project ID 1591438

6.0.0-beta.1 to beta.9 (late July to September 3): test builds

What changed. The release notes only say the AI configuration was reworked, so we compared the beta.9 jar with 5.7.4 directly:

• More AI providers. GROQ, OPENAI, GEMINI, MISTRAL, OPENROUTER, and OLLAMA (direct, on port 11434, no LiteLLM). The default is OPENAI, so set it to GROQ if you use a Groq key.
• Two presets instead of three. SMART (default) and FAST; on Groq they are openai/gpt-oss-120b and openai/gpt-oss-20b. Use Custom Model lets you type any model ID, and Ollama always needs one.
• Thinking mode for models that support it.
• New voice providers. Native, Local (default), Groq, Kokoro, and Cartesia for speech; Groq, Native (default), or a local Whisper server for recognition.
• Long-term memory. Verity saves verity_memory.json and remembers you across sessions; /recoververity clear_history wipes the chat history.
• More horror controls. New Kill Entities and Kill Wildlife toggles; the karma bar is now hidden by default; the Demon gains window-stalking, door-breaking, climbing, and glass-breaking behaviours.
• Same requirements. Forge 47+, Minecraft 1.20.1, GeckoLib 4.4+, YACL 3.6+. The Demon still arrives after 5 in-game days by default.

Who should update. Players who want to try new features and can live with bugs, and anyone who wants Verity JE Extra, which requires Verity 6.x.

What to redo. Treat it as a new install, not an upgrade:

• Make a separate Forge 1.20.1 profile; keep your working 5.7.4 profile untouched.
• Re-enter your provider settings in the beta’s menu. Do not copy the 5.7.4 config file across.
• For local AI, follow the maintainer’s 6.0.0+ tutorial. Do not reuse the stable LiteLLM address on port 4000 or the ollama/ prefix just because 5.7.4 needed them.
• Expect each new beta to change things again; read its notes before replacing the previous beta.

5.7.4 (August 18): stable, recommended

What changed. The release notes record one fix: a Groq model that had gone missing. No setup changes are described.

Who should update. Everyone on 5.7.3 or older 5.7.x who uses Groq, especially if replies stopped with a model error.

What to redo. Replace the jar, keep your config. Then send one test message. If you see a model or 404 error after updating, check the error lookup before changing your key.

3.4.1 (June 30): legacy NeoForge 1.21.1

What changed. This is the NeoForge 1.21.1 file listed on the project, on a separate older branch. The main project line is Forge 1.20.1.

Who should update. Only players who must stay on NeoForge 1.21.1 for another mod. New players should not start here.

What to redo. Nothing, if you are already on it. Moving to 5.7.4 means a new Forge 1.20.1 profile; worlds and configs from 1.21.1 should not be copied into it.

Verity BE by Utlover65 (Bedrock), Project ID 1574632

4.2.3 (October 18): current, Bedrock 26.50

What changed. No release notes were published. Inside the file, the packs are labelled 4.2.3 (the folders are still named 4.2.0), require game version 1.21.110 or newer, and the resource pack declares PBR and ray-tracing support, which is what the new lighting needs. The AI still connects through the Hive Mind relay with /script debugger connect traye.ddns.net 19144; see how it connects.

Who should update. Everyone on 4.2.0. A follow-up file on the same game build normally fixes problems found in the previous one.

What to redo. Remove the 4.2.0 packs, import 4.2.3, activate both packs, and repeat the connection step in a new world.

4.2.0 (October 5): first 26.50 file, lighting update

What changed. A visual update. The notes describe colored light from torches, lanterns, candles, and other light sources; reworked materials and shading on Verity, the box, the chest version, the Smiler, and the flashlight; and a game-version check of Minecraft 1.26.0 or higher. The new lighting needs Vibrant Visuals or ray tracing.

Who should update. Everyone whose Minecraft is on 26.50. If your device cannot use Vibrant Visuals, you still need this line for 26.50; it simply looks like the previous version.

What to redo. Turn on Vibrant Visuals in Settings > Video if your device offers it. See the Bedrock guide for what flat lighting does and does not mean.

4.1.2 and 4.1.3 (September 1 and 16): Bedrock 26.40

What changed. Two revisions for 26.40. This site could not verify release notes for either, so no specific fixes are claimed.

Who should update. No one should install these now unless the device is still on 26.40.

What to redo. If you are on 26.50, move to 4.2.3 instead.

Earlier files (August): 2.0.1 and the 4.0.0 hotfix

Utlover65 moved quickly in August, from 2.0.1 to a 4.0.0 hotfix, both for 26.40. Tutorials recorded in August may show menus or commands from these files. If a video’s steps do not match what you see, the video is probably for one of these releases.

Verity - Bedrock Edition by PnTMC, Project ID 1575941

4.0.0 for 26.50 (September 17): current

What changed. A new file for Bedrock 26.50, still numbered 4.0.0. The change is the game build it targets; this site did not find setup changes in the project’s notes or setup guide.

Who should update. Anyone on Bedrock 26.50 who downloaded 4.0.0 before September 17. That earlier download is the 26.40 file, even though it has the same number.

What to redo. Remove the old packs, import the 26.50 file, and keep using the same helper and .env. Run /connect 127.0.0.1:3000 again in each world session, as before.

Helper files v4.0.0 to v4.0.3 (August 15 to 27)

What changed. The helper programs are released separately from the add-on, on PnTMC’s GitHub setup guide. Four helper releases appeared in August: v4.0.0 and v4.0.1 on August 15, v4.0.2 on August 20, and v4.0.3 on August 27. v4.0.3 is the latest. Its contents are described in the Bedrock guide.

Who should update. Anyone whose helper folder came from a video or a friend rather than PnTMC’s own release, or who installed before August 27.

What to redo. Download the zip for your device from the setup guide’s v4.0.3 release, copy your three values (GROQ_API_KEY, FISH_API_KEY, FISH_REFERENCE_ID) into the new .env, and close the old helper before starting the new one.

4.0.0 for 26.40 (August): the local-helper setup

What changed. PnTMC’s 4.0.0 setup uses a device-specific local helper: Termux on Android, a-Shell on iOS, and Python on Windows, with your own Groq and FishAudio keys in a .env file. The previously documented /verity_language command is not part of the 4.0.0 guide.

Who should update. Only devices still on 26.40.

What to redo. Follow the Android guide or the Bedrock device steps. When PnTMC updates the helper files, copy the new folder but keep your .env values, and compare them with the new template in case a setting was renamed.

When Minecraft itself updates

Bedrock updates automatically on most phones and on Windows. When the game moves to a new build (for example from 26.40 to 26.50), an add-on built for the old build can import fine and still fail in the world.

• Do not open your main Verity world right after a game update. Check the project’s Files tab for a file that names the new build.
• If there is no new file yet, wait. Editing a pack’s manifest to claim the new version does not make its scripts compatible.
• On Java, the game does not update on its own. Keep the Verity profile pinned to Minecraft 1.20.1 in the launcher so it is not moved to “latest release”.

How this page is maintained

Entries are written from the projects’ own pages, release notes, and setup guides, linked below. Where a project did not publish notes for a file, the entry says so instead of guessing. When a new file appears, it is added here with the same three questions: what changed, who should update, and what to redo.