Reports

Reports

Applies to all versions.

Data Miner writes everything under a folder in the game (or server) directory:

• data_miner/info_client/ when running on the client,
• data_miner/info_server/ when running on a dedicated server.

The folders are created on startup.

data_miner/info_client/          (or info_server/)
├── startup/
│   ├── registries/          registry dump (JSON per registry)
│   ├── logs/
│   │   ├── captured.log     WARN/ERROR lines from other mods
│   │   └── issues.jsonl     detected issues, one JSON object per line
│   ├── mods.json            loaded mods with versions and dependencies
│   ├── mod_impact.json      blocks, items and entities per namespace
│   ├── mod_analysis.json    per-mod profile with potential issues
│   ├── info.json            Minecraft and Java versions, OS, memory, locale
│   └── errors/              exceptions during startup
├── performance/
│   ├── *.json               FPS / MSPT sessions
│   └── latency/*.json       latency sessions
└── events/
    ├── *.json               event traces
    └── errors/              exceptions in the event tracer

Registry dump

/data_miner dump, or every start with dumpOnStartup = true, writes one JSON file per registry to startup/registries/: blocks.json, items.json, entities.json, status_effects.json, sound_events.json, creative_tabs.json, potions.json, villager_professions.json and attributes.json. Each registry can be turned off in the Configuration.

Mod analysis

mods.json, mod_impact.json and mod_analysis.json list the loaded mods, count what each namespace registers, and note potential problems per mod. They are generated on startup and again with /data_miner mods analyze.

Captured logs and known issues

Data Miner hooks into the game log and copies every WARN and ERROR line from other mods into startup/logs/captured.log, so they are easy to review without the rest of the log.

Lines that match a known problem are also written to startup/logs/issues.jsonl and tagged with its type:

Type	Meaning
missing_refmap	A mixin refmap could not be found.
access_transformer	An access transformer entry failed to apply.
missing_texture	A texture or model could not be found.
pack_metadata	A resource or data pack has a metadata problem.
lootr_missing_loot_table	Lootr reports a missing loot table.

Performance

/data_miner perf start / stop records FPS (client) and MSPT; the report goes to performance/.

Latency

The latency tracer measures how long eating and block breaking take and counts slow server ticks (more than 50 ms). /data_miner latency stats shows the numbers in chat; stop writes the report to performance/latency/.

Events

/data_miner events start / stop traces player interactions and ticks, block placement, entity joins, damage and deaths, and chunk loads, and writes the trace to events/.

Client reload reporting

On NeoForge 26.2.0.57 (1.2.x) the client detects every resource reload (F3+T, changing resource packs…) and sends it to the server, which logs a warning with the player's name and the stack trace that caused the reload. This helps find mods that trigger unexpected reloads.