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 Verity JE project and file pages on CurseForge. Check the owner, Project ID 1591438, Minecraft version, loader, filename, upload date, and changelog before installing.

The public Verity JE project currently lists Forge for Minecraft 1.20.1 and NeoForge for Minecraft 1.21.1. The project warns that its NeoForge 1.21.1 branch is deprecated and has many bugs.

Yes. CurseForge currently lists independent .mcaddon projects including Verity BE by Undertaletalelover and Verity — Bedrock Edition by PnTMC. They are separate from the Java JAR and require their own setup instructions.

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.

The Java project describes Groq-powered AI and also documents a local Ollama setup. Its page 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 build targets Minecraft 1.20.1, while the listed NeoForge build targets 1.21.1 and is marked deprecated by the project. Loading both files together will not combine their features; it creates a duplicate or incompatible-mod problem before a world can load.

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 that the download came from the expected CurseForge project and file page, compare its name and size with the listing, and scan the untouched artifact. Check whether the maintainer has acknowledged the same detection before making an exception. Do not bypass protection for an EXE or script claiming to be a mod installer. When details do not match, delete that copy and return to the publisher record. Keep the alert name and scan result if you ask for help.