Would be a nice opt-in thing to have where the deployment result is at most a single .cs and a single .sbc file.
The context for this is Steam/SE's lack of reliability in updating mods, most often happens when renaming/moving/deleting files would still remain in players' downloaded mod folder and either causing compile errors or insert sneaky bugs. For example, an issue still happening despite being fixed and not happening for the author, leading to wild goose chases.
Having all the sbc and cs data being packed into one would allow modders to rename/move/delete things on their real project while the user-side would at worst experience a different sbc data than the cs, but no smaller differences where only one file isn't updated and etc.
This also means any logged versions in the .cs files would at least guarantee that the entire script section is that version.
Would be a nice opt-in thing to have where the deployment result is at most a single .cs and a single .sbc file.
The context for this is Steam/SE's lack of reliability in updating mods, most often happens when renaming/moving/deleting files would still remain in players' downloaded mod folder and either causing compile errors or insert sneaky bugs. For example, an issue still happening despite being fixed and not happening for the author, leading to wild goose chases.
Having all the sbc and cs data being packed into one would allow modders to rename/move/delete things on their real project while the user-side would at worst experience a different sbc data than the cs, but no smaller differences where only one file isn't updated and etc.
This also means any logged versions in the .cs files would at least guarantee that the entire script section is that version.