Introduction
Most "mod not working" problems are filename, conflict or browser problems, in that order. Work through this guide in order, changing one thing at a time, instead of reinstalling everything at once.
1. Check the filename first
Copy the filename from the mod page. Check capitalisation, check the .js ending, and check for a space before or after it. Re-enter it in the Mod Manager, press Enter, and refresh. This alone fixes most reports.
2. Check for conflicts
Disable all other mods, test this one alone, then re-enable the others one at a time. Mods that change the same elements can conflict, and the conflict may only appear when both are enabled together.
3. Check the browser
Update your browser to a current version. Glow is listed as Chrome only, so if you are using another browser for that mod, that is the expected explanation — not a bug in this directory. Try a clean browser profile or a different browser to rule out an extension blocking the game.
4. Check for an outdated mod
Game updates can break mods. Check the original source listing for a note about a newer version or a game update. This site's verification date is when this site checked the listing, not a mod release date, so it cannot tell you whether a mod is up to date with today's game.
5. Collect useful details before asking for help
Note the exact filename, your browser and version, which other mods were enabled, and what you expected to see versus what happened. A creator can help with that list; they cannot help with "it doesn't work" alone.
What not to do
- Do not download a "fixed" copy from an unknown site. Use the official list and repository.
- Do not enable ten mods at once to "test" — you will not know which one failed.
- Do not assume this directory is wrong because a mod broke after a game update. Check the source first.