01

Step 1: identify the edition

Java Edition is normally launched through the Java launcher or a custom mod launcher on Windows, macOS, or Linux. Bedrock runs on phones, consoles, and Minecraft for Windows. Windows alone does not identify the edition.

02

Step 2: select the project

Choose Verity JE for the current stable Forge 1.20.1 route, Verity Revamped for its separate NeoForge 1.21.1 route, or one Bedrock project for a supported 26.40 world. Record the project ID so another same-name file cannot replace it.

03

Step 3: create an isolated profile or world

For Java, let CurseForge create a new profile with the exact Minecraft version and loader. For Bedrock, back up the world and test on a copy. Isolation makes loader, dependency, script, and configuration failures observable.

04

Step 4: install from the maintainer platform

Use the CurseForge Install action or the exact project Files tab. Do not rename files or copy a Java JAR into Bedrock. Review current relations for the selected release; Revamped explicitly requires GeckoLib.

05

Step 5: verify content before AI

Launch once and confirm the project appears in the Java mod list or the Bedrock packs are active. Load a disposable world and verify the documented entity or interface. Only then choose a provider or project-specific connection path.

06

Step 6: verify AI and voice separately

A text response proves the provider layer works. Voice, speech-to-text, and microphone controls are later layers with separate permissions and fallbacks. Diagnose silence without destroying a working text configuration.

07

Success checklist

A complete install has six signals: correct project, supported game version, correct loader/import method, required relations active, world behavior present, and provider response working. Record the exact versions before adding other mods.

FAQ

Questions

Should I configure Groq before the first launch?

No. First prove that the correct mod or add-on loads. Provider configuration cannot fix a loader or pack failure.

Can I add Verity to an existing large modpack?

Test the exact project in a clean supported instance first, then add other mods in small batches while preserving the working profile.