Grognak's Mod Manager v1.7 (Updated March 6, 2013!)

[Brink]

If your antivirus reads it as a threat (false positive) it may eliminate it before it even gets written to your drive.

you may speak the truth gonna check avast and see what happens

[mrepikfail]

I was wondering, every time I download the the program it says it's a backdoor trojan and the file is always corrupt, is there any way to fix this?

[GroxGlitch]

I was wondering, every time I download the the program it says it's a backdoor trojan and the file is always corrupt, is there any way to fix this?

It's a false positive. Many AV programs are nailing parts of this program for various reasons. Some read it was a trogan, some read it was malwaregen, some read it as something else.
Little bit of AV Info: Antiviruses don't recognize entire viruses, the look for snippets of data called "definitions". Mind, definitions are not automatically a virus, but they're a good indicator. If an AV program detects a sequence of data that is similar or identical to a definition in it's database, it'll flag it as a virus, matching it to a particular virus based upon the data detected. Various AV's have differing definitions, as not all av system programmers use the same definitions, so what snippet Kapersky reads as a trojan, may be considered as a Malware by, saaay, Avast!. This is why it's a good idea to have multiple AV programs to get a second and, if deemed needed, a third opinion.
So far, Grognak has been sending messages to the av producers, but it may take them a while to verify the safety of the file and push a definition update. So please, be patient, it should be resolved in time. In the interum, there's plenty of time to provide moral support to Grognak, as this has, in all probability, been a headache and a half \:|

[Grognak]

Version 1.4 has been released.

Patch Notes:
- New custom GUI
- No longer reliant on EasyGUI
- Better ZIP file support
- More relevant error messages
- Now offers the option of running the game after you're done patching (Windows only)
- Now removes deleted mods from modorder.txt
- Now supports .append.xml as well as .xml.append
- Improved Mac OS X support
(Thanks to ser_aerochorro for his contributions!)

[GroxGlitch]

APOLOGIES FOR THE SECOND RAPID POST
Preliminarily, Avast! no longer appears to flag Modman.exe as the Malwaregen virus, so Avast! users should have access back!

[Grognak]

I am so so happy right now to hear that.

[Whale Cancer]

I updated and...

The 'do you want to run FTL' doesn't work and the 'select all' option for which mods to load is missed

Edit: "I am experiencing crashes on previously stable .ftl files" needs more testing before I am confident enough to assert this.

I'm rolling back to 1.3 for now.

I'm on a Windows 7 system.

Edit: Specifically re: FTL autorun, the FTL window would pop up for a second and then close.

[Grognak]

That's odd. I just tried it again and it worked perfectly on my system.

[Law]

So, I've updated.

Only a little thing I've needed to change, since it didn't run when I tried to on OS X.

Code: Select all

Traceback (most recent call last):
  File "./main.py", line 407, in <module>
    dir_root = realpath[:realpath.rindex("\\")]
ValueError: substring not found

I've replaced realpath[:realpath.rindex("\\")] with os.getcwd() + '/' and it seems to work fine, though it got a segment fault after successfully patching. I fixed that by adding exit() right at the last line.

Else, it's quite a neat looking mod manager now.

[jaillyn]

I'm using Windows 7 64 Bit, and when I run manmod.exe all I get is a blank command prompt looking window that does nothing.