Verity Mod Versions: Java, Forge and Bedrock Compatibility

Current Verity Mod versions

The stable Java route is Verity JE 5.7.4 for Minecraft 1.20.1 with Forge. CurseForge also displayed 6.0.0-beta.9 as a beta file when checked on 2026-09-05. Bedrock has two separate projects: Utlover65 lists 4.1.2 and PnTMC lists 4.0.0, both labeled for Bedrock 26.40.

Those numbers cannot be compared as one release sequence. Bedrock 4.0.0 is not the same file or code line as Java 5.7.4. Each project has its own author, numeric Project ID, file format, supported game build, and setup instructions.

Use the table as a compatibility snapshot, then open the project page before installing. A new upload can appear after the displayed check date.

Edition	Project and ID	Checked release	Game and loader	Status on 2026-09-05
Java	Verity JE, ID 1591438	5.7.4 stable; 6.0.0-beta.9 also listed	Minecraft 1.20.1, Forge	5.7.4 is the main stable file; beta is optional test software
Java	Verity JE, ID 1591438	3.4.1	Minecraft 1.21.1, NeoForge	Separate legacy branch; not the current main stable file
Bedrock / PE	Verity BE (Official), ID 1574632	4.1.2	File metadata lists Bedrock 26.40	Current file, but setup copy still says 26.30; verify before import
Bedrock / PE	Verity - Bedrock Edition, ID 1575941	4.0.0	Bedrock 26.40 add-on	Current file for this project

Verification history

This log records what the linked project pages displayed on each check date. A row is added only after those pages are opened and compared; unchanged builds do not receive a made-up historical entry.

Checked	Project ID	Version observed	Change from the previous recorded snapshot	Source result
2026-09-05	1591438	5.7.4 main file; 6.0.0-beta.9 also listed	Stable unchanged; beta updated, released September 3	Maintainer page snapshot
2026-09-05	1574632	4.1.2 for 26.40	New release dated September 1; setup copy still says 26.30	Maintainer page contains a version-label conflict
2026-09-05	1575941	4.0.0 for 26.40	File unchanged; linked setup guide now checked for local AI connection requirements	Maintainer page and linked platform instructions
2026-08-25	1591438	5.7.4 main file; 6.0.0-beta.7 also listed	Stable and beta listings changed	Maintainer page snapshot
2026-08-25	1574632	4.0.0 hotfix for 26.40	Current file changed; setup text still says 26.30	Maintainer page contains a version-label conflict; verify the Files tab
2026-08-25	1575941	4.0.0 for 26.40	Current release changed from 3.2.0	Maintainer page snapshot
2026-08-11	1591438	5.7.3 main file; 6.2 Beta 1 also listed	Beta file added after the prior page snapshot	Maintainer page snapshot
2026-08-11	1574632	2.0.1 file labeled 26.40	Changed from the previously documented 1.1.0 / 26.30 route	Maintainer page contains a version-label conflict; verify the Files tab
2026-08-11	1575941	3.2.0 file for 26.40	Game-build association changed from the previously documented 26.30 route	Maintainer page snapshot

The three project pages listed in Sources below are the evidence for this snapshot. The labels above describe what those pages displayed at the time.

What outside demonstrations confirm

The Verity JE project page links to a setup tutorial and a recorded playthrough. Those maintainer-controlled videos show the project being configured and running in the creator’s environment. They demonstrate the intended setup and gameplay, but a recorded configuration cannot establish compatibility with every device, loader build, provider, or later release.

An independent macOS walkthrough records a NeoForge 1.21.1 installation of Verity JE 3.4.1 and includes screenshots from that loader setup. Its author also says the in-game AI screenshots were still pending. That makes it useful evidence for the legacy installation path, not proof that Groq, Ollama, speech, or the current Forge 5.7.4 release worked in the same run.

These sources are most useful when their limits stay visible. A maintainer demonstration shows intended behavior; an independent walkthrough can confirm a specific environment; neither should be stretched into a blanket compatibility claim.

Why the Project ID matters

The title “Verity Mod” is not a unique identifier. Search results can show Java mods, Bedrock add-ons, modpacks, remakes, old uploads, and projects with reused or similar names. A thumbnail can also be copied or changed.

The numeric Project ID is more reliable:

• 1591438 identifies Verity JE by VarmiteYT.
• 1574632 identifies Verity BE by Utlover65.
• 1575941 identifies Verity - Bedrock Edition by PnTMC.

Confirm the author and Project ID together. The number tells you which project page you are reading, while the author and project description tell you who maintains that implementation. If a tutorial names one ID but links to another, stop and resolve the mismatch before downloading.

This website links to project pages rather than package files. The project page shows the latest release, file history, supported versions, and maintainer notes that a direct link can hide.

Java: stable 5.7.4 and beta 6.0.0-beta.9 on Forge 1.20.1

Verity JE’s main stable file was 5.7.4 for Minecraft 1.20.1 with Forge, released on 2026-08-18 when checked. CurseForge also listed 6.0.0-beta.9, dated 2026-09-03. CurseForge lists the environment as client and server, while Modrinth identifies the maintained project as Minecraft 1.20.1 with Forge.

Choose 5.7.4 when you want the stable route shown as the project’s main file. Use 6.0.0-beta.9 only in a separate test profile when you deliberately want to evaluate a prerelease and can roll back. Create a Forge 1.20.1 profile, launch the empty loader once, and install only one Verity release plus dependencies listed for that file. Continue with the Java Edition setup guide for Groq or Ollama configuration.

Match the exact Minecraft version instead of choosing “latest Minecraft.” A mod built for 1.20.1 is not made compatible with 1.21.x by placing it in a newer profile. Minecraft, loader, mod release, and dependencies must target the same environment.

If a launcher offers several Forge builds for 1.20.1, follow the maintainer’s current file details and dependency requirements. Prefer that current information when an older video shows a different loader build.

Java: the NeoForge 1.21.1 branch

Verity JE also listed 3.4.1 for Minecraft 1.21.1 with NeoForge, released on 2026-06-30. It is a separate legacy release, not a port of the current Forge stable file.

That means the file exists, but it is not the recommended starting point. Use it only when you understand the limitation and need compatibility with an existing 1.21.1 NeoForge setup. If you are trying Verity for the first time, use the Forge 1.20.1 main route.

Keep the NeoForge file in a NeoForge profile. Forge and NeoForge are separate loaders, and a launcher folder named “1.21.1” does not prove the correct loader is active.

When reporting a 1.21.1 problem, reproduce it on a clean profile and state that you are using the legacy branch. If the same action works on 1.20.1 Forge, the difference is useful evidence of a branch-specific problem.

Is there a Fabric version?

Verity JE by VarmiteYT does not list Fabric. Its checked loaders are Forge for 1.20.1 and NeoForge for the legacy 1.21.1 branch.

Separate same-name Fabric projects can appear on hosting platforms. They may have different authors, features, files, permissions, and support channels. A Fabric result is not a Fabric build of Project ID 1591438 unless the Verity JE maintainer links it as such.

If your modpack requires Fabric, choose a project built for Fabric or make a separate supported Forge profile. Renaming a Forge file or using an undocumented loader bridge does not make the loaders interchangeable.

Bedrock: Verity BE 4.1.2 by Utlover65

Verity BE by Utlover65, Project ID 1574632, displayed 4.1.2 for Bedrock 26.40, dated 2026-09-01. On the 2026-09-05 check, the project listed 26.40, 26.30, and 26.20, while the setup description still said 26.30. That is a source-page conflict, so verify the exact file details before importing it.

This project requires Beta APIs and cheats for its documented setup. Its current description instructs users to complete a connection command and begin chat with Verity followed by the message. It also documents ... as a connection or backend symptom.

Keep that connection method with Utlover65’s project. The two Bedrock add-ons are separate even though both adapt Verity and currently show files labeled for Bedrock 26.40.

If your Minecraft build is 26.20 or 26.30, select a file explicitly listed for that build rather than installing the current file based only on its name. The latest project version is not automatically compatible with an older game build.

Bedrock: PnTMC 4.0.0 for 26.40

Verity - Bedrock Edition by PnTMC, Project ID 1575941, listed version 4.0.0 for Bedrock 26.40, released on 2026-08-20. The project page says it requires version 26.10 or newer and Beta APIs, but the Files area still provides the exact build association for each release.

PnTMC documents nearby chat when Verity is on the ground and Hey Verity when it is in inventory. Its current description links a separate setup guide for AI and speech. The previously documented /verity_language command is not repeated in that current guide, so do not assume it applies to 4.0.0.

Version 4.0.0 belongs only to this project. Treat it and Utlover65’s 4.1.2 as separate release lines rather than comparing their release numbers, then choose by the author, Project ID, gameplay, and tutorial you intend to follow.

For this release, continue with the device-specific Bedrock setup steps. They cover the local connection helper before conversation or microphone troubleshooting. Open the project page before installation even when this table looks current.

Bedrock 26.40, 26.30, and displayed version labels

The Utlover65 project description still described the required game version as “Minecraft 1.26.30 (a.k.a. 26.30)” while its current file metadata listed 26.40. Bedrock’s displayed version labels can vary by page or context, but conflicting labels on one project page are a reason to pause and compare the full release shown in Minecraft with the selected file’s details.

Check the edition before comparing numbers. Java 1.20.1 is unrelated to Bedrock 26.20, and Java 1.21.1 is unrelated to a Bedrock build beginning with 1.21. Similar numbers do not indicate compatible code or files.

If your device updated Bedrock automatically, check the exact new build before opening an important world. A creator API change can affect an add-on even when the pack still imports.

Does Verity work on PE, mobile, or Windows?

“Pocket Edition” or “PE” is an older name commonly used for Minecraft on mobile. Current Android and iOS Minecraft releases use Bedrock Edition. A Bedrock add-on can be relevant to mobile, but device support still depends on the current project, game build, import method, and available experimental settings.

Minecraft for Windows is also Bedrock Edition, but it is separate from Java Edition. Check the title screen and launcher entry instead of choosing by operating system alone.

Console installation has different restrictions. Use only methods supported by the device and current Minecraft platform; a mobile file-manager tutorial or Windows import step may not apply.

Versions not confirmed by the maintained projects

The checked maintainer pages do not establish a supported Verity JE route for Fabric, Eaglercraft, Minecraft Education, browser-based “online” Minecraft, or arbitrary newer Java versions. Separate projects or simulations may use the name Verity, but that does not make them builds of IDs 1591438, 1574632, or 1575941.

Treat a claim as unverified when it lacks all of the following:

• A maintainer-controlled project page.
• A matching Project ID and author.
• An exact game version.
• A loader or Bedrock import type.
• A release date and file history.
• Instructions for that same project.

Use a maintainer project page rather than a renamed package from a shared drive. A name in a filename is not provenance.

How to check compatibility before downloading

Use this six-step check:

1. Identify the edition. Confirm Java or Bedrock from the launcher or title screen.
2. Identify the project. Match title, author, and numeric Project ID.
3. Read the game version. Match every part of the version, not only the first two numbers.
4. Match the loader or format. Java needs Forge or NeoForge as listed; Bedrock uses an add-on and active world packs.
5. Read the current release notes. Check dependencies, experiments, connection steps, and known warnings.
6. Use a test environment. Create a separate profile or new world before touching a save you care about.

If one item does not match, stop. Installing first and diagnosing later costs more time than checking the project page.

Updating an existing Java profile

Back up worlds and record the working Verity release, Minecraft version, loader, dependencies, provider, and model. Then check whether the new file targets the same game and loader.

Remove the old Verity file from the test profile before adding the new one. Duplicate versions can create loader conflicts. Update dependencies only when the new release requires them, and launch a new test world before opening a long-running save.

Test in this order: Minecraft launch, world load, Verity appearance, typed conversation, provider response, then voice. If something fails, the first failed step tells you which setting to inspect.

Upgrade Minecraft and Verity in separate tests when possible. Changing one variable makes rollback and diagnosis much easier.

Updating a Bedrock world

Duplicate the world first. Record the active pack version and required experimental settings. Remove old pack revisions from the duplicated test world, import the release that matches the current Bedrock build, and confirm both behavior and resource components are Active.

Create a separate new world with the same packs. If the new world works and the copy of the old world does not, the problem is likely in world state or the update path rather than the basic add-on release.

Keep the published manifest version. Changing its number cannot make incompatible scripts or creator APIs work together.

What about modpacks?

A Verity modpack has its own version and can include a particular Verity release, loader, dependencies, configuration, and unrelated mods. The pack’s version number does not replace the included Verity project’s version number.

Open the Verity modpack guide and inspect the pack author, Project ID, Minecraft version, loader, included projects, and update date. Confirm which Verity project and release it contains. A pack can simplify setup, but it also adds more files that can conflict.

When a pack fails, test the maintained standalone Verity route in a clean profile. That comparison tells you whether the base project works and whether the pack adds the problem.

Keep a known-good record

After Verity works, save a short text note with the edition, Project ID, Verity release, Minecraft build, loader, dependency versions, provider, model, and date. Keep the Groq key out of that note.

This record is more useful than “I used the latest version.” When a future update arrives, compare the new environment with the known-good one. If only one item changed, you have a clear rollback point and a useful support report.