Repository navigation
Datapacks
TonyTurnover edited this page Oct 3, 2026
·
2 revisions
Almost everything the murk does to the world is data, so a datapack can change it without touching the config. The config lists only add to what datapacks define.
| You want to… | Use | Page |
|---|---|---|
| Turn one block or item into another under the murk |
fogged:murk_transform recipe |
Datapack Murk Transforms |
| Make the murk remove, spare, douse or snuff a block | block tags | Datapack Tags |
| Let a mob live under the fog | entity tag | Datapack Tags |
| Turn off or override a built-in pack | pack list or override files | Datapack Built-in Packs |
| Change where karst towers generate | biome modifier and structure sets | Datapack Worldgen |
my_pack/
├── pack.mcmeta
└── data/
├── my_pack/
│ └── recipe/
│ └── rust_iron_doors.json ← murk transforms
└── fogged/
└── tags/
├── block/
│ ├── scoured.json ← add blocks the murk removes
│ └── scour_immune.json ← spare blocks
└── entity_type/
└── breathes_murk.json ← mobs that live under the fog
pack.mcmeta for Minecraft 1.21.1:
{
"pack": {
"pack_format": 48,
"description": "My murk tweaks"
}
}- New world: Create World → More → Data Packs, and drag the folder or zip in.
-
Existing world: put it in
saves/<world>/datapacks/, then run/reload. -
Server: put it in
world/datapacks/, then run/reload.
Use /datapack list to check that the pack is enabled.
A mod uses the same files, placed under src/main/resources/data/. Fogged doesn't need to be a dependency. If Fogged isn't installed, the recipe type and tags are simply never read. To keep the log clean in that case, guard recipes with a NeoForge mod_loaded condition:
"neoforge:conditions": [{ "type": "neoforge:mod_loaded", "modid": "fogged" }]