VVerity Mod

Verity mod not working — fixes and FAQ

If your Verity mod is not working, you are in the right place. This page covers the twelve most common reasons the Verity mod for Minecraft Java fails to load, fails to spawn the yellow ball, crashes on world join, or runs but does not behave as documented. Every fix here is taken from real support threads in the Verity mod Discord and from the github.com/Esylmu/Verity-CE issue tracker.

Start at the top of the list and work down. Most "Verity mod not working" cases are fixed by step 1, 2, or 3 below.

1. Wrong launcher — the most common reason Verity mod is not working

The Verity mod only runs on Lunar Client (for 1.20.1, 1.20.4, 1.21) or NeoForge (for the 1.21.1 community fork). If your Verity mod is not working, the very first thing to check is which launcher you used to install it.

The Verity mod will refuse to load under any of these:

  • Vanilla Minecraft launcher
  • CurseForge standalone launcher
  • Modrinth app
  • Prism launcher
  • MultiMC
  • Fabric (any version)
  • ATLauncher
  • GDLauncher

If you installed the Verity mod through any of the above, the mod will not load, the mod list will not show it, and there is no error message. This is the single most common reason the Verity mod is not working.

Fix: install Lunar Client from lunarclient.com. Launch, sign in with your Microsoft / Mojang account, click the Mods tab in the left sidebar, search Verity, click Install. The mod downloads in about 30 seconds. For the 1.21.1 community fork, install NeoForge 1.21.1 and drop the Verity-CE JAR from github.com/Esylmu/Verity-CE into your mods folder.

2. Mod version vs Minecraft version mismatch

Each Verity mod build targets exactly one Minecraft version. If your Verity mod is not working, the second thing to check is whether the mod build and the Minecraft version match.

Common mismatch cases:

  • You installed the 1.21 mod but your Minecraft version is 1.20.4 — the mod will silently fail to load
  • You installed the 1.21.1 community fork JAR on 1.21 (or vice versa) — NeoForge will refuse to load the JAR with a class version error
  • You installed the 1.20.1 mod on 1.20.4 — Lunar Client will silently skip it
  • You installed any 1.2x mod on 1.20.1 — the mod will fail to find GeckoLib bindings

Fix: in Lunar Client, click the version dropdown at the top right of the dashboard and pick the Minecraft version that matches the mod you installed. The modpack store then re-downloads the matching Verity build. In NeoForge, swap the Verity-CE JAR for the one matching the Minecraft version field in your NeoForge profile.

3. Lunar Client is out of date

Lunar Client bundles a custom LWJGL and audio stack. The Verity mod is built against a specific version of these. If your Lunar Client is more than 2 weeks old, the bundled LWJGL may be too old for the mod and the mod will fail to load silently. This is a frequent cause of "Verity mod not working after Lunar Client update" reports.

Fix: close Lunar Client entirely (Cmd-Q on macOS, Alt-F4 on Windows). Reopen. Lunar Client self-updates on launch. If it does not, download the latest installer from lunarclient.com and reinstall over the existing install — your modpack and Verity install will be preserved.

4. Outdated or wrong GeckoLib (1.21.1 community fork only)

The 1.21.1 community fork of the Verity mod (Verity-CE by Esylmu) requires GeckoLib 4.9.1 in your mods folder. Newer GeckoLib versions (4.10+, 5.x) will break entity rendering. If your Verity mod is not working on 1.21.1 specifically, and you see "Failed to register entity" in the log, this is almost always the cause.

Fix: download GeckoLib 4.9.1 from CurseForge and drop the JAR into your .minecraft/mods folder. Do not use 4.10 or newer.

The official 1.20.1 / 1.20.4 / 1.21 Verity mod on Lunar Client does not need a separate GeckoLib install — it is bundled in the modpack.

5. The yellow ball (Verity) never spawns

If the mod loads without errors but you do not see the yellow ball, the spawn conditions are not met. The Verity mod only spawns Verity after the player has all of these:

  • A bed placed and slept in at least once
  • Time of day is night (or the player is in a low-light area like a cave)
  • The player has not already triggered the encounter (each world has one Verity spawn per in-game "story cycle")
  • The world is in Survival or Hardcore mode (Creative mode skips the spawn)

Fix: load a survival world, place and sleep in a bed, wait for night OR enter a cave, then explore for about 10 minutes. Verity will spawn within 200 blocks of you.

If you spawned into a flat Creative world at noon, Verity will not appear. This is by design — the Verity mod is a survival-horror experience, not a Creative-mode decoration.

6. Mod loads but no Verity dialogue or voice

If Verity (the yellow ball) spawns but never speaks, the AI dialogue backend is blocked. The Verity mod streams dialogue from ThatMobb's backend at runtime. If the backend is unreachable (firewall, school / work network, or a temporary outage), Verity will spawn but be silent.

Fix: test your network access to api.verity-mod.com (or the URL listed in .minecraft/logs/latest.log under [Verity] Dialogue endpoint:). If it is blocked, switch networks or whitelist the endpoint. The 1.21.1 community fork on NeoForge supports a custom OpenAI-compatible API endpoint — you can self-host the dialogue model.

7. Performance — Verity mod makes the game lag

If the Verity mod is not working performance-wise (low FPS, audio stutter, world load lag), the cause is usually the spatial audio engine. The mod runs 8-12 simultaneous voice channels. On systems older than 2017, this can clip during long sessions.

Fix: lower the in-game sound slider to 80%. The spatial audio engine will automatically downmix to fewer channels. Also: disable shaders. Sodium + Iris are bundled and recommended; ReplayMod and shader mods are not. The Verity mod is built for vanilla-quality rendering with the bundled shader pack.

8. Minecraft crashes on world join after installing Verity

If Minecraft crashes the moment you load a world with the Verity mod installed, the most common cause is a duplicate mod. Lunar Client occasionally ships an older Verity mod in the modpack that conflicts with the one you just installed.

Fix: in Lunar Client, click Mods, search Verity. If two entries appear, disable the older one (the one with the smaller file size or older version number). Click Restart in the top right. Re-join the world.

9. Verity mod works on one version but not another

If the Verity mod works on 1.21 but not on 1.20.4 (or vice versa), and you used the same Lunar Client install, the cause is that you have the wrong Verity build for the second version. Lunar Client stores mod versions per Minecraft version, not globally.

Fix: switch to the second Minecraft version using the top-right dropdown, then click Mods and verify the Verity build version matches that Minecraft version. Lunar Client auto-downloads the right one, but if you previously disabled auto-updates the wrong build may be cached.

10. The mod disappeared after a Lunar Client update

This is normal Lunar Client behavior: when Lunar Client updates, the modpack is rebuilt and your mod settings may be reset. The Verity mod is reinstalled automatically.

Fix: in Lunar Client, click Mods, search Verity. If it is not there, search for "verity" (lowercase) — the search is case-insensitive but sometimes misses mixed-case entries. Re-enable it and click Restart.

11. Reading the log — debugging the Verity mod

If the Verity mod is not working and the above did not fix it, the next step is to read the log:

  1. Open .minecraft/logs/latest.log in a text editor
  2. Search for [Verity]
  3. Look for one of these lines:
    • [Verity] Mod loaded — the mod loaded successfully
    • [Verity] Failed to register entity — your GeckoLib is wrong version (1.21.1 only)
    • [Verity] Dialogue endpoint: ... — the AI backend URL (use this to test network access)
    • [Verity] Spawn conditions: <conditions> — shows why Verity has not spawned
    • No [Verity] lines at all — the mod did not load (wrong launcher, wrong version, or Lunar Client not updated)

If you cannot interpret the log, post the relevant section to the Verity mod Discord #support channel. Daily Q&A there from 50+ experienced players and the mod author.

12. Still stuck after trying everything above

If your Verity mod is not working after all 11 steps:

  • Join the Verity mod Discord (link in the site footer) and ask in #support — typical response time is under 30 minutes
  • For the 1.21.1 community fork, file an issue at github.com/Esylmu/Verity-CE
  • For the official 1.20.1 / 1.20.4 / 1.21 builds, file an issue on the Lunar Client modpack store page

Include in your report:

  1. Minecraft version (e.g. 1.21.1)
  2. Launcher (Lunar Client or NeoForge)
  3. Verity mod version (visible in the Mods list)
  4. Operating system
  5. The relevant section of .minecraft/logs/latest.log

A complete report gets a fix in 30 minutes. An incomplete report ("Verity mod not working help") takes 24 hours because the support team has to ask for each piece of info.

Related

Verity mod for Minecraft running on Lunar Client — yellow ball companion in a forest biome