The One Who Watches mod not working: fixes that solve most cases

When a Forge mod fails, the cause is usually one of a handful of mismatches. Work through this list in order; each step rules out a common cause before moving to rarer ones.

Start with the error message

Forge usually tells you what went wrong. If you get an error screen, read it before closing it. If the game closes with no screen, open logs/latest.log in your Minecraft folder, or the newest file in crash-reports, and search for "geckolib", "requires" or the mod's name. The line that names a missing mod or a version range is usually the answer.

1. GeckoLib missing or mismatched

Mod versions 1.4.0 and up require GeckoLib. Make sure exactly one GeckoLib file is in your mods folder and that it is built for Forge and the same game version as the mod. Details are in the GeckoLib guide.

2. Wrong Minecraft version

The mod has builds for 1.20.1 and 1.19.2 only. A 1.20.1 jar will not work on 1.20.4, 1.21 or 1.21.11, and a 1.19.2 jar will not work on 1.19.4. Check the version number in the file name against the version shown on your game's title screen. More in our 1.21 status page.

3. Wrong loader

The mod is Forge-only. It will not load on Fabric, Quilt or NeoForge. If you launched the vanilla profile by mistake, the mod simply will not appear; if you launched a Fabric profile, it will be ignored or flagged. See the Fabric page.

4. Forge build too old

Very early Forge builds for a game version sometimes lack features that later mods use. If the error points at Forge itself, install a current recommended Forge build for your version (47.x for 1.20.1, 43.x for 1.19.2).

5. Java version

Minecraft 1.20.1 and 1.19.2 both run on Java 17. The official launcher bundles the right Java automatically. Problems show up mostly with third-party launchers or custom Java paths: if you have pointed your profile at Java 8 or Java 21, switch it back to Java 17.

6. Conflict with another mod

If the mod works in a clean profile but not in your pack, another mod is involved. Remove half of your other mods, test, and keep halving until the problem disappears. This finds the culprit quickly even in large packs. Once you know which mod conflicts, check whether both have newer files.

7. Server and client don't match

CurseForge lists the environment as client and server. The server and every player need the mod and GeckoLib installed, in the same versions. A mismatch typically shows up as a disconnect when joining, with a message about missing or mismatched mods.

8. It loads, but nothing happens

This is often not a bug. The entity does not spawn during the first day/night cycle and may not appear every night. Open the Mods screen from the title menu to confirm the mod is listed. If it is, give the world a few in-game days before concluding anything is wrong. Tips for what comes next are in the survival guide.

Still stuck?

Reinstall from scratch with the install guide, using the file from the download section. If the issue persists with a clean setup, the mod's CurseForge comments and the author's community links are where bugs get reported.