Quick answer: Java needs the matching loader and dependencies.
For the current Java route, verify Verity JE by VarmiteYT on its CurseForge project page (ID 1591438). The listing has had different game-version branches, so the filename alone is not enough evidence.
Java installation order
- Create a clean Minecraft profile matching the file’s stated version.
- Install the stated loader, such as Forge or NeoForge, only if the file notes say so.
- Install every required dependency in the same profile.
- Place the JAR in that profile’s
modsfolder. - Launch a new world and check the Mods list before using an existing save.
Common Java mismatch
A Forge file will not necessarily load under Fabric or NeoForge; a 1.20.1 file is not automatically compatible with 1.21. Do not select the newest-looking file without checking the listing’s supported game version.
Java compatibility record
Two Java branches, two different decisions
verity-5.7.3.jarUse only with a matching Forge profile.verity-3.4.1.jarAuthor labels this branch deprecated and bug-prone.What this means in practice
Do not choose the 1.21.1 branch simply because its game number is newer. The project page explicitly warns that its NeoForge build has many bugs. For a first attempt, the evidence supports checking the active Forge 1.20.1 release first, then following its current setup tutorial and dependency notes.
AI and privacy boundary
The Java project says it uses Groq for its AI companion and also mentions a fully local Ollama route. Those are different configurations. Treat any API key as private: only enter one into the setup flow you have independently verified from the maintainer’s own documentation; never submit it to ModCheck or an unrelated download page.
Source record: Verity JE by VarmiteYT, Project ID 1591438. The listing publishes the version/loader pairs and the NeoForge warning.
LOCAL GUIDE
Need the Brazilian Portuguese Java/Groq path?
This guide addresses a separate Brazilian query cluster around Verity JE and Groq configuration.