Fix a datapack that does not show up or load

A missing datapack is usually a placement or format issue

Datapacks are world-specific. A pack can be perfectly valid and still not appear if it is inside the wrong save, trapped one folder too deep, disabled, or built for a different Minecraft version.

This guide focuses on making Minecraft see the pack first. Once it loads, use a separate compatibility guide if recipes, loot, structures, or worldgen still behave differently than expected.

Read the reload message before changing everything

The datapack list and reload output often tell you whether Minecraft found the pack but rejected it, or never found it at all. Those are different problems with different fixes.

How to know you are finished

For fix a datapack that does not show up or load, the work is not finished when a file is merely downloaded. Treat it as finished when you can point to the setup you changed, explain why it matches the intended Minecraft version or platform, and repeat the result in a clean test or copied world.

Use the checklist as the exit test: correct world folder used, pack.mcmeta is top-level, datapack is enabled. If one of those checks is still uncertain, stop and verify that detail before moving to a main world, public server, or shared pack.

If the first failure you hit is "The datapack does not appear in the list", start with this fix: Check the world path and folder depth. Minecraft usually cannot see a pack if pack.mcmeta is inside an extra nested folder. This keeps recovery tied to the guide instead of turning into unrelated guesswork.