'buildblugin' method without user prompting? And what about Projects?

I am currently developing an abstraction that allows for building and scripting standalone applications from patches or projects. The buildplugin message is seemingly equivalent to the buildcollective message to Max. From the reference we learn, that

The word buildcollective, followed by a reference name symbol and an output filename, builds a collective using the patcher associated with the symbol. The collective is named with the output filename.

So firstly, if a reference name is provided after opeing the patch to build under this name using the ; max openfile method, Max either opens a dialog for saving or throws an error, depending on the second argument provided when building…

if argument #2 is

a) path only — the dialog will open (a previously used path, not the one provided) and chooses the patch-name as name for the standalone

b) appname only — Max complains: buildcollective: location [appname.app] does not exist

c) path/appname — Max complains: [appname.app]: can't create file error -1409. Build Failed for [appname.app]

Since the buildcollective method behaves identically, I assume this is not what the developers had in mind? Otherwise the documentation isn't clear to me, nor would I know how to achieve an automatized cascade of building and scripting, especially batch-building, as it is quoted in the reference.

has anyone found a work-around or hidden method to let Max know what to build, where and under which name? In my humble perspective, this should be doable, especially since buildcollective could build a Max Collective while buildplugin could build a standalone without further user interaction or extra arguments required. Am I wrong?

And secondly, when working with Projects and building standalones from opened projects, the toplevel patch simply needs to be built from the menu while most project-specific dependencies are being copied into the internal Max Collective of the standalone. When using the ; max openfile method, however, one can only open a .maxpat and not a .maxproj. When opening the toplevel Max Patch of the Project, the dependencies are ignored (if the project isn't alraedy opened) and therefore would have to be copied/scripted manually into the standalone. Especially when considering batch processing, this can be pretty tricky. Is there an elegant way around this? How could a Project be built into a standalone using the above mentioned methods buildcollective or buildplugin?

I would highly appreciate support or feedback!

Big thanks.