Current project map checked July 24, 2026
Verity Mod is the name players use for separate Minecraft Java and Bedrock projects based on the Verity AI horror character. Compare the current projects, match your game version, and open the maintainer page before downloading.
Quick answer
The Verity Mod is not one universal Minecraft file. The name began with ThatMob's Verity character and horror videos, while the playable files now found by players are separate community projects. They share a character idea, but they do not share one owner, package, game edition, or installation process.
On Java Edition, Verity JE is an AI-powered companion project for Forge 1.20.1, with an older NeoForge 1.21.1 branch that its maintainer calls deprecated and buggy. On Bedrock and MCPE, Verity BE, PnTMC's Verity - Bedrock Edition, and Verity Pocket Edition (Be) are separate add-ons. Choose the project first; then match its exact Minecraft version and setup instructions.
Current verified release map
These are separate community Verity Mod projects. A familiar name or thumbnail is not enough: confirm the owner, Project ID, Minecraft build, loader, and file date on the project page.
Both checked records list the July 18, 2026 file for Minecraft 1.20.1 Forge.
Open CurseForge record Open Modrinth version and checksum Read Java install detailsThe maintainer describes this branch as deprecated and buggy. Do not choose it only because 1.21.1 is newer.
Read the Verity JE statusVersion 1.0.9 adds local text-to-speech controls and new interaction behavior. Use this route for Bedrock or mobile and follow its world-setting requirements.
Open exact Verity BE record Read MCPE route detailsThis is a different Bedrock adaptation. Follow PnTMC instructions only when that is the project you selected.
Open exact PnTMC recordThis is another similarly named Pocket Edition listing. Use it only when the project page or tutorial names that exact route.
Open Pocket Edition record Read Pocket Edition checksBrowser-only identity check
Paste a project URL or choose a local file. The Verity Mod checker compares names, domains, paths, extensions, and known project identifiers. It calculates SHA-256 locally and compares the current Java JAR with Modrinth's published SHA-512. Your file never leaves this browser.
Setup route chooser
Select your edition and problem. The result links to a maintainer project page and gives a short setup order.
Complete topic directory
Every Verity Mod guide has a distinct job. Use one route instead of reading the same generic setup advice repeatedly.
What players need to know
Verity began as a Minecraft horror concept associated with ThatMob, while the files players can install now are community adaptations and modpacks. The current Java and Bedrock listings do not share one package, owner, loader, or setup process. That is why a search result that only says "download Verity" is incomplete.
For Java, the checked route is Verity JE by VarmiteYT. Its project description says the adaptation has permission from ThatMob and documents Groq and Ollama options. For Bedrock, the checked projects are maintained by different people and use different add-on instructions. Treat each project page as its own product record.
A Java jar belongs in a matching Forge or NeoForge profile. A Bedrock mcaddon is imported into Minecraft and then activated through world settings. Renaming a file does not convert one edition into the other. The game version is equally important: a 1.20.1 Forge file is not a replacement for a 1.21.1 NeoForge file.
Use the Files tab on the maintainer page to check the release date, supported version, and changelog again. Current values on this guide are a routing snapshot, not a promise that the hosting page will never change.
| Player setup | Expected file | First check | Continue here |
|---|---|---|---|
| Java 1.20.1 | Forge jar | Loader and dependencies | Java guide |
| Java 1.21.1 | NeoForge jar | Legacy warning and version | Verity JE status |
| Bedrock 26.30 | mcaddon | Project owner and world options | Bedrock guide |
| Mobile / MCPE | Bedrock mcaddon | Import visibility and pack activation | MCPE guide |
Safe installation order
Confirm Java, Bedrock, or MCPE before opening a file page. A Java jar cannot be imported into Bedrock.
Compare owner, Project ID, supported game version, loader, release date, and file history.
Use a clean Java profile or fresh Bedrock world before adding unrelated mods, resource packs, or an important save.
Configure Groq, Ollama, permissions, and voice only after the base Verity project loads successfully.
Do not paste credentials into a download guide, mirror, short-link page, or comment thread.
Frequently asked questions
Start from the maintainer project page for your edition. Verity JE by VarmiteYT is the checked Java route. Verity BE by Undertaletalelover, Verity - Bedrock Edition by PnTMC, and Verity Pocket Edition (Be) are separate checked Bedrock routes. This site links to those project records and does not host a file mirror.
The checked Java project is Verity JE. The current Forge 1.20.1 file appears under CurseForge Project ID 1591438 and Modrinth Project ID on1Y0osD. CurseForge also lists an older NeoForge 1.21.1 branch. Match the Minecraft version and loader together before placing a jar in the mods folder.
Separate community Bedrock add-ons are available. Use an mcaddon route for Bedrock or MCPE and do not try to import a Java jar. Check the project owner, supported game build, required Beta APIs, cheats, and pack activation steps.
Start with edition, version, and loader. Java failures often come from a mismatched profile or incomplete AI setup. Bedrock failures often come from inactive behavior or resource packs, disabled experimental settings, or commands. Continue with the focused troubleshooting guide after checking the base install.