Verity Mod FAQ

Yes. Verity JE is a public CurseForge project by VarmiteYT with ThatMob listed as an author. CurseForge also hosts separate Bedrock add-on projects. A real listing does not make every mirror or similarly named file safe.

Use the publisher's Verity JE release pages on Modrinth or CurseForge. The current Forge release is available through Modrinth, while the NeoForge option opens its CurseForge file page. Match the Minecraft version, loader, and filename before installing.

The public Verity JE project lists Forge for Minecraft 1.20.1 and an older NeoForge release for Minecraft 1.21.1. Forge has a stable 5.7.4 release and a separate 6.0.0-beta.9 test release. Choose the file made for your exact loader and game version.

Yes. CurseForge lists Verity BE (Official) by Utlover65 and Verity — Bedrock Edition by PnTMC. These .mcaddon projects have separate files and setup instructions. Verity BE 4.2.0 lists Minecraft 26.50, 26.40, and 26.30; PnTMC 4.0.0 offers packages for several Bedrock versions.

The verified Verity JE listing currently names Forge and NeoForge, not Fabric. Do not rename or force-load a Forge JAR in a Fabric profile.

Verity JE supports AI conversations through a configured provider or local Ollama service. Stable 5.7.4 fixes a missing Groq model; the 6.0 test branch expands provider support and connects to Ollama without LiteLLM. Follow the instructions for your installed branch. The project says AI text supports multiple languages, while speech-to-text and text-to-speech were tested only in English.

No. VerityMod.link is an independent download and setup guide. It is not affiliated with Mojang, Microsoft, CurseForge, VarmiteYT, ThatMob, or the add-on developers.

Yes. Use a separate test profile and back up any world you care about before adding a large or unfamiliar mod. A clean profile also makes conflicts easier to diagnose.

Place the unchanged JAR in the mods folder used by the matching Forge or NeoForge launcher profile. Do not put it in resourcepacks, datapacks, or the main Minecraft folder, and do not extract the JAR. If you use a third-party launcher, open that instance's folder from the launcher itself so you do not accidentally modify a different profile.

No. Each release belongs in a separate profile with its own Minecraft version and loader. The current Forge builds target Minecraft 1.20.1, while the older NeoForge build targets 1.21.1. Loading both files together will not combine their features; it creates a duplicate or incompatible-mod problem before a world can load. Install only one Verity JE JAR in each profile.

Remove other newly added mods, confirm the Minecraft and loader versions, and launch a clean test profile with only Verity JE and documented dependencies. If it still fails, read the first relevant error in latest.log or the crash report rather than relying on the final exit code. Keep the report intact when asking for help because the missing-mod or incompatible-class line is often near the beginning.

Copy the world and the entire launcher instance before replacing a file. Read the new release notes for configuration, dependency, or world-format changes, then test the copied save first. Keep the previous JAR or .mcaddon and a note of its version until the update is proven stable. Never open your only copy of a valuable world while experimenting with a new branch.

A successful game launch only confirms the local mod loaded. AI features may still depend on the provider, model, endpoint, key, local Ollama service, microphone permission, or audio device described by the Java project. Recheck those settings without posting a secret key in screenshots or logs. The maintainer says multilingual AI text is supported, but speech-to-text and text-to-speech were tested only in English.

First confirm that the download finished with the .mcaddon extension and was made for your Bedrock version. Open it through Minecraft rather than extracting and rearranging its folders. If Minecraft reports a duplicate pack, remove or deactivate the older copy before importing again. After import, check both Behavior Packs and Resource Packs for the new world and enable only the experiments required by that project.

Compatibility depends on the edition, release, server or realm setup, and any external services the selected project requires. Do not assume that a single-player installation automatically works for every participant. Test with a disposable world, make sure all required sides use compatible versions, and follow the current maintainer's multiplayer notes. Never share an API key, account token, or private endpoint with other players.

Not by itself, but it should stop you from opening the file until you investigate. Confirm the publisher, filename, size, and release record, then scan the untouched artifact. PnTMC documents a separate platform helper in its Bedrock setup guide; obtain that helper only through the maintainer's links, not from a site claiming to convert or install the .mcaddon. Check any security alert before running it. Do not bypass protection for an unrelated or unverified installer. When details do not match, discard that copy and return to the publisher page. Keep the alert name and scan result if you ask for help.