Pocket Edition route check
MCPE players do not need a Java jar. They need a Bedrock add-on route that matches their Minecraft build, package type, and setup instructions. This page separates Verity BE, PnTMC's Bedrock edition, and the similarly named Verity Pocket Edition (Be) listing so a mobile player can choose the correct .mcaddon before importing anything.
Current route map
Verity BE by Undertaletalelover is a current Bedrock add-on route. The checked file is Verity (Stable) (1.0.9)-(26.3).mcaddon, file record #8486588, published July 22, 2026. At the latest check, the project showed 3,570,128 downloads on CurseForge.
Open Verity BE file recordVerity - Bedrock Edition by PnTMC is a separate add-on, not the same listing as Verity BE. The checked file is ThatMob's Verity 2.1.0 by PnTMC [Add-on] - V26.30.mcaddon, file record #8327253, published June 27, 2026. At check, the project showed 6,278,446 downloads.
Open PnTMC file recordVerity Pocket Edition (Be) by vexi1111_ is another similarly named Bedrock listing. The checked file is Verity (1.0.2) - (26.3).mcaddon, file record #8406293, published July 10, 2026, with 18.6 MB displayed size and 41,316 project downloads at check.
Open Pocket Edition file recordWhy this matters
A player searching for Verity Mod MCPE usually wants a working mobile import, not a lesson in project history. The problem is that the same Verity name appears across Java mods, Bedrock add-ons, Pocket Edition pages, videos, comment links, and old mirrors. A search result can say "download" while sending a phone user to a Java .jar or a desktop setup guide. That is a poor fit even when the file is real.
The first useful distinction is file type. Java uses .jar files with Forge or NeoForge. MCPE and Bedrock use .mcaddon or .mcpack packages that import into Minecraft and then require world activation. If a page asks a mobile player to install Forge, place a jar in a mods folder, run a Windows executable, or open an APK as the mod itself, it is not answering the Pocket Edition route question.
Bedrock add-ons do not always share setup instructions. One route may require Beta APIs, another may describe a debugger connection, and another may rely on its own backend or world behavior. Copying commands from the wrong project is a common reason players think Verity installed but only says dots, never spawns, or fails after the first world load.
Use the exact project name from the file page. If the page says Verity BE, read Verity BE notes. If it says PnTMC, use PnTMC notes. If it says Pocket Edition, read that project's requirements. Mixing instructions can create a failure even when every individual page is describing a real add-on.
Decision table
| User signal | Likely fit | First check |
|---|---|---|
| Video says Verity BE or Undertaletalelover | Verity BE Project 1574632 | Match file #8486588 and Bedrock 26.30. |
| Video says PnTMC or ThatMob's Verity 2.1.0 | Verity - Bedrock Edition Project 1575941 | Match file #8327253 and PnTMC setup notes. |
| Page says Verity Pocket Edition (Be) | Pocket Edition Project 1596246 | Match file #8406293 and the listed 26.30 requirement. |
| File ends in .jar | Java route, not MCPE | Switch to Java only if you are using the Java launcher. |
| Page offers APK, EXE, password ZIP, or notification unlock | Not a normal add-on route | Back out and use a traceable project page instead. |
Mobile setup
A successful import means Minecraft recognized the package. It does not prove the add-on is active in the world. Create a fresh test world, activate the behavior pack and resource pack, enable the required experiments, and follow only the current project instructions. If the test world works, your main world probably has a settings conflict or an older pack state.
Mobile players should also restart Minecraft after importing if the pack list does not update. Some devices cache the available packs until the app restarts. Re-importing the same file repeatedly is less useful than checking the active world settings.
Some Verity add-ons depend on an online AI backend, debugger connection, or service quota. The Pocket Edition listing says AI features require an active connection and notes that AI may stop responding when a Cloudflare Workers daily limit is reached. That kind of failure is not fixed by downloading a random mirror. It is a service or setup condition that should be checked against the current project page.
If the add-on imports and Verity appears but does not answer, check the project instructions, server status, required command, Beta APIs, and comments before replacing the file. If nothing works in a clean world, return to the project page and use the maintainer's support path.
Common fixes
Confirm the package is .mcaddon or .mcpack. A Java .jar, APK, EXE, or archive-gated download is not the normal Pocket Edition add-on path.
Activate both behavior and resource packs in the target world. Then enable required experiments and retest before trying another source.
Check the exact project's backend, debugger, command, and quota notes. A service limit can look like a broken file even when the import is correct.
FAQ
No. Verity BE, Verity - Bedrock Edition by PnTMC, and Verity Pocket Edition (Be) are separate public project routes with different owners and file records. Check the Project ID before copying setup instructions.
A normal Minecraft Bedrock add-on route uses .mcaddon or .mcpack files. Treat APK, EXE, password ZIP, or notification-unlock pages as unrelated unless the maintainer page clearly explains them.
The useful task is route verification. The project page shows owner, Project ID, update date, comments, version support, and setup notes. Rehosting a trending add-on would hide those signals.