A Java JAR is not a Bedrock add-on
A Java JAR belongs in a Java launcher profile with the matching Minecraft version, loader, and
dependencies. It does not import into MCPE, Bedrock mobile, PS4, Xbox, Switch, or a Bedrock Realm.
If a video tells you to place a ZIP or JAR in the mods folder but your game is Bedrock, that
instruction is for the wrong platform. Move back to the route map and pick a .mcaddon source.
The opposite mistake also happens. A Bedrock .mcaddon can look like a mod download, but it is
not a Forge or NeoForge mod. Do not put the PnTMC, Verity BE, or Pocket Edition package in a
Java mods folder and expect the launcher to load it.
Similar names do not prove the same project
Search results include Verity JE, Verity BE, Verity - Bedrock Edition, Verity Pocket Edition
(Be), VERITY.exe, Ultimate VERITY, app-store listings, and unrelated mirrors. Treat the name as
a clue, not proof. A reliable route should name the owner, Project ID or version ID, file record,
file type, size, supported Minecraft build, update date, and final maintainer page.
Voice and AI errors are not always file errors
A working install can still fail when the AI provider, key, model, rate limit, microphone path,
resource pack, or command setup is wrong. If Verity appears but says API connection failed,
diagnose 401, 429, OpenRouter, Groq, or Ollama before replacing the file. If Verity appears but
does not talk, separate chat response from audio output and check the page for your edition.
Old tutorials can still point to old records
PnTMC 2.1.0 records 8327253, 8327250, and 8327242 are old Bedrock rows. They may matter for an
older world or video, but they are not the default fresh-install route now. Java users may also
find older exact file names such as verity-3.4.1.jar. Use old records only when the
tutorial, world, server, or loader version specifically requires them.