# Verity Mods Wiki: Complete Site Guide

> Verity Mods Wiki is an independent English reference for people searching for the Verity Minecraft mod. The site identifies the current Verity JE Java Edition release, links downloads to the file published through the project source, explains Forge and AI requirements, and separates confirmed facts from unverified Bedrock or remake claims. It is designed for players who first encounter Verity through horror videos and need to know whether the mod is real, which edition works, how to install it, and why an AI or multiplayer setup may fail. The site is not affiliated with Mojang, Microsoft, Modrinth, ThatMob or the Verity JE developers, and it does not claim ownership of project files or media.

## Site Background
Verity is commonly described as a small yellow AI companion whose relationship with a Minecraft player can develop into a horror experience. Search results mix questions about the original video concept with requests for a downloadable mod, Java and Bedrock packages, remakes, resource packs and platform listings. Verity Mods Wiki exists to organize those different intents around evidence.

The editorial process starts with first-party or project-controlled information. Version numbers, file names, publication dates, Minecraft compatibility, loaders and file sizes are checked against the public Verity JE project data. Authorization wording is reported from the Verity JE description and the ThatMobbb/VerityCraft repository, both of which state that the Java adaptation was created with ThatMob's explicit permission and contractual agreement. The site links to those statements so readers can inspect them directly.

The site does not infer a Bedrock release from Java popularity. A Forge JAR and a Bedrock MCAddon use different engines and package systems. Bedrock pages therefore show an availability status until a traceable first-party or clearly authorized package can be verified. Corrections can be sent to support@veritymods.wiki with the affected page and a supporting source. Private API keys, passwords and unredacted logs should never be submitted.

## Content Category Details
### [Current Download and Java Release](https://veritymods.wiki/)
The homepage satisfies the primary Verity Mod download intent. It identifies Verity JE v6.0.0-beta.7 as the current checked release for Minecraft Java 1.20.1 with Forge, displays the published JAR name, approximate size and publication date, and connects the primary action to the Modrinth CDN file. A 15-second in-page source-check countdown precedes the download, while a normal source-page link and non-JavaScript fallback remain visible. The page also places platform requirements, installation order, real-versus-remake context, Java-versus-Bedrock availability, release history and FAQ answers around the download.

### [Java Compatibility and Installation](https://veritymods.wiki/verity-je/)
The Java guide explains the supported edition, Minecraft branch, Forge loader, client/server requirement and AI setup boundary. It distinguishes the Minecraft mod layer from Groq online or Ollama local language processing. The linked [installation guide](https://veritymods.wiki/how-to-install/) turns those requirements into an ordered workflow: prepare a clean profile, install Forge, place the intact JAR in the correct mods folder, verify the mod loads, configure the AI backend and test in a new world. It also covers backups, server installation and credential protection.

### [Verity Mod Fabric Compatibility](https://veritymods.wiki/verity-mod-fabric/)
The Verity Mod Fabric guide owns the Java-loader compatibility question that is not the same as the Java download page or the Bedrock status page. It records the official Verity JE project metadata checked on September 19, 2026: Forge for Minecraft Java 1.20.1, with no Fabric loader listed. The guide explains why a Forge-only JAR cannot be converted by renaming it or adding Fabric API, gives a table for comparing loader, package, client/server and source evidence, and provides a safe checklist for evaluating a future Fabric port. It keeps the Java-versus-Bedrock boundary separate and points Fabric users to a separate Forge test profile instead of an unverified download.

### [First-session Gameplay Guide](https://veritymods.wiki/how-to-play-verity-mod/)
The first-session guide owns the informational question of how to play Verity Mod after the JAR is installed. It starts with a clean Minecraft Java 1.20.1 Forge test world, confirms the companion before testing AI, and puts text replies before microphone, TTS or multiplayer changes. The guide links download and installation questions back to their specialist pages, keeps Bedrock and server compatibility separate, and labels its AI-generated first-session illustration as an editorial concept rather than an official screenshot.

The current project record used in the guide is Verity JE v6.0.0-beta.7 for Java 1.20.1 with Forge, checked on August 22, 2026 and published on August 19, 2026. The page does not promise that every edited video event will reproduce in every world; it uses the installed release, documented features and a disposable test world as the practical boundary.

### [Authenticity and Platform Availability](https://veritymods.wiki/is-verity-mod-real/)
The authenticity guide answers why players question whether Verity is real and documents the evidence for a public Java adaptation. It explains the difference between the original property, the authorized Verity JE adaptation, independent remakes, resource packs and claimed Bedrock ports. The separate [Bedrock status page](https://veritymods.wiki/bedrock/) explains package incompatibility and warning signs such as renamed JAR files, EXE installers, missing publisher identity and reused Java screenshots.

### [Verity Mod Status and Availability](https://veritymods.wiki/what-happened-to-verity-mod/)
The status guide owns the question of what happened to the Verity Mod without turning a missing URL into an unsupported cancellation claim. It records the checked legacy CurseForge route as unavailable on August 16, 2026, explains why a 404 does not prove the cause, and keeps Verity Soul, Verity Remake and Verity JE as separate project identities. It also records the current Verity JE v6.0.0-beta.7 source and gives a publisher-first checklist for old links, mirrors and re-uploaded JARs.

### [Java versus Bedrock Comparison](https://veritymods.wiki/verity-je-vs-bedrock/)
The comparison guide owns the platform-choice intent that is different from the Java requirements page and the Bedrock status page. It records Verity JE v6.0.0-beta.7 as a Minecraft Java 1.20.1 Forge JAR, explains why a Forge JAR cannot run as a Bedrock add-on, and separates the current CurseForge Bedrock listing pages from the Modrinth Java project. It does not invent a direct Bedrock package URL or claim that similarly named listings share ownership.

### [Version Tracking and Troubleshooting](https://veritymods.wiki/versions/)
The version tracker records Verity JE v6.0.0-beta.7, 5.7.2 and 5.6.2 with file names, sizes, dates and the common Minecraft 1.20.1 Forge target. It explains safe update and rollback practices, including world backups and removing duplicate JARs. The linked [troubleshooting guide](https://veritymods.wiki/troubleshooting/) separates failures into Minecraft/Java, Forge/JAR, AI backend, audio and multiplayer layers. That structure helps users preserve useful logs and test one cause at a time.

### [Verity TTS and Voice Setup](https://veritymods.wiki/voice-setup/)
The voice guide separates microphone capture, speech recognition, Groq or Ollama AI responses and text-to-speech output. It provides a staged test routine for API connection failures, silent replies, wrong input devices and application-specific audio routing while keeping credentials out of screenshots and logs.

### [Verity Mod on Aternos](https://veritymods.wiki/aternos-server-setup/)
The Aternos guide owns the platform-specific question of whether Verity JE can be used on a managed Aternos Java server. It tells readers to select Minecraft Java 1.20.1 with Forge, search the Aternos mod library, and compare the library entry with the verified Verity JE v6.0.0-beta.7 project record. It does not claim that a downloadable JAR can be uploaded through an unsupported Aternos path. When the project is not listed, it explains the safe fallback of choosing a host that explicitly permits custom Forge files, while preserving the official source and version checks.

### [Mod Background and Horror Features](https://veritymods.wiki/what-is-verity-mod/)
The overview describes Verity as an AI-powered companion implemented alongside programmed Minecraft entities and events. It covers the animated box, Verity Demon, darkness and horror atmosphere while avoiding claims that every dramatic video scene is a guaranteed feature. It also explains why a visible companion can load while Groq or Ollama conversation still fails, and why English-tested voice support is narrower than general AI text-language support.

### [Verity JE vs Verity Remake](https://veritymods.wiki/verity-je-vs-verity-remake/)
The comparison guide explains that Verity JE and Verity Remake are separate Minecraft Java projects. It compares the current Modrinth evidence with the Remake listing history, records that the commonly cited Remake route was not reliably verifiable on July 23, 2026, and explains why files, dependencies and setup instructions should never be mixed.

### [Verity Remake Download Status](https://veritymods.wiki/verity-remake/)
The dedicated Verity Remake guide answers the exact project query without presenting an unverified mirror as an official download. It separates historical 1.0.0 and 1.1.0 index records from a currently verified release, explains why an old listing can disappear, provides a publisher-first JAR verification workflow and points readers to the separate Verity JE route only when that project matches their needs.

## User Value
The site helps a player make several concrete decisions before changing a Minecraft installation. It answers whether the public Java mod exists, whether a file matches the current project release, whether the player owns the correct Minecraft edition, whether Forge and game versions match, and whether a Bedrock claim has comparable source evidence. It reduces the chance that a player downloads an unrelated remake, renames a Java file for Bedrock, exposes an API key or opens an important world without a backup.

After installation, the guides help locate the failing layer. A crash before the menu is treated differently from a missing mod entry, a silent companion, a microphone problem or a server mismatch. Groq and Ollama are documented as separate AI paths with different network, privacy and hardware requirements. Multiplayer guidance emphasizes matching client and server versions and protecting credentials rather than distributing them inside a public modpack.

Legal and editorial pages explain external download ownership, analytics and advertising, the correction process, trademarks and the site's independent status. Product facts remain linked to the published project so an automated system or human reader can distinguish site commentary from first-party claims.

## Latest Update Content
### [Verity JE v6.0.0-beta.7 Verification](https://veritymods.wiki/versions/)
On August 22, 2026, the site verified Verity JE v6.0.0-beta.7 as the newest published release returned by the project source. The file is verity-6.0.0-beta.7.jar, 257,909,430 bytes, published August 19, 2026 for Minecraft Java 1.20.1 with Forge. The version page also records the two preceding releases so users can compare a server requirement or identify a mislabeled mirror.

### [Direct Download and Setup Refresh](https://veritymods.wiki/)
On August 22, 2026, the homepage was refreshed around the verified v6.0.0-beta.7 download action. Version facts, the platform warning, Forge requirements and AI setup are visible before long explanatory content. Official project gallery images replace generic artwork, and the download action links to the published project CDN after an accessible 15-second countdown.

### [Bedrock Status Check](https://veritymods.wiki/bedrock/)
On August 22, 2026, no matching Modrinth Java-to-Bedrock package was verified from the project sources. Separate CurseForge pages named Verity - Bedrock Edition and Verity BE (Official) were recorded as independent listing sources, not silently merged with the Java project. The status page therefore does not offer an invented direct MCAddon download.

### [Verity Remake Availability Check](https://veritymods.wiki/verity-remake/)
On July 23, 2026, the site rechecked the CurseForge route most often associated with Verity Remake and could not verify a stable first-party file, current size or durable direct JAR URL. The page therefore uses an internal comparison CTA rather than a download button and documents what evidence would be required before the status changes.