01

What the maintainer page confirms

These are the prerequisites currently listed on the public project page.

FieldOfficial statusSource
Required versionMinecraft 1.26.30 / 26.30Verity BE project FAQ
Experimental settingBeta APIs must be enabledVerity BE setup + FAQ
Command requirementRun the debugger connect commandVerity BE setup + FAQ
Permission settingCheats enabled: yes, absolutelyVerity BE FAQ
Support pathUse Discord/status and the linked No Purpose videoVerity BE FAQ
02

Safe triage order

Confirm the project identity first: Verity BE project 1574632, release 1.0.8, and Bedrock 26.30. Then check the copied world's Experimental Toggles, make sure cheats are enabled, run the current connect flow from the project tutorial or Discord, and test again before replacing files.

03

What this error does not prove

It does not prove malware, a broken Bedrock install, or that every backend outage has the same cause. The public FAQ links out to a support video instead of publishing a text diagnosis, so anything more specific must stay labeled unknown unless the maintainer documents it.

04

Useful support report

Record project ID 1574632, release 1.0.8, device, Bedrock version, whether Beta APIs and cheats are enabled, whether the debugger connect command completed, and whether Verity shows ellipses, no dialogue box, or the exact Error: No Purpose string. Never include secrets or unrelated world files.

FAQ

Questions

Does 'Error: No Purpose' mean the project is fake?

No. The official Verity BE page documents the error and links users to a support video; it is a project-specific troubleshooting state, not proof that the download is fake.

Should I switch to PnTMC Bedrock when I see this error?

Not automatically. PnTMC Bedrock is a different project with a different setup flow. Finish the Verity BE checks first instead of mixing Bedrock projects.