Verity Mod Versions: Java, Forge and Bedrock Compatibility

Current Verity Mod versions

The stable Java release is Verity JE 5.7.4 for Minecraft 1.20.1 with Forge. CurseForge still displayed 6.0.0-beta.9 as the newest test build when checked on 2026-10-18. For Bedrock, both projects now have a 26.50 file: Utlover65 moved to 4.2.3 (October 18) after the 4.2.0 lighting update, and PnTMC’s 4.0.0 has had a 26.50 file since September 17. Check the project as well as the release number before updating Minecraft.

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-10-18
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.2.3	Bedrock 26.50 add-on	Current main file, dated October 18
Bedrock / PE	Verity BE (Official), ID 1574632	4.1.3	Bedrock 26.40 add-on	Previous line; keep only if your device is still on 26.40
Bedrock / PE	Verity - Bedrock Edition, ID 1575941	4.0.0	Bedrock 26.50 add-on	Current file, released September 17
Bedrock / PE	Verity - Bedrock Edition, ID 1575941	4.0.0	Bedrock 26.40 add-on	Older game-build file; do not confuse it with the 26.50 upload

Which version should you choose?

Most players need one of four answers. Find the row that describes your situation:

Your situation	Recommended choice	Why
First time on Java, any PC	Verity JE 5.7.4, Forge 1.20.1	Main stable file with the most setup documentation
Want to test new Java features	6.0.0-beta.9 in a separate profile	Prerelease; keep 5.7.4 as a fallback
Existing NeoForge 1.21.1 pack	Verity JE 3.4.1	Only file for that loader; legacy branch
Bedrock on 26.50, least setup	Utlover65 4.2.3	No helper program; connection step and chat trigger only
Bedrock on 26.50, own AI keys and voice	PnTMC 4.0.0, 26.50 file	Local helper on the same device with your Groq and FishAudio keys
Bedrock still on 26.40	Utlover65 4.1.3 or PnTMC 4.0.0 (26.40 file)	Older files; update Minecraft and the add-on together when you can

If none of these rows describes your setup, for example Fabric, a browser-based version, or Minecraft Education, read Versions not confirmed by the maintained projects before searching for an alternative file.

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-10-18	1591438	5.7.4 main file; 6.0.0-beta.9 also listed	Unchanged	CurseForge listing
2026-10-18	1574632	4.2.3 for 26.50	4.2.0 for 26.50 added October 5; 4.2.3 main file dated October 18	CurseForge listing; 4.2.0 notes on MCPEDL; 4.2.3 changelog not available
2026-10-18	1575941	4.0.0 for 26.50	Unchanged	CurseForge listing
2026-10-01	1591438	5.7.4 main file; 6.0.0-beta.9 also listed	Unchanged	Maintainer project listing
2026-10-01	1574632	4.1.3 for 26.40	Unchanged; setup copy still says 26.30	Maintainer project listing and Files tab
2026-10-01	1575941	4.0.0 for 26.50	New game-build file dated September 17, without a new add-on version number	File 8902437
2026-09-16	1591438	5.7.4 main file; 6.0.0-beta.9 also listed	Unchanged	Maintainer project listing
2026-09-16	1574632	4.1.3 for 26.40	New main file dated September 16; setup copy still says 26.30	Maintainer project listing; changelog not verified
2026-09-16	1575941	4.0.0 for 26.40	Unchanged	Maintainer project listing
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 the release pattern tells you

The history shows three different update rhythms. Verity JE keeps one stable main file and updates a beta line alongside it, so a newer beta does not mean the stable file is outdated. Utlover65 publishes frequent add-on revisions, from 2.0.1 in August to 4.1.3 in September and 4.2.3 in October, and its description text has often lagged behind the file metadata. PnTMC uploads a new file for each game build but can reuse the add-on number, as it did with 4.0.0 for both 26.40 and 26.50.

In practice, this means:

• Java: check whether the file is marked Release or Beta, not just which number is higher.
• Utlover65 Bedrock: trust the selected file’s game-version metadata over the description paragraph.
• PnTMC Bedrock: match the game build in the file title, because the add-on number alone may be the same across builds.

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.

Stable versus beta: how to test safely

A beta file is published so players can try changes before they become the main release. It can include new behavior, changed configuration keys, or unfinished features. That is useful if you want to help test, but it is not the right base for a long-running survival world.

To test a beta without risking your stable setup:

1. Duplicate your working 5.7.4 profile, or create a new Forge 1.20.1 profile with its own game directory.
2. Replace only the Verity file with 6.0.0-beta.9 in the copy. Leave dependencies unchanged unless the beta file lists different requirements.
3. Create a new world in the test profile instead of opening an existing save.
4. Check whether the configuration file was regenerated or changed. Re-enter the provider settings if needed, without copying your Groq key into shared screenshots.
5. If you report a problem, include the exact beta number and say that the same action works or fails on 5.7.4.

Separate game directories also keep config files and logs apart, which makes it clear which file produced each result.

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.2.3 by Utlover65

Verity BE by Utlover65, Project ID 1574632, displayed 4.2.3 for Bedrock 26.50 as its main file on 2026-10-18. The 4.2 line began with 4.2.0 on October 5, the first Utlover65 file for 26.50. A changelog for 4.2.3 was not available when this page was checked, so no specific fixes are claimed for it.

The 4.2.0 notes published on MCPEDL describe a visual update rather than new conversation features:

• Colored light from torches, lanterns, candles, and other light sources.
• Reworked materials on Verity’s box, the chest version, the Smiler, and the flashlight, so the models react to light, plus new shading on Verity and the chest version.
• Looser game-version check: the add-on is described as running on Minecraft 1.26.0 or higher instead of one exact build.
• Graphics requirement for the new lighting: Vibrant Visuals or ray tracing must be turned on, together with Beta APIs in the world.

Two practical consequences follow. First, if your device cannot run Vibrant Visuals, expect the add-on to look like the 4.1 line rather than the screenshots in the 4.2 announcement; that is a graphics limitation, not a broken import. Second, “1.26.0 or higher” describes the author’s intent, not a promise for future builds. When Minecraft moves past 26.50, check whether the Files tab lists the new build before updating an important world.

This project still requires Beta APIs and cheats for its documented setup. Its description instructs users to complete a connection command and begin chat with Verity followed by the message, and it documents ... as a connection or backend symptom. Keep that connection method with Utlover65’s project: both Bedrock add-ons now target 26.50, but PnTMC’s local helper and /connect 127.0.0.1:3000 step do not apply here.

If your device is still on 26.40, the older 4.1.3 file (September 16) was the most recent Utlover65 file for that build in our checks. For 26.20 or 26.30, select a file explicitly listed for that build.

Bedrock: PnTMC 4.0.0 for 26.50

Verity - Bedrock Edition by PnTMC, Project ID 1575941, lists version 4.0.0 for Bedrock 26.50, released on 2026-09-17 as file 8902437. Its older 4.0.0 file targets 26.40. The add-on number stayed the same, so looking only for “4.0.0” is not enough: match the game version in the file title and details.

The project description’s broad “26.10 or newer” statement is not a substitute for the selected file’s compatibility metadata. If Minecraft updated to 26.50, use the matching PnTMC file and a copied world. If you are staying on 26.40, keep the matching older file instead of importing the newer package just because both say 4.0.0.

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.2.3 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, or the complete Android Termux and local-helper guide. 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.50, 26.40, 26.30, and displayed version labels

In the September and October 1 checks, the Utlover65 description still described the required game version as “Minecraft 1.26.30 (a.k.a. 26.30)” while its file metadata listed 26.40. That history is a good example of why the selected file’s details matter more than the description paragraph. Bedrock’s title screen shows the long form (for example 1.26.50), while project pages usually write the short form (26.50); compare the last two parts of the number.

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.

How to find your exact Minecraft version

Before choosing a file, read the version from the game rather than from memory:

• Java Edition: the bottom-left corner of the title screen shows the Minecraft version and, in a modded profile, the loader name. The launcher’s installation list also shows the version and loader for each profile.
• Bedrock on Windows, Android, or iOS: the version number appears in the bottom-right corner of the title screen. Settings also shows it under the general or profile area, depending on the build.
• Automatic updates: app stores can update Bedrock overnight. If an add-on suddenly stops working, compare the title-screen number with the one you recorded when it last worked.

Write down the full number, including every segment. “26.4” or “1.20” is not specific enough to pick a file.

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.

Common version mismatch symptoms

A version mismatch shows up at specific points. Use the symptom to find the mismatch:

Symptom	Likely mismatch	What to check
Launcher crashes before the title screen	Wrong loader or Minecraft version for the Java file	Profile version, Forge versus NeoForge, duplicate Verity files
Forge reports missing or incompatible mods	Dependency version does not match the Verity release	Required dependencies listed on the selected file
Bedrock pack imports but Verity never appears	Pack built for a different game build, or experiments off	Game build, Beta APIs, both packs Active
Verity appears but replies with ... or nothing	Connection or provider issue, not usually a version problem	Connection command, helper, API key, model
Worked yesterday, broken today on Bedrock	Automatic game update	Title-screen version against the file’s listed build

For full step-by-step fixes, use the Verity not working guide or the crash troubleshooting guide.

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.

Rolling back to a previous version

If an update breaks a working setup, rolling back is usually faster than debugging the new release.

Java: open the project’s Files tab, find the release from your known-good record, and download that exact file. Remove the newer Verity jar from the mods folder, add the older one, and restore the config file you backed up if the new release changed it. Open a copy of your world first, because some mods write data that an older release may not read.

Bedrock: remove the newer pack from the duplicated world, delete the newer revision from global resources and behavior packs if both are installed, then import the file listed for your game build. Two revisions of the same pack can override each other in confusing ways.

If Bedrock itself updated and the older add-on file only lists the previous build, a rollback of the add-on cannot fix it. Wait for a file that lists your new build, or use the other maintained project if it already has one.

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.

Versions on servers and multiplayer

On a Java server, the server and every player must run the same Verity release, Minecraft version, and loader. A client on 5.7.4 and a server on 6.0.0-beta.9 can fail to connect or behave inconsistently. On Bedrock, the world host’s active packs are sent to players, but the game build still has to match the file. See the Verity multiplayer guide for server setup.

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.