Verity Mod Java vs Bedrock: Which Edition?

Short answer

Choose Verity JE if you play Minecraft: Java Edition and can run a Forge or NeoForge profile on a desktop computer. For Minecraft: Bedrock Edition, including supported Windows and mobile builds, choose between Verity BE by Utlover65 and Verity - Bedrock Edition by PnTMC using the author and Project ID. Do not choose based on which screenshot looks newer.

All three projects adapt the Verity horror-companion idea, but they are not interchangeable releases from one codebase. Java and Bedrock use different game engines, packaging, scripting or mod APIs, version schemes, world settings, and support channels. The two Bedrock adaptations also differ from each other.

In practice, the question is rarely “which Verity is better?” It is “which Minecraft do I already run, and which AI setup can I maintain?” Answer those two questions first and the right project usually becomes obvious.

Start by identifying your edition

Many failed installs begin with a player who is not sure which Minecraft they own. A few quick checks settle it:

• Title screen text. Java shows “Minecraft: Java Edition” and a version such as 1.20.1 in the lower-left corner. Bedrock shows a version with a different numbering style and no Java label.
• Launcher. Java profiles are created in the Minecraft Launcher (or a third-party launcher such as Prism or CurseForge) and can be pointed at Forge or NeoForge. Bedrock on Windows starts as its own app with a Marketplace button.
• Device. Phones and tablets run Bedrock. Consoles run Bedrock with stricter add-on rules. Java runs on Windows, macOS, and Linux desktops.
• Store purchase. Modern PC purchases include both editions, so owning both is common. In that case, choose the edition you want to play Verity in rather than the one you open most often.

If you own both on PC, the deciding factors move to AI setup and troubleshooting comfort, covered below.

Side-by-side comparison

Decision	Verity JE	Bedrock adaptations
Minecraft product	Java Edition	Bedrock Edition, including supported Android and iOS builds
Project	Verity JE by VarmiteYT	Verity BE by Utlover65; Verity - Bedrock Edition by PnTMC
Project ID	1591438	1574632; 1575941
Game version to match	1.20.1 Forge	The Bedrock build named on the selected file
Other supported setup	1.21.1 NeoForge, legacy 3.4.1	Both list older Bedrock builds; match the chosen project’s file history
Package model	Java mod loaded by Forge or NeoForge	Bedrock behavior and resource packs imported as an add-on
AI option	Groq cloud or local Ollama	Project-specific AI, interaction, and connection behavior
Required world setup	Normal Java test world plus mod-specific interaction	Active packs, Beta APIs, and cheats; each project has its own connection setup
Best first diagnostic	Loader log and clean profile	Content errors, active packs, experiments, and connection response

These details were checked on 2026-09-05. Game updates can change compatibility, so confirm the version on the project page before downloading.

Java Edition strengths and tradeoffs

Java gives you a conventional mod-loader environment. You can isolate Verity in its own launcher instance, inspect detailed logs, choose cloud or local AI, and test compatibility with other mods in a controlled order. The 1.20.1 Forge version is the recommended option in the current project listing.

That flexibility creates more components to match. The Minecraft version, Java runtime, loader, Verity release, dependencies, and every other mod must agree. The companion can appear even when the AI provider is misconfigured, so installation success and conversation success are separate milestones.

Choose Java when you already use Forge profiles, want to run Ollama locally, or need the specific Java implementation documented by its project. For a first install, prefer the Forge 1.20.1 main stable file. The separate NeoForge 1.21.1 branch may suit an existing 1.21.1 environment, but remains a legacy release.

What a typical Java setup involves

1. Create a dedicated 1.20.1 instance so Verity does not share a folder with an unrelated modpack.
2. Install the Forge build that the project page names, then launch once to generate folders.
3. Add the Verity JE file and any dependencies listed on the project page to the mods folder.
4. Launch to the title screen. If the game crashes here, the problem is loader, runtime, or dependency related, not AI related.
5. Configure Groq with your own API key, or start Ollama and pull a model before opening the world.
6. Create a new test world, meet the companion, and send a short message to confirm a response.

Each step has a clear pass or fail result, which is the main practical advantage of Java: when something breaks, you can usually see where.

Bedrock and PE strengths and tradeoffs

Bedrock uses the platform’s add-on import experience instead of a Java loader. For a supported build, importing a package can feel more direct. “PE” is the former Pocket Edition name; current mobile releases use Bedrock Edition.

The setup still requires several checks. The behavior and resource packs supplied by the selected project must be active, and both current descriptions require Beta APIs and cheats. Utlover65 documents its own online connection step; PnTMC 4.0.0 uses a local helper and WebSockets connection before its nearby or inventory chat interaction. Follow the connection instructions for your project. Bedrock creator APIs can change between updates, so a mismatch may appear as missing UI or silent scripts rather than a clear desktop crash log.

Choose Bedrock if that is the game edition installed on your device and the project page lists your exact build. Do not follow unofficial console sideload instructions just because the same project works on mobile or Windows; platform restrictions differ.

Choosing between the two Bedrock projects

The two Bedrock adaptations solve the same idea in different ways, so compare them on the points that affect you:

• Connection model. Utlover65 relies on its documented online connection steps. PnTMC uses a local helper over WebSockets, which must keep running on the same device as Minecraft while you play.
• Device fit. PnTMC’s documented helper runs on Windows, in Termux on Android, or in a-Shell on iOS. Mobile users need to keep the helper running in the background; a second computer is not required. Utlover65’s online connection avoids a local helper but depends on the author’s service being available.
• Version match. Compare your exact Bedrock build against each project’s file history. A project that lists your build is a better first choice than one that is “probably close.”
• Interaction style. PnTMC describes nearby and inventory-based chat; Utlover65 describes its own interaction flow. Read each page to see which matches how you want to talk to the companion.

Install only one Verity adaptation in a world at a time. Two add-ons that both define a Verity companion can conflict in ways that look like neither works.

File formats help identify the right edition

Java mod releases commonly use a .jar package loaded by Forge or NeoForge. Bedrock add-ons commonly use a .mcaddon package that Minecraft imports into behavior and resource packs. Seeing the expected extension helps detect an obvious edition mismatch, but it does not prove a file is authentic or safe.

A renamed executable can imitate a familiar title. A copied package can retain the expected extension while coming from an unknown source. Check the project page, author, Project ID, supported version, release date, and file history together. Use the project page rather than a copied file link.

A useful rule: a .jar never belongs in Bedrock, a .mcaddon never belongs in a Java mods folder, and an .exe or .bat presented as “the mod” should be treated as a warning sign unless the project page itself documents that helper.

AI behavior differs

Verity JE documents two provider choices. Groq sends model requests to a cloud service using the user’s own API key. Ollama talks to a model service running on the user’s machine. The choice affects privacy, hardware use, network needs, troubleshooting, and response speed. It does not change the need to protect logs and configuration.

The Bedrock adaptations use project-specific AI and interaction behavior. Utlover65 documents a set of online connection steps; PnTMC documents its own resource-intensive AI and chat behavior. Do not paste a Java Groq API key or Ollama address into a Bedrock command unless the selected project explicitly asks for it.

Hardware and network expectations

• Java with Groq. Light on local hardware beyond Minecraft itself, but requires a stable internet connection and a valid key. Rate limits on the provider side can show up as slow or missing replies.
• Java with Ollama. No cloud dependency for the model, but the model runs on your CPU or GPU alongside Minecraft. Smaller models respond faster on modest machines; larger ones may need a dedicated GPU to feel conversational.
• Bedrock projects. Phone players should expect battery and heat costs from any resource-intensive add-on, and any connection step depends on network quality. Test in a short session before committing to a long playthrough.

Troubleshooting differs too

For Java, start with game startup. If Minecraft does not reach the title screen, inspect the runtime, loader, dependencies, duplicates, and earliest useful log error. If the world opens and Verity appears, check provider configuration, model access, microphone, speech recognition, and text-to-speech.

For Bedrock, start with the world. Confirm the exact Project ID and game build, required packs, Beta APIs, project-specific settings, and a clean world. Utlover65 associates a visible ... response with a connection issue. Do not automatically apply that diagnosis or connection command to PnTMC’s project.

Symptom quick reference

Symptom	Likely edition-specific cause	First check
Game crashes before title screen	Java: loader, runtime, or dependency mismatch	Earliest error in the latest log
Companion spawns but never replies	Java: Groq key or Ollama not reachable	Provider settings and whether the model service is running
Add-on imports but nothing happens	Bedrock: packs inactive or Beta APIs off	World settings, both packs listed as active
Replies show only ...	Bedrock (Utlover65): connection not established	Repeat that project’s documented connection steps
Chat works in one world, not another	Either: world created before setup changed	Test in a brand-new world

Which edition is more private?

No edition earns a blanket privacy label. Java with Ollama can keep language-model inference local, but the game, launcher, mod files, and any other services still have their own behavior. Java with Groq sends model requests to Groq under that service’s terms. Bedrock uses the add-on’s documented connection steps, which may depend on an online service run by the project author.

The practical privacy questions are: where does the prompt go, what API key is used, what appears in logs, and what third-party service is active? Use the current project documentation, avoid sensitive prompts, and never share API keys. This site never receives AI conversations or API keys; if analytics is accepted, it records only the general guide and selector choices described in the Privacy Policy.

Recommendations by player type

• Phone or tablet player: Bedrock is the only realistic route. Pick the project whose file history lists your build and whose connection model fits your setup.
• PC player who wants the most control: Java with a dedicated Forge 1.20.1 instance gives the clearest logs and the option of local AI.
• Privacy-focused player: Java with Ollama keeps model inference on your machine, at the cost of hardware load.
• Content creator recording a playthrough: Choose the edition you can troubleshoot quickly on camera. A clean, dedicated profile or world matters more than the edition itself.
• Player with a large existing modpack: Test Verity alone first, then add other mods back in small groups. Do not judge the project from a crash caused by an unrelated mod.

Final choice checklist

• If your title screen says Java Edition, use the Java project and Java setup.
• If you play the Bedrock product on a supported Windows or mobile build, choose the Bedrock project by author and Project ID.
• If you want local Ollama, choose the documented Java setup.
• If you cannot create a separate profile or test world, pause before modifying an important save.
• If your exact version is not listed, do not substitute a mirror or a close-looking release.
• If a tutorial mentions the other edition’s loader, pack settings, or command flow, stop and return to the matching guide.

After choosing, follow one edition from download through first response. Mixing instructions is the fastest way to produce a setup that partly loads but cannot answer.