Verity mod compatibility: verified release facts

Compatibility claims should be tied to a specific release, not to the project name alone. The public Verity-CE release currently reviewed by this site identifies Minecraft 1.21.1 and NeoForge in both its tag and asset name. That is the narrow compatibility statement supported by the public record.

Current documented combination

The release tag is neoforge-1.21.1-1.0b(ce), and the attached asset is named verity-ce-1.0b-mc1.21.1-neoforge.jar. The repository README also describes Minecraft 1.21.1 adaptation and GeckoLib 4.9.1 work.

Together, those sources support using 1.21.1 and NeoForge as the starting point for this release. They do not guarantee that every NeoForge build works, that every dependency is bundled, or that the release will remain unchanged. Read the current release notes before installing.

What is not established by the public release

The public community repository does not provide primary-source installation evidence for these combinations:

| Edition or loader | What the reviewed source establishes | | --- | --- | | Minecraft Java 1.21.1 + NeoForge | Named by the current release tag and asset | | Lunar Client | Not documented as a supported path by the reviewed repository | | Fabric | Not named by the current public release asset | | Forge | Do not treat NeoForge and Forge as interchangeable without project documentation | | Vanilla Java | A loader-specific JAR is not a vanilla installation path | | Bedrock Edition | A Java JAR is not a Bedrock add-on package | | Older Minecraft versions | Not established by the current public release |

This does not prove that no historical or unrelated Verity build ever used another platform. It means this site does not have enough current primary evidence to publish those combinations as working installation instructions.

Quick answer by the route you found

If you arrived from an old install URL, use the route name only as a description of the question you searched. It is not proof of support.

| Route or search | Current answer from the reviewed evidence | | --- | --- | | Verity mod 1.21.1 NeoForge | This matches the current public release label; verify the exact release and dependencies | | Verity mod 1.21 Lunar Client | The reviewed community repository cannot verify this separate distribution claim | | Verity mod 1.20.1 Lunar Client | Historical references may exist, but current primary evidence is required | | Verity mod Bedrock | The reviewed release is a Java JAR, not a Bedrock package | | Verity mod Fabric | The current public asset is labeled NeoForge, not Fabric | | Verity mod vanilla | A loader-specific JAR is not a loader-free vanilla install |

The retained install pages explain these evidence boundaries without redirecting visitors to an unverified download. If you have another file, return to the original source that published it and use that source's compatibility documentation.

Why search results can disagree

Search results may combine the original project, community editions, removed listings, cached snippets, video tutorials, and unrelated projects with the same name. A page can remain indexed after its download or instructions become outdated.

Resolve the disagreement by asking which repository or platform published the exact file. Then check that source's current release notes. Do not combine a JAR from one project with instructions written for another project simply because both use the word Verity.

How to evaluate a new release

Use the release tag, asset filename, README, and dependency notes together. All four should agree on the Minecraft version and loader. If one source differs, pause and investigate the discrepancy before moving the JAR into a normal profile.

Create a separate test instance with the named loader. Keep the loader log and add only documented dependencies. If the release requires a different loader or Minecraft version in the future, create a new instance rather than converting a working one in place.

NeoForge is not a generic label

Forge and NeoForge share history and concepts, but a release labeled NeoForge should be tested with the documented NeoForge environment. Copying it into Fabric, vanilla, Bedrock, or an unspecified Forge profile is not a compatibility test; it is a different setup.

The same rule applies to dependencies. A library version that works for one Minecraft and loader combination may not work for another. Use the version specified by the current project documentation.

Compatibility checklist before launch

Write down the Minecraft version, loader name and version, release tag, asset filename, and documented dependency versions. These values should describe one coherent release. If they were copied from different tutorials, stop and rebuild the checklist from the primary source.

Use a new test instance instead of converting an existing profile between Fabric, Forge, NeoForge, or vanilla. Loader configuration and cached files can survive a simple JAR swap, so a failed converted profile is weaker evidence than a clean test.

After the first launch, keep the complete loader log. A successful menu load proves only that the loader completed; it does not prove that every API-backed function, story claim, or third-party integration is available.

When a future release changes the answer

Compatibility is release-specific. A future asset may name a different Minecraft version, loader, dependency, or configuration format. When that happens, the new release should get its own test record instead of silently replacing the evidence for this one.

Search snippets and third-party tutorials can lag behind a release change. Check the date and release tag even when a result ranks highly. This page's last review is a reference point, not a substitute for the current project page.

Source boundary

The repository README says the community edition is based on a decompiled original and includes version adaptation, API changes, and bug fixes. Those statements describe the community project. They should not be projected onto a different original build or used as evidence that a third-party launcher distributes the same artifact.