Repository navigation
For Pack Makers
Packscope is made for sorting the resource packs of a modpack: you see at once which pack overrides which, and once the order is right, you can ship the result so that later changes stand out.
- Activate all packs you want to ship.
- Open the pack screen and look at the red and yellow icons first:
- Completely covered: the pack has no effect. Move it up, or remove it if it is only a copy (old version, same pack twice).
- Replaces sounds: the pack mutes sounds of a lower pack. Check that this is wanted.
- Then go through the packs with "Overrides" and "Is overridden". Click the icon and decide for each pair which pack should win; the texture preview shows every version side by side.
- Move packs until every pair is the right way round. The icons update before you press "Done".
When a pair is right, press "Mark as intended" in the detail window, or right-click the pack in Packed Packs and choose "Mark all as intended". When you are done, the list should only show grey icons (or none). See Intended conflicts.
Put the file into the config folder of your modpack. Your players get:
- grey icons for every conflict you already checked,
- normal icons for every new overlap, for example after a pack update or a pack they add themselves,
- "Against marking" if a pair ends up the wrong way round.
Do not ship the packscope/ folder. It only holds the cache and the reports of your own game.
Markings with file/... ids match by base name, so they keep working when a pack update changes the version in the
file name. Check the "Markings" section in "All packs" after an update: every marking should say "works".
"Export report" in the detail window or /packscope report writes packscope/reports/packscope-report.md: the full
load order with ids and status, every pair, every marking with its state. Handy for a changelog or for your pack
documentation. packscope-report.json has everything for scripts. See Reports and commands.
Packscope never changes the pack order. The order lives in options.txt (resourcePacks) as always. To ship it
with your modpack, use what you already use for default options (for example the Default Options mod or your own
options.txt). Packscope then shows the conflicts of the order your players actually get.
Packs made for another game version are only active if they are listed under incompatibleResourcePacks in
options.txt. Packscope rates them like every other active pack.
- With Packed Packs, sort in its screen: drag and drop with live icons, and the right-click items "Show conflicts", "Mark all as intended" and "Remove all markings". See Packed Packs.
- To group zip packs in Packed Packs 2.4 or newer, do not move them into a subfolder. List them under
packIdsin the folder'spacked_packs.folderpack.jsoninstead, see Packed Packs. They stay inresourcepacks/and keep their ids, sooptions.txt, your default options and your markings stay valid. - Moving a zip pack into a subfolder changes its id (
file/<folder>/<pack>). Markings still match by base name, butoptions.txtand your default options need the new id. - If a launcher installs and updates the packs of your modpack (for example the CurseForge app), leave the zip packs
directly in
resourcepacks/. Launchers expect them there and lose track of packs in subfolders. - Packs hidden in a profile are still active and still rated; they show up as "(hidden)".
Before a release, start the modpack once the way a new player does: move options.txt away (with Packed Packs also
config/packed_packs/__version.json), start the game and open the pack screen. The order should be the one you ship,
and every icon should be grey or gone.
Some mods turn their built-in packs on by themselves on the first start and remember this in a file of their own. If packs you turned off are active again, find that file and ship it with your modpack.
- No red icon left (or only packs you ship on purpose).
- No "Replaces sounds" you did not intend.
- Every remaining conflict marked; all icons grey or gone.
- "Markings" in "All packs": every entry says "works".
-
config/packscope-intended.jsonand your default options in the modpack, but not thepackscope/folder. - Tested as a new player: same order, only grey icons.
Packscope for NeoForge 1.21.1 · CurseForge · Source · Report a bug
Start
Using Packscope
For pack makers
Reference