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.

The box above shows each project’s current file. The two authors release on different schedules, and PnTMC reuses the add-on number across game builds (its 26.40 and 26.50 files are both 4.0.0), so match the game build on the file page rather than the add-on number. The version guide keeps older files and the check history.

Installing PnTMC on a phone? Use the Android setup guide for Termux, permissions, local helper files, and reconnecting after a restart. The steps below compare both projects and cover the other supported device instructions.

“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.

Utlover65 vs PnTMC at a glance

	Verity BE (Utlover65)	Verity - Bedrock Edition (PnTMC)
Project ID	1574632	1575941
Required world settings	Beta APIs, cheats	Beta APIs, cheats, WebSockets enabled
AI connection	/script debugger connect traye.ddns.net 19144, a third-party relay	Local helper on the same device (Groq + FishAudio keys in .env)
Requires game version (manifest)	1.21.110 or newer	1.26.40 or newer (26.50 file)
How to start a conversation	Begin a chat message with “Verity”	Nearby chat on the ground, “Hey Verity” from inventory
Voice input	Per project instructions	Android and Windows; not iOS

1. Minecraft Bedrock + Verity BEUtlover65; chat starting with “Verity”
2. script debugger to traye.ddns.net:19144
3. Hive Mind relayThird-party server that makes web requests for the add-on
4. your message, name, history
5. The add-on's WorkerCloudflare Worker that picks Groq or another AI

1. Minecraft Bedrock + PnTMC add-on/connect 127.0.0.1:3000 each session
2. WebSocket, same device
3. PnTMC helperPython, Termux, or a-Shell; your keys in .env; microphone on Android and Windows
4. HTTPS
5. Groq + FishAudioYour accounts: text reply and generated voice

Yellow border: leaves your deviceGreen border: stays on your device

Use the table to pick a project, not to mix them. If you want the least setup on a phone, Utlover65’s project has fewer moving parts, at the privacy cost explained in how Utlover65 connects. If you want local control over the AI provider and generated voice, PnTMC’s helper gives you that at the cost of extra installation steps and keeping a background program running.

Utlover65 4.2: the lighting update and Vibrant Visuals

Utlover65’s 4.2.0 release (October 5) was a visual update. Its notes list colored light from torches, lanterns, candles, and other light sources, reworked materials on Verity’s box, the chest version, the Smiler, and the flashlight, and new shading on Verity itself. The notes also say the new lighting needs Vibrant Visuals or ray tracing turned on, alongside Beta APIs in the world. 4.2.3, the main file on October 18, did not have public release notes when checked.

What that means on your device:

• Look for the setting first. Vibrant Visuals is a graphics mode in Settings > Video. It is offered only on hardware Mojang supports, so if the option is missing on your phone or tablet, the add-on still loads but without the new lighting.
• Expect a performance cost. Vibrant Visuals is heavier than the standard renderer. If a phone heats up or stutters during a long Verity session, switching back costs you the colored light, not the companion or chat.
• Do not treat flat lighting as a broken import. If Verity appears, answers, and only the colors look plain, the cause is the graphics mode. Use the missing-entity and three-dot checks only when the character or the conversation fails.
• Update in one step. Remove the 4.1.3 packs from the world before activating 4.2.x, so the world does not reference two revisions of the same add-on.

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.

How to check your Bedrock build

Open Minecraft and look at the version number in the lower corner of the title screen, or open Settings > General and scroll to the bottom. Compare the full number with the file’s listed game version. Phone app stores often update Minecraft automatically, so a setup that worked last week can break after an overnight update. If you rely on Verity for a recording or a shared world, check the version before every session.

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.

File types and what they mean

• .mcaddon usually contains both behavior and resource packs and imports them together.
• .mcpack contains a single pack; you may need to import two of them.
• .zip is not opened by Minecraft directly. Do not rename a random zip to .mcaddon unless the project tells you to; a renamed archive with the wrong folder structure imports as an empty or broken pack.

If tapping the file does nothing on Android, use a file manager’s “Open with” option and choose Minecraft. On iPhone, use the Files app share sheet. If Minecraft shows “Import failed,” the download is often incomplete; download it again from the project page instead of a cached copy.

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.

Before running the Windows .bat files as administrator

PnTMC’s Windows instructions ask you to run fix_minecraft_loopback.bat as administrator and, if that is not enough, fix_firewall_and_loopback.bat. Administrator rights let a script change any system setting, so it is worth knowing exactly what these two do. We read both files in PnTMC’s helper release v4.0.3 (the files attached to the setup guide’s GitHub release, dated August 27). This is what they contain:

File	What it actually does
fix_minecraft_loopback.bat	Asks Windows for administrator rights, then runs CheckNetIsolation.exe LoopbackExempt -a for two package names: Microsoft.MinecraftUWP_8wekyb3d8bbwe (Minecraft) and Microsoft.MinecraftWindowsBeta_8wekyb3d8bbwe (Minecraft Preview). It then lists the Minecraft exemptions and prints the next steps.
fix_firewall_and_loopback.bat	Asks for administrator rights, deletes a firewall rule named Verity Minecraft WS 3000 if one exists, then applies the same two loopback exemptions. It adds no firewall rule; a comment in the file says not to open port 3000 to the local network.

Two lines look alarming and are not:

• powershell -Command "Start-Process -FilePath '%~f0' -Verb RunAs" relaunches the same .bat file with an administrator prompt. %~f0 means “this file”. It does not download or start anything else.
• The netsh ... delete rule line removes access rather than granting it.

Why the loopback step exists. Minecraft installed from the Microsoft Store runs as a packaged app, and Windows blocks such apps from connecting to 127.0.0.1 on the same PC by default. The exemption lifts that block for Minecraft only, which is what lets /connect 127.0.0.1:3000 reach the helper.

If you downloaded the helper from anywhere other than PnTMC’s own release, or a newer release, open each .bat in Notepad first (right-click, Edit) and compare it with the table. Stop if it contains anything else, especially commands that download or start other programs (curl, powershell -enc, Invoke-WebRequest, bitsadmin, start https://), long encoded text, changes to Windows Defender (Set-MpPreference, Add-MpPreference -ExclusionPath), new user accounts, or scheduled tasks (schtasks).

To undo the change later, run CheckNetIsolation LoopbackExempt -s to list exemptions and CheckNetIsolation LoopbackExempt -d -n=Microsoft.MinecraftUWP_8wekyb3d8bbwe (and the same for the Preview name) to remove them. Never turn the whole firewall off to make the helper connect: the helper only listens on 127.0.0.1, so traffic stays on your PC.

About the startup script. start_minecraft_stt.bat installs the Python packages each time it runs, then forces websockets version 10.4, which Bedrock’s /connect needs. Its requirements file asks for a newer websockets first, so you may see it reinstalled on every start; that is expected and needs an internet connection. If Python is missing, the script prints Python not found. and stops.

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.

What the helper sends, and where

We read the helper’s source code in the v4.0.3 release for all three platforms. Nothing was run; this describes the code as published.

1. Your deviceHelper listens on 127.0.0.1:3000 only; history kept in memory
2. your message + last 12 messages + game context
3. GroqChat: openai/gpt-oss-20b. Voice input: whisper-large-v3
4. Verity's reply text
5. FishAudioTurns the reply into speech with your voice model

Question	What the code does
Can other devices reach the helper?	No, by default. It listens on 127.0.0.1 port 3000. Leave the optional VERITY_WS_HOST setting unset.
Which servers does it contact?	api.groq.com for chat and speech recognition, and api.fish.audio for generated voice. Nothing else.
What goes to Groq with each message?	Verity’s character instructions, your last 12 chat messages (six exchanges), your new message, and game context from the add-on: the story phase, the biome you are in, and the block or creature you are looking at.
What happens to my voice?	!talk records 5 seconds (VERITY_LISTEN_SECONDS), sends the recording to Groq for transcription, then deletes the file.
Is the conversation saved?	Only in memory. Closing the helper clears Verity’s memory of the conversation.
Are keys bundled?	No. Every .env in the release has empty key fields. You add your own.

Practical consequences. Each message is large: the character instructions alone are about 1,400 tokens before any history, so expect roughly 2,000–3,000 tokens per message once a conversation is going. Use that figure in the Groq limit calculator. If Groq starts returning 413 or 429 late in a session, restarting the helper resets the history and shrinks the requests again.

Keys, costs, and privacy for the helper

The helper sends your messages to Groq for text and speech recognition and, if configured, to FishAudio for generated speech. Both accounts belong to you, and any rate limits or charges apply to your accounts, not to the add-on author. Groq’s free tier is usually enough for casual play, but rapid repeated messages can trigger temporary limits that look like Verity “ignoring” you. See the Groq key guide for creating and storing a key safely.

The default .env settings are VERITY_LLM_MODEL=openai/gpt-oss-20b, VERITY_LANGUAGE=auto, and FISH_TTS_MODEL=s2.1-pro-free. Change the model only if Groq reports that this one is unavailable to you; the helper has special handling for reasoning models like this one, so a different model can behave differently.

Keep the .env file only on your device. Do not screenshot it, paste it into Discord, or share a helper folder with someone else. If you suspect a key was exposed, revoke it in the provider dashboard and create a new one before reconnecting.

Connect Utlover65’s project and test chat

We read the scripts in Utlover65’s 4.2.3 file (its folders are still named 4.2.0) to see what the connection step does. Nothing was run.

The connection command is a script debugger connection. Bedrock add-ons cannot make web requests on their own, so this one uses a library called Hive Mind. You run:

/script debugger connect traye.ddns.net 19144

or set the same address under Settings > Creator > Attach debugger on load. That attaches Minecraft’s script debugger, a developer tool, to a server run by the Hive Mind developer. While connected, the add-on writes each web request into the world, the server picks it up, makes the request, and writes the reply back. The add-on’s own guide calls this the “shared cloud relay”.

What travels through it, according to the code:

AI mode (say it in chat)	Where your message goes	What it includes
verity ai worker (default)	Hive Mind relay, then the add-on’s Cloudflare Worker, which picks Groq or another model	Your player name, Verity’s instructions, up to 20 recent messages, your new message
verity ai key <your-key>	Hive Mind relay, then OpenAI’s API (gpt-4o-mini) by default	The same, plus your API key in the request header
verity ai local or verity ai local <url>	Hive Mind relay, then your own Ollama or llama.cpp server	The same, without a key

Two practical consequences:

• “Own key” mode does not bypass the relay. A code comment says it bypasses the Worker, and it does, but the request still goes through Hive Mind with your key attached. The key is also saved inside the world as a player property, so anyone you share the world file with gets it. If you use this mode, create a separate Groq key just for it and revoke it when you stop.
• “Own key” mode expects an OpenAI key. The bundled guide says to use a Groq key, but the 4.2.3 code sends key-mode requests to api.openai.com with the model gpt-4o-mini; the setting that would change that is not in the shipped config. A Groq key is rejected there.
• Local mode asks for a model called llama3. The bundled guide tells you to download llama3.2:1b, which Ollama stores under a different name. Either run ollama pull llama3, or keep the small model and give it the expected name with ollama cp llama3.2:1b llama3.
• The default mode has a shared limit. The bundled guide says the shared relay is “shared across all players. If Verity stops responding, the limit was hit”. That is the most common reason for three dots on this add-on.

Starting a conversation. After connecting, begin a chat message with Verity. /verity:help lists the commands and /verity:status shows the current phase; /verity:phase, /verity:reset, /verity:summon, and /verity:remove need operator rights.

About the bundled local-AI script. The pack’s local files folder includes a Termux script that builds llama.cpp and starts it with --host 0.0.0.0, which makes the AI server reachable by other devices on your Wi-Fi. If you use it, change that to --host 127.0.0.1 unless Minecraft runs on a different device.

PnTMC’s add-on uses its own local helper and /connect 127.0.0.1:3000 instead; do not mix the two methods. 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.

A five-minute first test

Before building a long survival world, run this short checklist in a fresh world. It separates installation problems from connection problems quickly.

1. Create a new world with only the chosen Verity packs active, plus Beta APIs and cheats.
2. Load in and confirm there are no content-log errors on screen.
3. Introduce or spawn Verity using the project’s documented method and confirm the entity appears.
4. Complete the connection step (Utlover65’s tutorial step, or /connect 127.0.0.1:3000 for PnTMC).
5. Send one short typed message such as “Verity, hello” and wait at least ten seconds.
6. Leave the world, rejoin, reconnect if required, and send another message.

For PnTMC, a reply that arrives but sounds generic and has no voice means the add-on answered from its built-in keyword library: the helper is not connected, so repeat step 4.

If step 3 fails, the problem is packs or settings. If step 5 fails but step 3 works, the problem is the connection or AI provider. If step 6 fails only after rejoining, you most likely forgot to repeat the connection.

Symptom: Verity shows three dots

Utlover65’s troubleshooting text associates ... with a connection or online service problem. In the 4.2.3 code, a reply has to make the round trip through the Hive Mind relay described above, so ... most often means the script debugger is not connected (it does not reconnect on its own after you leave the world unless Attach debugger on load is set) or the shared relay’s limit was hit. 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.

Symptom: the helper stops when Minecraft opens

On phones, the operating system may pause or close Termux or a-Shell when Minecraft takes the foreground. On Android, allow Termux to ignore battery optimization and keep its notification visible; some manufacturers (Xiaomi, Samsung, Huawei, Oppo) add extra “app sleeping” controls that must also be disabled for Termux. On iPhone, background execution is more limited, so switching apps for a long time can end the helper; restart it and reconnect when that happens. The Android setup guide covers manufacturer-specific settings in more detail.

Symptom: voice works on PC but not on phone

Microphone capture depends on the platform. PnTMC’s Android helper needs Termux:API and microphone permission granted to it, not just to Minecraft. The iOS helper does not support microphone input at all. If generated speech is silent but text replies arrive, check your FishAudio key and voice model ID rather than the Groq key.

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.

Realms and public featured servers generally do not allow arbitrary script add-ons with Beta APIs, so plan on a locally hosted world. With PnTMC’s project, the helper runs on the host’s device, which means conversations use the host’s keys. Tell friends that before inviting them, and see the multiplayer guide for server-side limitations.

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.

Updating safely

When a new release appears, read its changelog on the project page first. Export your world (World settings > Export World) so you have a restorable copy. Remove the old packs from the world and from storage, import the new file, and re-activate both packs. For PnTMC, also update the helper files, because a new add-on release can expect a newer helper; keep your existing .env values but compare them with the new template in case a setting was renamed.

If the update breaks something, restore the exported world and the previous release rather than mixing old and new packs. Report the issue with your Bedrock build, add-on version, device, and exact error text on the project’s own support channel.