Skip to content

Compatibility

Drehverschluss edited this page Nov 14, 2026 · 3 revisions

Compatibility

Required

Mod Version Note
NeoForge 21.1.265 or newer Minecraft 1.21.1

Client only. Packscope is not needed on a server. If it is installed on a dedicated server, it loads and does nothing. Players with Packscope can join servers without it, and the other way round.

Packed Packs

Mod Version Note
Packed Packs 2.3 or newer (tested with 2.4.0) Optional

Packscope hooks into the Packed Packs screen only through its public API. Without Packed Packs, none of that code is loaded. Details: Packed Packs.

KubeJS and other mods that inject packs

Some mods add packs straight to the game's resources, without the pack list, so they never show up in the pack screen. KubeJS does this with its virtual resource packs and with the files in the kubejs/assets folder.

Packscope reads the real resource stack after each resource reload and rates these packs where the game has them:

  • above "Mod Resources": as resource packs (they can override your packs and be overridden by them),
  • below "Mod Resources": as mod info, like the mod resources themselves.

For KubeJS, Packscope knows where it puts its packs: its "[Before Mods]" pack directly above the vanilla resources, its "[Last]" pack on top of everything, and the other KubeJS packs (including kubejs/assets) directly above the highest zip pack, so they move along when you move that pack. For other mods: a pack on top of everything stays on top, a pack directly above the vanilla resources stays there, and any other injected pack stays directly above the nearest pack below it.

Injected packs have no icon (there is no entry to put it on). They appear as "Pack (injected)" in tooltips, in the "All packs" view of the detail window and in the report ("injected (not in the pack screen) by mod"). Their ids do not start with file/, so a marking for them needs the exact id or regex: (see Intended conflicts).

Built-in packs of mods

  • Packs that mods show in the pack list (for example "Programmer Art", "High Contrast" or packs that come with a mod) are rated like any other resource pack.
  • Packs inside a mod jar are read straight from the jar, just as exactly as zip packs (scan jar in the report).
  • Some built-in packs hold child packs with their own files. They are rated as resource packs; the entry shows a combined icon (see Status icons).

Dynamic packs: "approximate"

A few mods build their packs while the game runs, with no file or folder behind them; for example Moonlight Lib, the compatibility packs of Eating Animation, and the virtual packs of KubeJS. Packscope cannot read such packs directly and lists them through the game instead, in the folders where resource files usually are (textures, models, blockstates, lang, sounds, font, atlases, shaders, particles, texts, optifine, emf, etf, and a few more) plus sounds.json. Files outside these folders can be missed.

These packs are marked approximate in the report (scan fallback (approximate), and one line under "Warnings"). They are read again after every resource reload, because their content can change. In the game there is no extra marking.

Other resource pack mods

  • Resource packs with OptiFine, ETF or EMF files (.properties, .jem, …): these files are rated as whole files like textures.
  • Packs that are hidden by mod code (active, but without an entry in the pack screen) are rated and shown as "(hidden)", see Conflict rules.

Not supported

  • Datapacks. The datapack screen stays unchanged, in vanilla and in Packed Packs.
  • Packs that are not active are not rated.

Clone this wiki locally