Hi,
after much frustration when releasing my own scripts for a while, I’ve written an mzp-builder. It’s a simple tool to build mzp-files from a set of files of your choice: scripts, presets, art and so on. You write an ini-file with the relevant filepaths and the script creates your run-file and mzp-file.
I know there are other solutions available which do much more, but this one’s a simple solution to a recurring frustration of creating run- and mzp-files by hand.
You can read more about it on my blog or get the script on github or Scriptspot
Klaas,
i’m absolutely sure that your new tool is the same perfect as all your others that in know. but my problem is…
am only i paranoid by not installing any MZP files in my max? i just CAN’T DO it before i would know for sure where it will be installed.
Denis,
When installing an mzp or any other installer in that case there’s a certain amount of trust involved. I don’t think it’s paranoid, I always check out the source to see if I can trust the author.
I could have my script generate a readme file which tells you which files go where before you even install a thing.
Klaas
So,
I’ve added a readme when an mzp-file is created. The readme describes which files go where. While I was at it, I added a place for the developer to display a small personal message, license, support and contact information. This should develop a bit more trust.
In the meanwhile this should make it easy for a scripter to do so, release after release.
Get it on github or scriptspot.