Repository navigation
[Bug] Packed Packs default resources overriden #102
Description
Minecraft Version
1.21.1
Mod Loader
NeoForge
Describe the Issue
Setting a default resource pack profile with Packed Packs is overriden by DefaultOptions even if no packs are set by default options.
I want to use the former for my resourcepack management as it's cleaner and easier to update, and only the latter for a few options and keybinds.
Steps to reproduce:
- Have no options file
- Have a default options option file with a few settings (but NOT any resource packs) ex:
version:3955
entityDistanceScaling:2.5
renderDistance:16
simulationDistance:12
skipMultiplayerWarning:true
soundCategory_master:0.50
- Have a default Packed Packs resource pack profile with resource packs
Ensureconfig\packed_packs\config.meta.jsonhas a default profile defined and it matches a file the config! - Launch game
- Observe default packs fail to load
DefaultOptions should not have this behavior if it does not have any resource packs defined, no?
I also tried removing the line related to resourcepacks in defaultoptions's config file as well but that immediately came back
Logs
Apologies for modpack spam
Working default packs with Packed Packs and no \config\defaultoptions\options.txt file
https://mclo.gs/iAzWOUB
Broken default packs with Packed Packs and a stripped down \config\defaultoptions\options.txt file
(Does not contain any resource packs but still overrides/prevents Packed Packs from registering the defaults)
https://mclo.gs/TMKuNKO
Activity
BlayTheNinth commentedon Jul 16, 2026
This is more of an issue on Packed Packs side in my opinion.
Their README states:
However, relying on
options.txtto be missing for applying these changes is unreliable, because some launchers (Modrinth App) and some mods pre-initialize an options.txt file. Default Options does so because it's in its name, but also various performance mods have done this in the past, I believe there was even a period where a mod loader did.This is why Default Options introduced a journal to track changes it applied for its new
defaultResourcePacksoption. That way they will be applied without the mod needing to know whether an already existingoptions.txtwas placed there with explicit user intent (e.g. enabling shared default options in their launcher), or just happened to be there (e.g. by default on some launchers or as part of some random mod).It would probably be best for Packed Packs to adopt a similar approach to ensure stability in all environments.