CurseForge intent checked July 24, 2026
A CurseForge search for Verity can show Java mods, Bedrock add-ons, old file records, and separate modpack pages. The useful question is not only where the button is. The useful question is whether the page matches your Minecraft edition, the project owner, the Project ID, the file type, and the record number named by the guide you followed.
Route map
This is the route for a Java launcher profile. The current checked Forge file is verity-5.7.3.jar for Minecraft 1.20.1. The CurseForge Project ID is 1591438, and the current checked file record is 8461257.
This is a Bedrock add-on route, not a Java mods-folder route. The current checked file is Verity (Stable) (1.0.9)-(26.3).mcaddon for Bedrock 26.30. Its Project ID is 1574632, and the checked file record is 8486588.
PnTMC's page is a separate Bedrock adaptation. Use it when the video, tutorial, or project page you followed names PnTMC or ThatMob's Verity 2.1.0. Its Project ID is 1575941, and the checked current record is 8327253.
Why results conflict
CurseForge hosts many Minecraft project types. A Java mod page, a Bedrock add-on page, and a modpack page can all be legitimate platform pages, but they do not answer the same player problem. If you use Java Edition, the file must match your loader and go into a Java profile. If you use Bedrock or MCPE, the package imports into Minecraft as an add-on and then needs behavior and resource packs activated in world settings. Those steps are not interchangeable.
This matters because trending video titles and short social posts often compress every route into one name. A player may search for Verity Mod, click the first familiar page, and download a file that belongs to a different edition. Another player may search for a CurseForge result after seeing a Bedrock tutorial and accidentally land on Verity JE. Both users are using a known host, but the host alone does not tell them which project they selected.
File record comparison
| Route | Checked public record | Use it when |
|---|---|---|
| Verity JE file record | Project ID 1591438, record 8461257, verity-5.7.3.jar, Forge 1.20.1 | You are installing a Java mod and can match Forge for Minecraft 1.20.1. |
| Verity JE Modrinth mirror check | Project on1Y0osD, version yAt0wv1Z, same Java filename and publisher checksums | You want an independent platform record and checksum for the current Java file. |
| Verity BE file record | Project ID 1574632, record 8486588, Bedrock 26.30 MCADDON | You are installing Undertaletalelover's Bedrock route. |
| PnTMC Bedrock file record | Project ID 1575941, record 8327253, ThatMob's Verity 2.1.0 V26.30 | You followed a PnTMC or ThatMob Bedrock tutorial and need that exact branch. |
| VERITY.exe and modpack searches | Separate modpack or Windows-file intent, not the standalone Java or Bedrock add-on route | You searched for an executable or a CurseForge profile rather than a single mod file. |
Practical install choice
The app is useful when you intentionally want a managed profile, dependency handling, or a modpack flow. It can reduce mistakes for players who already use CurseForge profiles. It does not remove the need to choose the right project. A Java profile still needs the matching loader, and a Bedrock add-on still needs a Bedrock-compatible import path.
If your goal is only to verify a file mentioned in a video, open the exact record page in the browser first. Read the owner, record number, game version, and file type before installing. Then use the app or browser route that makes sense for your edition.
Stop when the final page changes from CurseForge to a short-link chain, asks for a password archive, offers an EXE for a normal JAR or MCADDON install, or hides the owner and version history. A repost can copy a popular name while losing the project evidence that matters.
If the file already exists on your computer, use the local checker to inspect extension, filename, source text, and SHA-256 without uploading the file. That check cannot prove safety, but it can catch obvious route mismatches before you put the package into a Minecraft profile or a Bedrock world.
FAQ
Because Verity-related searches include a character, a Java project, two common Bedrock add-on routes, modpack searches, old slugs, and mirrors. The name alone is not enough. Use the category, Project ID, owner, file type, and record number to decide.
No. The Java route is a JAR for a Java launcher profile. Bedrock and MCPE need an MCADDON or MCPACK-style route, then world-level pack activation. Use the Bedrock guide if you are not running Java Edition.
No. A higher Minecraft version or newer-looking branch can still be a legacy, test, or deprecated route. For Java, the older NeoForge 1.21.1 branch remains separate from the current Forge 1.20.1 file. Match the route named by your setup, not only the largest version number.
No. This page routes players to public project records and keeps a machine-readable release snapshot at verity-releases.json. It does not mirror CurseForge or Modrinth downloads, and it does not ask for API keys.