Skip to content

Conflict Rules

Drehverschluss edited this page Nov 14, 2026 · 1 revision

Conflict rules

Resource packs lie on top of each other: the highest pack in the list wins. Packscope compares every file under assets/ of every active pack (namespace:path, for example minecraft:textures/item/diamond.png). pack.mcmeta and pack.png in the root of a pack are not part of it.

Not every file that two packs share is a conflict. Some file types are merged by the game, so both packs take effect. Packscope rates every file type the way Minecraft 1.21.1 loads it.

File types

File type What the game does What Packscope counts
Textures, models, shaders, sounds (.ogg), particles, texts and every other file Whole file, the top pack wins Conflict per file
Blockstates blockstates/*.json Merged per block state Rated as a whole file, with the note merged per block state in game (see Known limitations)
.mcmeta next to a file (*.png.mcmeta: animation, blur) The top .mcmeta at or above the pack whose texture wins applies Conflict per file. A .mcmeta of a pack below the texture winner never applies: .mcmeta without effect, shown with the winner and not counted as a file
Language files lang/<language>.json Merged per key, the top pack wins per key Conflict per key that both packs have in the same language. New keys are no conflict. Only the languages the game loads count: en_us and the selected game language (all languages with allLanguages = true)
sounds.json Merged per sound event, unless an event has "replace": true Conflict only when a higher pack replaces an event with "replace": true that a lower resource pack also defines. The sounds of the lower pack are muted: status Replaces sounds
Atlases atlases/*.json, fonts font/*.json Merged Never a conflict
filter in pack.mcmeta Hides files of lower packs (also of mods and Minecraft); the pack's own files stay Own category "Hides with its filter". A hidden file of a lower pack counts like an override for "Overrides" / "Is overridden"
Overlays in pack.mcmeta Active overlay folders belong to the pack; within the pack a later overlay wins over the main folder Treated as normal files of the pack (only the overlays the game uses)
Invalid paths (for example capital letters) and files directly in assets/ Never loaded Left out
Byte-identical files (same size and CRC32) It does not matter who wins Duplicates, harmless, no conflict (ignoreIdentical, on by default). Also for merged files and sounds.json: an identical second copy adds nothing
Language entries with the same text Same result Harmless as well (with ignoreIdentical)

Files that match ignoredPaths never count (see Configuration).

Pairwise, like Mod Organizer 2

  • A pack overrides every lower pack that has the same file, also when a third pack above both wins in the end.
  • "Overridden by" always names the pack whose version reaches the game.
  • Copies make no pairs of their own: a byte-identical copy of the winning file counts like that file and does not override lower packs by itself.

Completely covered

A pack is completely covered when not a single element of it reaches the game: every file, language entry and sound event is overridden by higher packs, hidden by a filter, or a byte-identical copy of a higher pack. This includes a pack that consists only of copies, for example the same pack twice, or an old and a new version where the old one adds nothing; then the tooltip says "Only copies of …". The status stays visible when the conflicts are marked as intended.

Mods and Minecraft

Replacing textures, models or language entries of mods and of Minecraft itself is what resource packs are for. Packscope shows it as information only, never as a warning:

  • grey line in the tooltip: "Replaces 37 elements of mods/Minecraft (Minecraft 30, Some Mod 7)",
  • section "Replaces mod/Minecraft files" in the detail window, grouped by mod,
  • a section in the report, with the numbers per mod (full list with reportListModOverrides = true).

On NeoForge, "Mod Resources" holds one hidden pack per mod; Packscope looks into each of them, so the info is grouped by the mod that owns the file. If a resource pack lies below a mod, the mod wins: "n elements overridden by mods".

Hidden and injected packs

  • Hidden packs: mod code can add packs that are active but have no entry in the pack screen. They are loaded, so Packscope rates them like every other resource pack and shows them as "Pack (hidden)". The same goes for packs hidden in a Packed Packs profile.
  • Injected packs: some mods put packs straight into the game's resources, without the pack list (for example KubeJS). Packscope reads the real resource stack and rates them where the game has them: above "Mod Resources" as resource packs, below as mod info. They are shown as "Pack (injected)". See Compatibility.
  • Children of other packs: a built-in pack can hold child packs with their own files. These children are rated as resource packs (the last child is the highest); the entry in the list shows a combined icon (see Status icons). Only the children of "Mod Resources" are mods.

Incompatible and inactive packs

  • Packs made for another game version ("incompatible") are only active if you confirmed them. Active ones are rated like every other pack.
  • Packs that are not active are not rated. Packscope does not tell what an inactive pack would override.

Clone this wiki locally