Verity Mod Guide

PnTMC V26.40 route checked August 9, 2026

ThatMob's Verity 3.2.0 by PnTMC File Check

ThatMob's Verity 3.2.0 by PnTMC is the current checked PnTMC Bedrock route family for players following the Verity - Bedrock Edition project. Use this page when a video, MCPEDL page, comment, or file host says PnTMC, ThatMob's Verity, V26.40, V26.30, V26.20, V26.10, 3.2.0, or CurseForge record 8593642. It is a Bedrock MCADDON route, not the Java Verity JE JAR and not a generic APK or EXE download.

Record 8593642 Bedrock 26.40 Previous V26.30 #8517480 V26.10 #8517473 39.6 MB Published August 7

Current record map

Check the PnTMC file identity before you install

Current PnTMC V26.40 file 8593642

ThatMob's Verity 3.2.0 V26.40

Choose this route when your source clearly says PnTMC, ThatMob's Verity 3.2.0, or Verity - Bedrock Edition. The checked CurseForge project is a Minecraft Bedrock Addons page, the owner is PnTMC, and the package type is MCADDON. The record is not a mirror hosted by this site, and a matching filename is not a malware verdict; it only proves you found the same public release route.

Open exact CurseForge record
Current 3.2.0 family 4 rows

V26.40, V26.30, V26.20, and V26.10-style builds

The CurseForge file list now shows the current ThatMob's Verity 3.2.0 by PnTMC V26.40 row: record 8593642 at 153.9K displayed file downloads. The older 3.2.0 family rows remain visible: V26.30 record 8517480 at 1.0M displayed downloads, V26.20 record 8517478, and V26.10 record 8517473 under a 26.13 plus three supported-build label. This matters when a Bedrock player follows a mobile tutorial that names an older build instead of the main V26.40 row.

Open all PnTMC files
MCPEDL clue Checked August 9

MCPEDL now lists V26.40 first, with old rows below

MCPEDL shows the Verity - Bedrock Edition page by PnTMC as updated August 7 and lists a V26.40 download first. At the August 9 source check, its visible Downloads section started with ThatMob's Verity 3.2.0 V26.40, then showed older 3.2.0, 3.1.0, and 3.0.0 rows below. That means a fresh install should start from the V26.40 row, while old rows are only for older Bedrock builds, old worlds, or old-video contexts.

Read the MCPEDL route check
Previous file 8503821

ThatMob's Verity 3.1.0 V26.30

Record 8503821 is still useful when a tutorial, old world, or support comment specifically names the 3.1.0 package. For a fresh install, compare it against record 8593642 first. Mixing old and new packs in the same world can create false troubleshooting signals, especially when a player is already testing Beta APIs, scripts, resource packs, and behavior packs.

Open previous 3.1.0 record
Older high-traffic file 8327253

ThatMob's Verity 2.1.0 V26.30

Record 8327253 can still appear in search because it was a high-download PnTMC Bedrock file. It belongs to the same project family, but it is not the current main route after the July 27 update. If a search result sends you there, treat it as an old route signal and rebuild the path through the current PnTMC page before installing.

Open older 2.1.0 record Read the 2.1.0 file check

Install route

Use the PnTMC 3.2.0 file only when your game and tutorial match it

Bedrock and MCPE players need a package route, not a universal Verity Mod file

The phrase Verity Mod can point to different things: the ThatMob horror character, the Java Verity JE project, Undertaletalelover's Verity BE route, the PnTMC Bedrock add-on, a Pocket Edition listing, a modpack, or a reposted file. For this page, the important constraint is narrow: ThatMob's Verity 3.2.0 by PnTMC is a Bedrock and MCPE add-on route family. It should be imported as a Bedrock package, then activated inside a world. It should not be placed in a Java mods folder, and it should not be treated as a replacement for a Forge JAR.

After importing, test in a clean world first. Activate both behavior and resource packs, enable the required experimental settings if the project asks for them, and keep your troubleshooting tied to PnTMC's own instructions. A comment for Verity BE can be wrong for the PnTMC project, and a Java API error guide can be irrelevant for a Bedrock MCADDON that has not even loaded into a world.

Before you click a download button

  • Project: Verity - Bedrock Edition by PnTMC, Project ID 1575941.
  • Version: ThatMob's Verity 3.2.0 by PnTMC for V26.40 record 8593642, previous V26.30 record 8517480, V26.20 record 8517478, or V26.10-style record 8517473.
  • Record: CurseForge file record 8593642 for the current checked V26.40 route.
  • Package: MCADDON, not JAR, APK, EXE, ZIP password archive, or short-link chain.
  • Context: MCPEDL is useful, but compare visible rows with the exact CurseForge record.

Common player problems after import

Current comments around the MCPEDL route show recurring confusion: Verity does not spawn, players ask how to make him talk, some expect microphone input on mobile, and others report that he does not always reply or never changes into the expected monster form. Those are setup, trigger, and feature-expectation questions, not proof that the file is fake. After you confirm record 8593642, move to the matching fix page instead of downloading random mirrors.

Fix spawning and setup Fix lag and delay Reply and transform fixes PnTMC talk controls PnTMC commands

Route comparison

Do not confuse PnTMC 3.2.0 with other Verity routes

What you have What it means Best next page
ThatMob's Verity 3.2.0 by PnTMC [Add-on] - V26.40.mcaddon Current PnTMC Bedrock 26.40 route, record 8593642 Use this file check
ThatMob's Verity 3.2.0 by PnTMC [Add-on] - V26.20.mcaddon Current PnTMC 3.2.0 row for Bedrock 26.20 builds, record 8517478 Open record 8517478
ThatMob's Verity 3.2.0 by PnTMC [Add-on] - V26.10.mcaddon Current PnTMC 3.2.0 row shown under 26.13 plus additional builds, record 8517473 Open record 8517473
ThatMob's Verity 3.1.0 by PnTMC Previous PnTMC route, useful only when a source names 3.1.0 MCPEDL route check
Verity (Stable) (2.0.1)-(26.40).mcaddon Verity BE by Undertaletalelover, a separate Bedrock add-on Bedrock route guide
verity-5.7.3.jar Verity JE Java Forge file, not a Bedrock or MCPE add-on Java file check
APK, EXE, password ZIP, or hidden mirror Not enough source context to trust as the PnTMC record Check the link first

FAQ

Questions players ask about the PnTMC 3.2.0 route

Is this page an official Verity or PnTMC download?

No. This is an independent source-check page. It does not host the file, mirror the MCADDON, or claim ownership of Verity. Use the linked maintainer pages for the final download and support context.

Why does the page mention MCPEDL if CurseForge has the exact record?

Many MCPE players discover this route through MCPEDL or video descriptions, not through a direct CurseForge record number. MCPEDL is useful as a route clue because it identifies PnTMC and the Bedrock project, but the exact CurseForge record is the better stable identity signal when the visible download rows are out of sync.

Does a matching record prove the file is safe?

No. A record match proves route identity, not a malware verdict. It helps you avoid wrong-edition files, stale mirrors, or random hosts. You still need normal device safety practices and should avoid any page that hides the final host or wraps the add-on in unrelated installers.

What should I do if Verity does not spawn after installing 3.2.0?

First confirm you installed the PnTMC route and not Verity BE or a Java JAR. Then test in a clean world, activate behavior and resource packs, enable required experiments, and read the not-working and talk-control pages for project-specific steps.

Why do MCPEDL comments say Verity does not reply or never transforms?

Current public comments on the MCPEDL route still include no-reply, no-monster-form, and not-spawning reports. Treat those as setup symptoms first, not proof that the file record is wrong. Check that the behavior pack and resource pack are both active, Beta APIs or required experimental toggles are enabled, your world is not carrying an old conflicting pack, and you are following the PnTMC route rather than Verity BE or Java JE advice. If the file identity is right but the behavior still fails, use the PnTMC YouTube/community feedback path named in the project description, because the maintainer says feedback there is easier to read.

Checked sources PnTMC 3.2.0 record V26.20 record V26.10 record MCPEDL listing PnTMC YouTube Release data Old 2.1.0 file check MCPEDL route notes Bedrock route guide Lag fix