Verity Mod Bedrock and PE Setup Guide

Identify your Bedrock project before importing

This guide covers two Minecraft Bedrock adaptations. Verity BE is published by Utlover65 under Project ID 1574632. Verity - Bedrock Edition is published by PnTMC under Project ID 1575941. Both project teams list thatmobyt as an Author member, but they remain separate implementations with different releases, gameplay, and support instructions.

On 2026-09-05, Utlover65 listed 4.1.2 for 26.40, although its setup copy still said 26.30. PnTMC listed 4.0.0 for 26.40 and described support for 26.10 or newer. Open the chosen project’s Files tab and resolve those labels before importing. The version compatibility guide keeps the full snapshot and verification history.

“PE” is an older name for Minecraft on mobile; current Android and iOS releases use Bedrock Edition. The exact project, Bedrock build, and device must still match. An add-on can import successfully and still fail in the world when any of those do not match.

Start with the correct project

Open the download guide and confirm the title, author, Project ID, supported game version, and release date for the Bedrock project you intend to use. Do not mix a tutorial for one Project ID with the other project’s files, and do not use a recovered copy shared in a video comment.

Download through the project’s own Files area. This guide does not provide a direct add-on file link because the project page is where the current version, changelog, requirements, and support information live. If the current game build is newer than the one listed by the project, wait for an update or test only in an expendable environment. Do not edit a manifest version number and assume the underlying scripts became compatible.

Import and activate both packs

Use the normal Bedrock add-on import process for your device. When import completes, create a new test world rather than opening an important save. In that world’s settings, activate every behavior pack and resource pack supplied by the add-on. If Bedrock reports a missing dependency, return to the project instructions and confirm that both parts imported.

Check the Active section after activation. A pack appearing under My Packs but not Active does not affect the world. If you imported multiple Verity versions during testing, remove duplicates or old copies before importing again; Bedrock may retain packs with similar names or UUIDs and make it difficult to know which revision is active.

On mobile, verify that the downloaded file was opened with Minecraft rather than only saved by the browser or file manager. On Windows, verify that the same Bedrock installation you launch completed the import. Console environments have different add-on limitations; do not assume a mobile tutorial provides a supported console installation method.

Enable the selected project’s settings

Both projects require Beta APIs, and their connection instructions require cheats. PnTMC’s 4.0.0 setup uses a local companion program, described below. Utlover65 has a separate connection service: the two projects’ commands and configuration are not interchangeable.

Experimental settings can affect compatibility and world upgrades, and Mojang may change or remove experimental APIs. That is another reason to use a separate test world and keep backups. If the dialogue interface is missing, return to world settings and verify that Beta APIs remained enabled after the pack was activated.

When the selected project requires cheats, enabling them can affect achievements in that world. Make the choice deliberately and do not use a valued achievement world as the first test.

Connect PnTMC 4.0.0 on your device

Use the platform-specific files and dependency instructions in PnTMC’s setup guide. Configure your own Groq key, FishAudio key, and voice model ID in the helper’s local .env file.

Android

1. Install Termux and Termux:API from F-Droid, then follow the Android dependency steps in PnTMC’s guide.
2. Allow microphone access for voice input and background operation so the helper can stay running beside Minecraft.
3. Inside the installed helper folder, run bash start_android.sh.

iPhone and iPad

1. Extract the setup into a-Shell’s local storage and configure its .env file.
2. Run sh reinstall_ios.sh to install the helper’s dependencies, then sh start_ios.sh to start it.
3. Use typed chat. The current iOS helper does not support microphone input.

Windows

1. Install Python 3.10 or newer and open a terminal in the helper folder.
2. Run python -m pip install -r requirements.txt, then follow the guide’s pinned WebSockets dependency and loopback steps.
3. Open start_minecraft_stt.bat and keep its window running.

Connect Minecraft to the helper

In Minecraft, open Settings > General > Configure WebSockets, enable WebSockets, and disable Require Encrypted Websockets for this local connection. Activate both packs, Beta APIs, and cheats. Keep the helper running, enter the world, and run:

/connect 127.0.0.1:3000

Repeat the connection after re-entering the world. This address is for a helper running on the same device, not a public server.

Check the connection before changing settings

First check whether the helper stays open without an error. If it exits immediately, restarting Minecraft cannot repair its missing dependency or configuration. Resolve that error using the platform section of the linked guide. Never upload the .env file with a support request.

Next, enter the connection command once and read Minecraft’s response. A rejected connection is different from an AI service rejecting a prompt: the former happens before a conversation can reach the provider. Do not replace every credential simply because the game cannot reach the local program.

Finally, try one short typed message using the interaction below. A text answer establishes that the basic connection works; it does not prove microphone capture or generated speech works. Test those separately. Do not disable your entire firewall, expose the helper to the internet, or run an unrelated administrator script as a shortcut. Inspect the maintainer’s Windows helper before allowing its requested loopback changes.

Connect Utlover65’s project and test chat

Utlover65’s Verity BE depends on a connection step described by that project’s tutorial and support material. Follow the current instruction rather than copying an old command from a short clip or comment. Do not apply that command to PnTMC’s project unless PnTMC’s current page explicitly instructs you to do so.

For Utlover65’s project, begin a message with Verity after the connection succeeds. PnTMC documents nearby chat when Verity is on the ground and Hey Verity when it is in inventory. Start with a short message and confirm the selected project’s packs and required settings before repeating it.

The older /verity_language instruction is not repeated in PnTMC’s current 4.0.0 setup guide. Do not assume that command exists in your installed release. See the conversation and voice guide when text works but a trigger phrase, distance rule, microphone, or language does not.

This website never asks you to enter a connection value, account secret, or private server information. Complete setup only where the selected project instructs you to do so.

Symptom: Verity shows three dots

Utlover65’s troubleshooting text associates ... with a connection or online service problem. The character and scripts can load before the service becomes available, so three dots do not necessarily mean the pack failed to import. For PnTMC’s project, use its own support page rather than assuming the same cause.

Check in this order:

1. Confirm that your Bedrock build matches the add-on release.
2. Confirm both behavior and resource packs are Active.
3. Confirm the selected project’s required experiments and cheats state.
4. Repeat its documented interaction or connection process once and read the exact response.
5. Test a new world with only that Verity project active.
6. Check the project page or support channel for a service incident or updated connection instruction.

If many users report the same connection failure at the same time, local reinstallation may not help. Preserve the exact error text and time without posting personal account information.

Symptom: the dialogue interface is missing

A missing dialogue box points more strongly to world configuration or version compatibility than to the remote AI response. Re-open world settings and verify experiments. Confirm that the behavior pack is active, not merely imported. Test a fresh world because changing experiments after a world has already initialized can behave differently from enabling them before first launch.

Remove other behavior packs for the clean test. Two packs can listen to the same events, replace resources, or rely on different experimental API states. If the clean world works, add other packs back one at a time.

Symptom: no entity appears

Read the current project instructions for how Verity is introduced, spawned, or triggered. Do not assume Java key binds or crafting recipes apply. Confirm that the pack appears in the world’s Active list and that no content errors were shown during load.

If an old version was installed previously, remove it from the world’s active packs and from storage, restart Minecraft, then import the current release again. Take screenshots of the pack version and world settings before changing them; a short record makes support much faster.

Multiplayer and device cautions

Every participating client must be able to receive the world’s required resource pack, and the host’s Bedrock build controls creator API compatibility. Test with one host and one client before inviting a larger group. Mobile devices may also close background processes or struggle with heavy worlds, so distinguish a device performance problem from an add-on connection failure.

Back up the world before updating Bedrock or the add-on. After an update, repeat the smallest possible test: load a clean world, confirm the entity, send one text message, and restart. Only then return to a long-running world.