With fabric#3164 allowing builtin resource pack extensions to override vanilla textures, we've got into a situation where we have two intentional behavior conflict with each other, which could theoretically be solved by a mixin on QFAPI's side but effectively? it would make QSL's behavior barely appear in practice;
In order to avoid a change on that area, I'd advocate for expanding the support for builtin resource pack extensions by having any resource pack be able to have such folders inside, in order to primarily allow builtin mod resource packs to modify vanilla Programmer's Art and High Contrast textures, since I believe having the mod itself attempt to override the vanilla textures without a builtin mod resource pack is bad practice due to how you can barely do anything about it and its potential to break stuff
Other than that? I believe that there's no other option but to flip the boolean in order to prevent breaking Fabric mods
With fabric#3164 allowing builtin resource pack extensions to override vanilla textures, we've got into a situation where we have two intentional behavior conflict with each other, which could theoretically be solved by a mixin on QFAPI's side but effectively? it would make QSL's behavior barely appear in practice;
In order to avoid a change on that area, I'd advocate for expanding the support for builtin resource pack extensions by having any resource pack be able to have such folders inside, in order to primarily allow builtin mod resource packs to modify vanilla Programmer's Art and High Contrast textures, since I believe having the mod itself attempt to override the vanilla textures without a builtin mod resource pack is bad practice due to how you can barely do anything about it and its potential to break stuff
Other than that? I believe that there's no other option but to flip the boolean in order to prevent breaking Fabric mods