![Resource Pack Overrides [Forge & Fabric]](https://media.forgecdn.net/avatars/thumbnails/783/898/256/256/638132186121495014.png)
[Bug]: Specifying "fixed_position": true for Fabric Mods resources always loads it at the top of the list, ignoring other configs
ildiem opened this issue · 5 comments
Mod Loader (Required)
Fabric
Minecraft Version(s) (Required)
1.20.4
Mod Version(s) (Required)
20.4.2
Notes (Required)
I have my config set to load the Fabric Mods pack first, then various other packs on top of it. However, when the Fabric Mods pack has "fixed_position": true
under pack overrides, it always loads at the top of the list, regardless of the default_packs
list. Reloading the default packs list with T
restores the proper order, but it's a pain to have to do that every time the game boots up.
latest.log (Required)
https://gist.github.com/ildiem/21be308dcd5ad419c1e7448509790886
Would love for this to be further looked into. I've found fixed position can cause all sorts of issues with different packs, but I'd really like the option to have certain packs not be able to be moved out of position. As mentioned in the issue, holding T and reloading default packs fixes it, but again, that's not viable to do that every time.
Maybe you could force a check during loading that the order matches the order defined in default packs and go from there?
This same issue also occurs with the "Moonlight Mods Dynamic Assets" resource pack from the mod Moonlight Lib, with the same symptoms. Like "Fabric Mods", this resource pack also deliberately force-enables itself by default, and resets to the top of the list every boot if "fixed_position": true
is applied to it.
EDIT: It's not as simple as that! Setting "default_position": "BOTTOM"
for "Moonlight Mods Dynamic Assets" fixes the issue for that resource pack, but setting that for "Fabric Mods" does NOT fix the issue!
Honestly the option and actually RPO in general is not designed for built-in packs, only for user installed resource packs.
There are many ways in which mods can add built-in packs, I won’t even try to support that.
The current stance basically is if it works then good, otherwise it’s just unfortunate.
Has there been any progress on this over the last year @Fuzss ?
Edit: Opened issue on the Fabric Loader repo FabricMC/fabric-loader#1051