Resource Pack Overrides Mod FAQ

Open the resource pack selection screen in-game and press R to reload the configuration file without restarting. Edit the config file to add the packs you want to control, then press R again to apply your changes instantly.

The config file lives in your instance's config folder, typically named after the mod. You can edit it directly while the game is running and press R on the resource pack screen to reload it.

Add the pack to the default/required list in the config file. The mod will force it to stay enabled every launch, even if a reload fails or a player tries to disable it.

Mark the pack as hidden in the config. It will still be active but won't appear in the selection list, so players can't accidentally turn it off.

Set the pack as locked in the config file. Locked packs are required and unmovable — players can see them but cannot change their enabled state or position.

Yes. The mod lets you override the display name and description shown in the selection screen. Set the custom name and description in the config for that pack.

Define the pack order in the config file. The mod enforces that order on every launch so packs don't shuffle around between sessions.

Yes, the mod can force a pack to appear as compatible with your version. Enable the compatibility override for that pack in the config.

You likely didn't reload the config. Press R on the resource pack selection screen to reload without restarting, or restart the game if the change still doesn't apply.

It only manages which packs are active and how they're displayed, so it adds negligible overhead. Conflicts are rare, but if another mod also forces resource packs, make sure they aren't fighting over the same pack.

Open the resource pack selection screen and press R to reload the config file, which is where you define your overrides. The config file is generated on first launch, so edit it while the game is running and reload to see changes immediately.

Add the pack to the default/required list in the config file so it stays active even after a reload or a fresh launch. This is what keeps modpack-critical packs from being dropped when something goes wrong.

Mark the pack as hidden in the config, and it disappears from the list players see. This stops players from disabling packs your modpack depends on.

If a pack isn't in the required list, a failed or partial reload can drop it. Add it to the always-enabled list so it survives reloads and restarts.

Set the pack as locked in the config, which makes it required and unmovable in the selection list. Players will see it but can't reorder or disable it.

Use the config's name and description overrides for that pack to change what shows in the selection menu. This is useful for cleaning up ugly internal pack names in a modpack.

Enable the compatibility override for that pack in the config. The mod then presents it as compatible even if its pack format doesn't match your game version.

It generally coexists with other pack-management mods, but if two mods try to control the same pack's enabled state you can get conflicts. Keep pack ordering and required lists defined in one place to avoid fights.

The mod only manages pack selection and ordering, so it doesn't add rendering overhead. Any performance change comes from the resource packs themselves, not from this mod.