Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
-
- Posts: 65
- Joined: Sat Nov 03, 2012 10:55 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
I got a new problem : I can not open main.py as admin.
MY ENGLISH IS TERRIBLYHELL YEAH!
This text is presented by Google translate , my english skill and german.
This text is presented by Google translate , my english skill and german.
-
- Posts: 792
- Joined: Thu Oct 25, 2012 12:01 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Have you installed Python 2.7, and what message did you get when it failed?Todes_Schnitzel wrote:I got a new problem : I can not open main.py as admin.
-
- Posts: 14
- Joined: Mon Dec 10, 2012 6:27 am
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Vhati wrote:DAOWAce wrote:Vhati wrote:Additionally, your statement is false. 1.6 had the same files as 1.5, minus the src/ folder.
Download 1.5 and 1.6 for yourself; see the additional files in the archive.
snip
Can't tell if you're being a troll or just completely arrogant.
I deleted the src folder immediately after extracting 1.5 without checking its contents as I know 'src' folders are source codes.
1.6 had a bunch of extra files but no src folder.
Stop assuming everyone is a developer.
I'm not even going to bother responding to the disk space argument, as you clearly can't understand what 'small OS SSD' is.
I don't mean to sound rude, but I can't help the way people interpret my words.
-
- Posts: 792
- Joined: Thu Oct 25, 2012 12:01 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Vhati wrote:GMM 1.5/mods/Beginning Scrap Advantage.ftl
/mods/readme.txt
/src/ftldat.py
/src/license.txt
/src/main.py
/src/readme.txt
/src/__init__.py
/modman.exe
/modman.ini
/readme.txt
GMM 1.6/mods/Beginning Scrap Advantage.ftl
/mods/modorder.txt (1.5 generates this on first-run too)
/mods/readme.txt
/ftldat.py
/license.txt
/main.py
/__init__.py
/modman.exe
/modman.ini
/readme.txt
DAOWAce wrote:I deleted the src folder immediately after extracting 1.5 without checking its contents
1.6 had [...] no src folder.
Can't tell if you're being a troll or just completely arrogant.DAOWAce wrote:Vhati wrote:your statement is false. 1.6 had the same files as 1.5, minus the src/ folder.
Download 1.5 and 1.6 for yourself; see the additional files in the archive.
Though your signature helps: "I don't mean to sound rude, but I can't help the way people interpret my words."
If you have nothing to contribute, and no problem that needs tech support, please leave.
-
- Posts: 65
- Joined: Sat Nov 03, 2012 10:55 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Vhati wrote:Have you installed Python 2.7, and what message did you get when it failed?Todes_Schnitzel wrote:I got a new problem : I can not open main.py as admin.
yes and
Todes_Schnitzel wrote:I got a problem with Modman : it says that I haven't the supported version of python , but I installed the correct verion.
Need help!!!
and good this community help each other
MY ENGLISH IS TERRIBLYHELL YEAH!
This text is presented by Google translate , my english skill and german.
This text is presented by Google translate , my english skill and german.
-
- Posts: 792
- Joined: Thu Oct 25, 2012 12:01 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Excellent.Todes_Schnitzel wrote:yes.Vhati wrote:Have you installed Python 2.7Todes_Schnitzel wrote:I got a new problem : I can not open main.py as admin.
There's a bug in GMM 1.7's modman.exe that prevents it from ever finding Python, so it will always say that Python is missing.Todes_Schnitzel wrote:it says that I haven't the supported version of python , but I installed the correct verion.
Sorry. By that I meant: What message do you get when you follow the steps I linked here?Todes_Schnitzel wrote:it says that I haven't the supported version of pythonVhati wrote:and what message did you get when it failed?Todes_Schnitzel wrote:I can not open main.py
Those steps are a workaround to start the manager from a prompt, without using the broken modman.exe.
In other words, what message did you get when main.py failed?
-
- Posts: 65
- Joined: Mon Oct 08, 2012 1:23 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Sorry if you already solved this issue earlier, but, with over 80 pages of posts, I didn't bother to look hard for answers.
After placing a mod in the mods directory, opening up GMM, and patching a mod, I received an error message stating:
2013-04-02 21:06:42 ERROR: unpack requires a string argument of length 8
Traceback (most recent call last):
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\lib\killable_threading.py", line 99, in run
result = self._payload(*self._payload_args, **self._payload_kwargs)
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\main.py", line 801, in patch_dats
unpackdat(resource_dat_path, resource_unp_path)
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\main.py", line 603, in unpackdat
unpacker = ftldat.FTLPack(open(dat_path, "rb"))
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\lib\ftldat.py", line 193, in __init__
self._read_index()
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\lib\ftldat.py", line 231, in _read_index
size, lfn = struct.unpack('<LL', self.f.read(8))
error: unpack requires a string argument of length 8
2013-04-02 21:06:42 INFO:
2013-04-02 21:06:42 INFO: Patching failed.
Any ideas on what I should do?
After placing a mod in the mods directory, opening up GMM, and patching a mod, I received an error message stating:
2013-04-02 21:06:42 ERROR: unpack requires a string argument of length 8
Traceback (most recent call last):
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\lib\killable_threading.py", line 99, in run
result = self._payload(*self._payload_args, **self._payload_kwargs)
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\main.py", line 801, in patch_dats
unpackdat(resource_dat_path, resource_unp_path)
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\main.py", line 603, in unpackdat
unpacker = ftldat.FTLPack(open(dat_path, "rb"))
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\lib\ftldat.py", line 193, in __init__
self._read_index()
File "C:\Users\larry\Desktop\Grognaks Mod Manager v1.7 Win32\lib\ftldat.py", line 231, in _read_index
size, lfn = struct.unpack('<LL', self.f.read(8))
error: unpack requires a string argument of length 8
2013-04-02 21:06:42 INFO:
2013-04-02 21:06:42 INFO: Patching failed.
Any ideas on what I should do?
-
- Posts: 65
- Joined: Sat Nov 03, 2012 10:55 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
Vhati wrote:
Those steps are a workaround to start the manager from a prompt, without using the broken modman.exe.
In other words, what message did you get when main.py failed?
I get in german -->it can not find this path
I tiped this :
c:\Computer\Lokaler Datenträger (C)\Program Files (x86)\GMM\is
MY ENGLISH IS TERRIBLYHELL YEAH!
This text is presented by Google translate , my english skill and german.
This text is presented by Google translate , my english skill and german.
-
- Posts: 792
- Joined: Thu Oct 25, 2012 12:01 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
I see. You had trouble with the third step.Todes_Schnitzel wrote:Vhati wrote:what message did you get when main.py failed?
I get in german -->it can not find this path
I tiped this :
c:\Computer\Lokaler Datenträger (C)\Program Files (x86)\GMM\is
- Start Menu -> Programs -> Accessories.
- Right-click "Command Prompt" to run as an admin.
- Type this, then hit enter: cd "c:\Program Files (x86)\GMM"
- Type this, then hit enter: main.py
-
- Posts: 792
- Joined: Thu Oct 25, 2012 12:01 pm
Re: Grognak's Mod Manager v1.7 (Updated March 6, 2013!)
It's been a while. Last mention was page 75.Sovereighn2280 wrote:Sorry if you already solved this issue earlier, but, with over 80 pages of posts, I didn't bother to look hard for answers.
After placing a mod in the mods directory, opening up GMM, and patching a mod, I received an error message stating:2013-04-02 21:06:42 ERROR: unpack requires a string argument of length 8
That one's still a bit mysterious.
Best I can tell, it means data.dat or resource.dat had been corrupted somehow, and that confused GMM when it tried to read them prior to patching.
This should get things working again...
- Delete the files in GMM/backup/
- Steam edition: Delete the FTL/resources/ directory and "verify game cache".
- Standalone edition: Reinstall FTL.
- Then run GMM.
If you ever discover the way to get from a fresh FTL install to ??? to seeing that error in GMM again, that would be incredibly helpful.
Last edited by Vhati on Fri Apr 05, 2013 4:07 am, edited 1 time in total.