Verity Minecraft Bedrock: Addon Choices and Installation
There are two separate Verity Bedrock projects. Choose Utlover65’s Verity BE or PnTMC’s Verity — Bedrock Edition, activate the chosen pack, and follow that author’s connection instructions; their chat rules and AI backends are different.
Updated
Choose the author before the file
| Choice | Current reference checked | Conversation path |
|---|---|---|
| Utlover65 — Verity BE | v4.2.3 file, marked 26.50; description requires 26.30 | Author’s debugger/backend connection; prefix chat with Verity |
| PnTMC — Verity — Bedrock Edition | 4.0.0 file labelled V26.50; description says V26.10+ | Separate setup bridge; /connect 127.0.0.1:3000 |
These file and description labels are not proof of compatibility with 1.21.130. Neither source establishes a direct import procedure for Nintendo Switch. The PnTMC setup guide explicitly documents Android, iOS and Windows; do not infer a console port from that list.
Import and activate the addon
Download the package from the chosen author’s project. On a device with supported file importing, open its .mcaddon package with Minecraft and wait for the import result. In a new test world’s settings, activate its behavior pack and any paired resource pack. Enable Beta APIs and the cheats required by the author’s connection command before entering the world.
An import-success notification means the package was imported; it does not mean it is active in a world, that its scripts initialized, or that its remote AI connection works. If the addon is missing, check the active world’s pack list. If its dialogue interface is absent, the Utlover65 FAQ specifically directs players to check Beta APIs and the addon version.
Keep the two authors’ packages separate while testing. Use a copy before adding a horror addon to an existing world.
PnTMC: connect the documented bridge
This path belongs to PnTMC’s 4.0.0 setup guide. Open Minecraft Settings → General, enable WebSockets, and turn off Require Encrypted Websockets as that local bridge requires. The author’s reference image is from 26.44; placement can differ in other versions. Keep this connection local rather than exposing it as a public service.
| Device | Author’s setup application | Start or resume the bridge |
|---|---|---|
| Android | F-Droid versions of Termux and Termux:API | Extract the author’s Android package; configure its .env; follow the package’s install command, then run bash start_android.sh from its setup folder |
| iPhone/iPad | a-Shell or a-Shell mini | Extract the iOS package into a-Shell; configure .env; run sh reinstall_ios.sh for setup, then sh start_ios.sh |
| Windows | Python 3.10+ and the author’s Windows package | Configure .env, install its requirements.txt and required websockets==10.4, then run start_minecraft_stt.bat |
Use the author’s setup packages and complete platform commands. They require Groq and FishAudio details plus the intended voice model ID; leave private keys out of chat and screenshots. On Windows the author also provides loopback repair scripts for connection failures: review what they change before granting administrator rights.
With the bridge running, enter the enabled test world and type:
/connect 127.0.0.1:3000Repeat that connection after leaving and re-entering the world. Stop the bridge with Ctrl+C on Android/Windows, or close the running a-Shell tab on iOS. The iOS instructions explicitly exclude microphone input and !talk; use normal text chat there.
Utlover65: use its backend instructions
Utlover65’s page uses a debugger connection, not PnTMC’s loopback bridge. Its FAQ names /script debugger connect traye.ddns.net or the author’s automatic alternative. That connects to the author’s service: use the current setup tutorial linked by Utlover65 and its public instructions before connecting, because a backend address can change.
The author says to type Verity followed by your message and says distance does not matter. PnTMC instead says proximity matters and uses Hey Verity when the companion is in the inventory. Applying one rule to the other addon can make a working installation look broken.
For a short test, send a fresh text question and look for a relevant new reply. If you get only dots, check the correct author’s connection and backend status; if text works but audio does not, continue to voice troubleshooting. The version table keeps the file branches separate.