I think most things can be solved with MZP it just needs some time to research and test, but it is certainly powerful and the easiest way to install scripts when used with the drag and drop way. From my expierence I would suggest triggering a maxscript file that actually takes care of the installation simply because the…
I use source control (Perforce) to update everyone's machines at work. When max is first installed, I have them run a Setup.ms script that changes the $UserScripts, $UserMacros, $UserIcons, and $UserStartup directories to a folder under the source tree. From then on when the users get latest in Perforce they get any new…
TexTools works for me in that way that I develop and fix scripts from a local directory (somewhere on the desktop, myDocuments or some usbDrive). upon executing the main TexTools...ms script it imports all the other scripts (for every tools and macroscript) using fileIn ... and because the last file I executed was that…
I always work in local folders outside 3ds Max directory structure and keep every path defined through custom "symbolicPaths". In this way I can archive copies of the whole develop folder and have every path working just by changing one line of code. The mzp thing comes in the way only when I need to release a new version…