Skip to content

Reports and Commands

Drehverschluss edited this page Nov 14, 2026 · 2 revisions

Reports and commands

Packscope can write everything it knows into two files: a readable Markdown report and a complete JSON report for tools. Both go to packscope/reports/ in the game folder and are overwritten each time.

File Content
packscope/reports/packscope-report.md Readable report
packscope/reports/packscope-report.json Everything, for scripts and tools

Commands

Client commands; type them in the chat of any world (single player or on a server, the server does not need Packscope).

Command What it does
/packscope report Evaluates the applied pack order and writes both report files
/packscope rescan Drops the cache (in memory and in packscope/cache/), reads config/packscope-intended.json again, scans every pack again and writes both report files

The chat shows "Packscope: checking n active resource packs...", then a summary: "Packscope: n resource packs, x conflicts (y intended), z completely covered. Report: packscope-report.md". Click the file name to open the report. If something goes wrong: "Packscope: the report failed (…). Details are in the log."

Use /packscope rescan to force a completely new scan, for example after you changed pack files while the game runs or edited packscope-intended.json by hand.

Export from the detail window

The button "Export report" in the detail window writes the same two files, but for the order in the pack screen, also if you have not pressed "Done" yet. Then the message says "(order not applied yet, noted in the report)", and the report starts with:

Note: The load order is the one in the pack screen and is not applied yet (press "Done" to apply it).

Automatic report

With autoExportReport = true (see Configuration) Packscope writes the report after every resource reload (applying packs, F3+T, changing the language). This one only goes to the log, not to the chat.

The Markdown report

Head:

  • time, Packscope, Minecraft and NeoForge version,
  • number of active resource packs and mod/vanilla packs,
  • conflicts (intended), split into files, language keys and replaced sound events,
  • completely covered packs and packs against marking,
  • counted languages, scan and evaluation time, the settings ignoreIdentical, ignoredPaths and allLanguages.

Sections:

Section Content
Load order (top = highest priority) Table of every pack: name, id, type, scan, files, status, overrides, overridden, notes
Completely covered packs Why each of them has no effect (only if there is one)
Pack against pack Every pair that is not marked, with its numbers
Intended (marked as wanted) Every marking with its state; the marked conflicts are one line per pair here, not one per file
File conflicts File → winner → losers, outside the intended pairs
Language key conflicts Grouped by file and pack pair, up to 50 keys with texts each, then "… n more (full list in packscope-report.json)"
Replaced sound events Event, replacing pack, muted sounds
Hidden by filters File, filter pack, hidden packs
Harmless duplicates (identical files) Byte-identical copies
Replaces mod and vanilla resources (info) Numbers per pack and mod; the full list with reportListModOverrides = true
Warnings Problems while scanning, one line per kind (only if there are any)

Empty sections say so ("None outside the intended pairs.").

In the load order table, Type is resource pack, resource pack (hidden), resource pack (injected), mod or vanilla. Scan says how Packscope read the pack:

Scan Meaning
zip Zip file, read from its directory
folder Folder pack
jar Built-in pack inside a mod jar
lookup Mod or vanilla resources: only asked for the files that resource packs also have
fallback (approximate) Pack of an unknown kind, listed through the game; may miss files (see Compatibility)

Status uses the same names as the game: Completely covered, Against marking, Replaces sounds, Overrides and is overridden, Overrides other packs, Is overridden, Only intended conflicts, No conflict. Mod and vanilla packs have no status (–).

Notes can say: hidden (not in the pack screen), injected (not in the pack screen) by mod, part of parent, only copies of …, n identical, against marking, intended: overrides x, overridden y, hidden by filter, hides n (filter), .mcmeta without effect, and more.

The JSON report

Field Content
generated, versions, notes Time, versions, note about an order that is not applied
scanMillis, evaluationMillis Times
conflicts, intendedConflicts Totals
languages, settings Counted languages (empty = all), ignoreIdentical, ignoredPaths, allLanguages
order Every pack, top first: id, title, role, scan, approximate, hidden, injected, injectedBy, files, modId, parent; for resource packs also status, wins, losses, intendedWins, intendedLosses, againstMarking, deadMcmeta, copies, onlyCopies, hiddenByFilter, hidesOthers, replacedSoundEvents, intendedSoundEvents, lostSoundEvents, lostToMods, modOverrides, winsAgainst, losesTo, copiesOf, modOverridesByMod
pairs upper, lower, files, langKeys, soundEvents, filtered, intended, againstMarking
markings winner, loser, note, state, winnerPack, loserPack, conflicts
fileConflicts location, kind, winner, losers, harmless, deadMcmeta, intended, note
langConflicts location, language, key, winner, winnerText, losers (pack, text), intended
soundReplacements event, pack, replacedPacks, lostSounds, intended
filtered location, filterPack, hiddenPacks, intended
modOverrides, modOverrideList Mod and vanilla info, numbers per pack and mod, and the single entries
warnings All warnings

In the JSON report the status values are the fixed keys completely_covered, against_marking, replaces_sounds, wins_and_loses, wins, loses, intended_only and no_conflict. The JSON report always lists every language key.

Cache

  • Packscope keeps the scan of each pack in memory for the game session. A zip is scanned again when its size or date changes.
  • For folder packs it stores the checksums of the files in packscope/cache/ in the game folder, so the next start does not have to read every file again.
  • cacheEnabled = false turns both off; every evaluation then reads the packs again.
  • /packscope rescan clears both.

Clone this wiki locally