Page 9 of 77
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Wed Oct 30, 2013 10:13 pm
by kartoFlane
The problem is that SMM doesn't have the rights to access stuff in Program Files. To solve this, run the manager as admin (right click on .exe > Run as admin...)
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Fri Nov 01, 2013 11:26 pm
by richeygator
If not for you the modding community would be about a tenth its current size.
Thank you for your great tool.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sat Nov 02, 2013 12:21 pm
by flint1996
i continue having the same error report on all mod even with those which come togethere with the mod manager.heres the report:
Patching failed: org.jdom2.IllegalDataException: The data "O6`@#` @eoe. H@eo oco6e##oo." is not legal for a JDOM character content: 0x001c is not a legal XML character.
can anyone tell me whats the problem and how to repair it?
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sat Nov 02, 2013 5:15 pm
by Sleeper Service
Hm I want to make use of the new capabilities slipstream offers, but it still does not run for me under Linux. Executing the modman.jar with Java 7 runtime simply does nothing. modman-log remains emtpy.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun Nov 03, 2013 1:03 am
by Vhati
flint1996 wrote:i continue having the same error report on all mods, even with those which come with the mod manager.
Here's the report:
Patching failed: org.jdom2.IllegalDataException: The data "O6`@#` @eoe. H@eo oco6e##oo." is not legal for a JDOM character content: 0x001c is not a legal XML character.
Copy/paste the contents of "modman-log.txt" into a reply here between [ code ] ... [ /code ] tags.
Since you're seeing that with all mods, the "If FTL's resources are corrupt" section in SMM's readme might help.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun Nov 03, 2013 1:06 am
by Vhati
Sleeper Service wrote:Hm I want to make use of the new capabilities slipstream offers, but it still does not run for me under Linux. Executing the modman.jar with Java 7 runtime simply does nothing. modman-log remains emtpy.
Run "java -version".
If it says 1.7.0_25, you'll either need to upgrade or run the mod manager with Java 1.6.
The logging library doesn't play nice with that specific version of Java.
Edit: That library just got an update to fix the hang, which will be included in the next SMM release.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Tue Nov 05, 2013 2:10 am
by agigabyte
When I run this it opens but the command prompt immediately closes before I can read the error.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Tue Nov 05, 2013 4:55 pm
by Vhati
agigabyte wrote:When I run this it opens but the command prompt immediately closes before I can read the error.
Which OS do you have?
Copy/paste the contents of "modman-log.txt" into a reply here, between [ code ] ... [ /code ] tags.
An error
Posted: Thu Nov 07, 2013 5:13 am
by Stefive
My pc is in norwegian, ingen tilgang means: No access
06:01:13.452 [AWT-EventQueue-0] INFO net.vhati.modmanager.ui.ManagerFrame -
06:01:13.452 [AWT-EventQueue-0] INFO net.vhati.modmanager.ui.ManagerFrame - Patching...
06:01:13.452 [AWT-EventQueue-0] INFO net.vhati.modmanager.ui.ManagerFrame -
06:01:13.453 [Thread-8] INFO net.vhati.modmanager.core.ModPatchThread - Restoring vanilla "data.dat"...
06:01:13.454 [Thread-8] ERROR net.vhati.modmanager.core.ModPatchThread - Patching failed. java.io.FileNotFoundException: C:\Program Files (x86)\FTL\resources\data.dat (Ingen tilgang)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at net.vhati.ftldat.FTLDat.copyFile(FTLDat.java:75)
at net.vhati.modmanager.core.ModPatchThread.patch(ModPatchThread.java:142)
at net.vhati.modmanager.core.ModPatchThread.run(ModPatchThread.java:88)
Any way to fix this?
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Thu Nov 07, 2013 10:41 am
by kartoFlane
@Stefive
You have to run SMM as admin. Right-click on the .exe and select "Run as administrator".
If you don't have admin privileges on your account, you'll have to keep your FTL installation outside of Program Files, since that folder is protected by Windows.