Verity Mod Download: Java and Bedrock Sources

Open the project for your edition

These buttons open the CurseForge project pages, not direct files. Choose your edition, then use that project’s Files tab to select the exact game version.

Compare the three projects

For Java Edition, start with Verity JE by VarmiteYT. For Bedrock Edition or Minecraft on mobile, compare Verity BE by Utlover65 with Verity - Bedrock Edition by PnTMC. These are separate projects with different authors, Project IDs, releases, requirements, gameplay, and support notes. A Java file cannot be imported into Bedrock, and one Bedrock project’s instructions should not be assumed to apply to the other.

Project	Author	Project ID	Platform	Choose it if
Verity JE	VarmiteYT	1591438	Java, Forge 1.20.1 (legacy NeoForge 1.21.1)	You play Java on a PC and can run a separate Forge profile
Verity BE	Utlover65	1574632	Bedrock add-on	You want the fewest setup steps on Bedrock: no helper program
Verity - Bedrock Edition	PnTMC	1575941	Bedrock add-on	You want your own Groq and FishAudio keys and generated voice, and can keep a helper running

The project page gives you information that a bare file link hides: the author, Project ID, supported game versions, loader, update time, changelog, comments, and file history. Read those details before choosing a release.

Check compatibility before choosing a file

The current files are in the box at the top of this page. Two details catch people out: on Java, the newest-looking file is often a beta rather than the stable release, and on Bedrock, PnTMC reuses the same add-on number for different game builds. Read the release type and the game version on the file page, not just the number.

Use the version compatibility guide for the complete current and legacy matrix, exact release numbers, source conflicts, and verification history. This page stays focused on choosing the correct project source.

How to choose a file without guessing

1. Confirm the edition first. Java users need a Java mod loader profile. Bedrock and PE users must also choose which Bedrock project their tutorial uses. The project title alone is not enough.
2. Match the full version. Treat 1.20.1 and 1.21.1 as different targets. Treat Bedrock 26.40 and 26.50 as different targets. A close-looking version is not a compatibility promise.
3. Match the loader or import method. The recommended Java setup uses Forge on 1.20.1. The older 1.21.1 branch uses NeoForge. Bedrock uses its own add-on import and world-pack setup.
4. Read dependencies and changelog. Use the dependencies shown by the project at the time you download. Do not copy a dependency list from an old video without comparing it with the current file page.
5. Check the release date and author note. A newer upload from a different account is not automatically the successor. Look for continuity on the same Project ID or an explicit link from the original project page.

Find your exact game version first

Many failed installs start with a guessed version. Check it before you open the Files tab.

• Java Edition: open the Minecraft Launcher, go to Installations, and read the version shown on the profile you plan to use. If you have no Forge profile yet, you will create one for 1.20.1 during installation.
• Bedrock on Windows: open Minecraft and read the version number in the bottom-right corner of the title screen.
• Android and iOS: the same title-screen number applies. Your app store may update Minecraft automatically, so recheck after an update before importing a new add-on file.

Write the version down. If the project’s newest file does not list it, look further down the Files history or wait for an update instead of forcing a mismatched file.

Stable release or beta?

The Java project lists both a stable file and test builds. A beta may add features, but it can also change config files, break saves, or require different dependencies. Choose the stable file for a first install, a long-running world, or recording a video. Choose a beta only in a separate profile with a copied world, and read its changelog first. If something breaks, roll back by removing the beta file and restoring your backup, not by mixing two Verity versions in the same mods folder.

Choose Java

Choose Java if you play Minecraft: Java Edition on a desktop system and can manage a Forge or NeoForge profile. The recommended starting point is Minecraft 1.20.1 with Forge. A separate legacy 1.21.1 NeoForge file remains listed. If your goal is simply to get Verity running, do not choose 1.21.1 only because its number is larger.

After opening the project page, use its Files view and filter for your exact Minecraft version and loader. Keep the project page open while installing so you can compare the current requirements. Then continue to the Java installation guide for the clean-profile and AI setup order.

Choose Bedrock or PE

Choose Bedrock if you play Minecraft for Windows, Android, or iOS and the selected project explicitly supports your current game build. “PE” is an older name for Minecraft on mobile; both projects here are listed as Minecraft Bedrock add-ons. Both projects’ current files now target 26.50 (Utlover65 4.2.3, PnTMC 4.0.0), but they were updated on different schedules and will not necessarily support the next Bedrock update at the same time. Check the selected Files tab instead of assuming the two projects share one compatibility rule. For PnTMC on a phone, continue with the Android installation and connection steps.

Do not choose by download count or thumbnail. Match the author and Project ID used by the tutorial, then follow only that project’s requirements. Both require Beta APIs in their current descriptions; Utlover65’s project also documents cheats and a connection step, while PnTMC documents a different interaction flow and warns that its AI can be resource intensive. Continue to the Bedrock / PE guide before testing an important world.

What the downloaded file should look like

Knowing the expected file type is one of the quickest ways to catch a fake download.

• Java: a single .jar file. It is not opened directly; it goes into the mods folder of your Forge or NeoForge profile. Dependencies, if listed, are separate .jar files from their own project pages.
• Bedrock: an .mcaddon or .mcpack file. Opening it on Windows, or choosing “Open with Minecraft” on a phone, starts the import. A Bedrock add-on usually contains both a behavior pack and a resource pack, and both must be active on the world.

A Verity download should not be an .exe installer, an .apk app, a “launcher,” a password-protected archive, or a file that asks you to disable antivirus. If you received one of those, delete it and return to the project page. The online and free-play claims guide explains common fake formats in more detail.

CurseForge, Modrinth, and modpacks are not interchangeable

VarmiteYT’s maintained Verity JE now also has a Modrinth project at /mod/verity-je-official, listed for Minecraft 1.20.1 with Forge. Confirm the title, creator, loader, and description before using it.

Modrinth also lists Verity Java as a separate Minecraft 1.20.1 Fabric project. That same-name project is not the Forge/NeoForge Verity JE project. A different loader, author, feature list, and project page means a different installation decision.

The readable CurseForge address /minecraft/mc-mods/verity-mod also does not identify Verity JE. Our July 20 record identified Verity Remake, Project ID 1587777, at that address; the September 16 lookup returned 404. It is not a current download source. A URL slug can change or disappear, so verify the numeric Project ID instead of following an old address to a mirror.

Modpacks are another project type. They bundle a loader, multiple mods, and configuration rather than providing only the base Verity component. Open the Verity modpack comparison to compare Project IDs 1587394, 1584643, 1596649, and 1589372. Do not use popularity as proof that a pack includes the specific Verity project you intended.

Common download problems and fixes

The Download button opens an app prompt. CurseForge may offer its desktop app. You can use it, or look for the manual file download option on the specific file’s page. Either way, the file comes from the same project.

The file I need is not in the list. The Files tab may default to a filter for the newest game version. Change the game version filter, or scroll to older files. If your version is not listed anywhere, that project does not support it yet.

My browser warns about the file. Browsers often flag any unfamiliar .jar or add-on. Check that the download came from the project’s own file page and that the name and size match what the page lists. A warning on a file from a mirror is a reason to stop, not to bypass the warning.

The download is interrupted or the file is 0 KB. Delete the partial file and download again from the project page. Do not rename a partial file and try to import it.

On mobile, the file opens in the wrong app. Use your file manager’s “Open with” option and pick Minecraft. On iOS, use the Share sheet. If Minecraft shows “Import failed,” check the game version against the file and see the troubleshooting guide.

What to do when the project looks removed

First, determine whether the missing item is one of the three projects identified above or a different same-name upload. Search by author and Project ID, not by the word “Verity” alone. A title can change; a copied title can be reused; search ranking can surface an older or unrelated project.

Next, inspect the project’s Files and changelog areas. A version may be archived, replaced, renamed, or hidden from the default filter while the main project remains available. If the author provides a replacement, follow the link from the original project page rather than a comment claiming to have a backup.

Do not recover a removed release from a shared drive, URL shortener, chat attachment, repost site, or an unknown person’s old mods folder. Removal is not proof that a file was malicious, but an untraceable copy has no reliable source or update history.

Why this guide does not state a universal removal reason

Community discussions contain incompatible explanations for old Verity uploads. Some comments speculate about security behavior; others describe creator disputes or simple project replacement. Repetition does not turn those claims into a statement from the author or a technical analysis. Unless an author or platform publishes a specific explanation for a specific Project ID, the honest status is unconfirmed.

That distinction protects users in both directions. It avoids falsely calling a person or file malicious, and it avoids telling users that an untraceable recovered copy is safe. The useful action remains the same: confirm the author and Project ID, avoid mirrors, and choose a release that matches the current game environment.

Keep your download up to date

Verity projects update often, and Bedrock add-ons in particular track new Minecraft builds. Before replacing a file, back up your world, read the new changelog, and remove the old Verity file instead of keeping both. On Java, keep dependencies at the versions the new file lists. On Bedrock, remove the old packs from the world before activating the new ones, so two versions do not load together. If an update breaks your setup, the previous file usually remains in the project’s Files history.

Before you press download

Confirm the author, Project ID, exact game version, loader or import format, and current setup notes. Use a test profile or world, avoid direct-file reposts, and keep API keys out of websites, chats, screenshots, and logs. The safety guide covers scans, permissions, mirrors, and credential handling in detail.

Once the source and version match, move to the edition-specific install guide. Downloading the right project is only the first part; installation and connection checks belong in the Java, Bedrock, and troubleshooting guides.