Well, I was always making my archives OMOD-ready by including rather complex install scripts and omod conversion data. Now I also started making them BAIN-ready by maintaining the typical folder structure of a BAIN package. But lately I've come to a point where I can't by the life of me have both in 1 file anymore without rather serious annoyances.

At the end of scripted install, when everything successfully and confirmedly went exactly where it is supposed to be, OBMM starts comlaining about the folders "meshes" (and any subfolders I'm using as a target) and "textures" (subfolders likewise) not being part of my package. I explicitly read this up in the manual of OMOD scripting and it definitely states the function won't do this anymore... yet it still does. Now I thought by simply including semi-empty (I put a 0-byte txt file into each) target folders into my package OBMM would be sated, which it was, but unfortunately by doing this I broke the BAIN structure and it's no longer working as a BAIN package with optional subpackages.

Is there any known way I can get both, OMOD-ready and BAIN-ready in the same archive? Any help will be very much appreciated, thanks in advance!
This is the only thing holding me back from being done with Argonian Beautification's main files once and for all. The project reached its final state.

Scratch that!

For one it was an oversight by myself in not noticing it was a different function complaining than I always thought it was, and then I also found out I can do without this function altogether.

For reference, if you use "DontInstallAnyDatafiles" and then go copying files from your options folders say into "meshes/characters/argonian", while this folder is not part of your OMOD, you don't even need to call "InstallDataFolder" for "meshes/characters/argonian" (which will raise an error but still do as told). Problem solved, OBMM's no longer complaining about this folder not being part of my package. I can finish the project now.

This can be locked. Sorry for bothering.

Well, package the archive with a structure as if you were installing it via BAIN, then just add an OMOD script to that. All Natural might be a good example, as it is structured for BAIN but also has a Wizard and OMOD conversion data, including an OMOD script, and deals with resources and plugins alike in sub-folders.

EDIT: Ninja'd! :sadvaultboy: