It depends on python being on the path; apparently the python installer doesn't do that automatically.

For the next version I'll also check to see if C: or D:\python* exists as well.

This is just a notice that I made a mistake with modman.exe; it will run for about nobody. Run main.py directly instead.

Vhati wrote:"modman.command" is missing from the *.tar.gz.
And license.txt is in a src/ directory instead of alongside the readme?

D'oh. Fixed for both. I guess src is a bit obsolete now.

Version 1.7.0 released: 1.7: - Lowered the required Python version to 2.6 - Added a Linux/Mac launcher (modman.command) to guarantee a terminal - Added forum-scraped metadata for most mod files (based on their md5) - Added a right-click clipboard menu to the text area. - Added ini setting: never_run...

It works for me; double check to make sure it's not on your end.

Version 1.6 (the "Holy crap Vhati did a lot" edition) released! Changelog: - GMM no longer needs to be placed in the FTL directory - Added ini setting: ftl_dats_path - Added drag-and-drop mod reordering - Added "Toggle All" button - Dats are unpacked to temp folders and deleted a...

@saren12, You need to make sure to move the .ini over with the source files

@LBraden, Yeah that's a completely different error. I'm still not positive what causes it; still working on it.

Modman.exe is a python file on my PC. Can you try installing python 2.7.3 and re-downloading GMM? Alas did not work, but they appear the same error message, I can't read all of it before it goes and trying to click prt scrn is a little hard before it goes too as it is only up for a second or two. B...

You should copy over the files and use modman.exe rather then the python files.

hmm, I copied everything from the folder over into my main FTL folder, but I kept everything in the src folder in there (often do with mods as I have had a few where those files if "loose" can cause a bug or two, or they are just developer files, like in Fallout Mod Manager) Sounds good. ...