Repository navigation
Data Pack Recovery
KineticCore helps diagnose data pack errors when opening a singleplayer world on Forge 1.20.1, NeoForge 1.21.1 and NeoForge 26.1.2. The failure page replaces the vanilla Safe Mode action with a temporary retry that preserves the other enabled packs.
Select a row to see the pack, resource file and underlying error. Scroll the details panel if the message is long. Errors may include malformed JSON, invalid fields, or missing references to biomes, structures, configured features and template pools.
The file belongs to the pack that actually supplied the failed resource, including when one pack overrides another. A referenced namespace does not necessarily identify the faulty pack. When the source cannot be determined, the page says so instead of guessing a file.
- Locate error file selects the file in Windows Explorer. For a ZIP pack, it selects the archive; the details show the resource path inside the archive.
-
Open core data packs opens
config/kineticcore/datapack/data. -
Open world data packs opens the current world's
datapacksdirectory.
Correct the resource or its missing dependency, then open the world again. Some missing tags are allowed by Minecraft as empty sets; these do not produce a fatal loading page merely because the tag is absent.
Use the reported cause to choose a repair:
| Error | What to check |
|---|---|
| Malformed JSON or invalid field values | Locate the reported file and correct its syntax, field types or values. |
| Missing required tag entries, biomes, structures or other references | Check whether the supplying mod or pack is missing or has an incompatible version, or update the broken reference. Tags that may be empty still follow Minecraft's rules. |
| Several packs override the same resource | Repair the pack identified as the actual source. Editing a lower-priority file alone will not fix the currently loaded resource. |
| Unresolved source or built-in mod resources | Read the complete error in the log and check the relevant mods, dependencies and references. Temporary skipping may be unavailable. |
For example, example.zip!/data/example/worldgen/biome/test.json identifies a file inside example.zip. Locate error file selects the archive; repair the JSON at the displayed internal path.
Temporarily skip and retry excludes the faulty local packs identified by the current diagnosis, then retries normal world loading. Unrelated packs remain enabled. If another error becomes visible, the next page shows it and allows another temporary retry where possible.
Skipping applies to the whole data pack, including its other data, rather than just the faulty JSON file. It lasts for this world-opening session, including subsequent data reloads while that world remains open.
The pack files are not changed, and the world's enabled/disabled pack choices are preserved. Leaving and reopening the world loads the original packs again, so an unrepaired error will appear again. Repair the error to stop it recurring.
The retry action is disabled when no new faulty local pack can be identified. Built-in resources and mod JARs are not automatically disabled. Use the diagnosis to correct the relevant pack or mod dependency instead.
Skipping world-generation packs can leave dimensions, biomes or other resources unavailable. Keep a backup of the world and repair its required data before relying on a temporary load for normal play.
Back or Esc cancels loading and releases the world so it can be opened again.
Dedicated servers write the pack, file and cause to their logs where the source can be determined. They do not open this page, launch Explorer, or automatically skip packs. Fix the reported files or dependencies before restarting the server.
On both singleplayer clients and servers, search logs/latest.log for Data pack loading failure or World data loading failure to find the loading diagnosis.