Page 31 of 77
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Mon Apr 28, 2014 1:34 pm
by ciociokiller
yes, i put CE and infinity in the mods foldier but when i start modman nothing appear ( i tried with an old version and with the new one)
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Mon Apr 28, 2014 5:46 pm
by bleedinghippy
So I'm getting an error saying something along the lines of:
"Exception in thread "main" java.lang.Unsatisfiedlinkerror: sun.awt.windows.WTool.kit.startToolkitThread"
when I try to run the modman.exe, and when I try to run modman.jar nothing happens at all...
Is there something I can do to fix it? (I have tried running as admin and updating java)
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Mon Apr 28, 2014 10:13 pm
by Vhati
bleedinghippy wrote:So I'm getting an error saying something along the lines of:
"Exception in thread "main" java.lang.Unsatisfiedlinkerror: sun.awt.windows.WTool.kit.startToolkitThread"
That's a new one.
Try uninstalling and reinstalling Java.
And be sure to avoid the 64bit Java if you don't have a 64bit system.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Tue Apr 29, 2014 4:41 pm
by bleedinghippy
well reinstalling java worked, so thanks

Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Fri May 02, 2014 10:00 am
by Russian Rockman
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun May 04, 2014 1:43 pm
by Sinnaj63
I am sure this already has come up dozens of times, but since today, every time I try to install more than 0 mods, I get the messages "Patching failed: java.io.EOFException" and my files are corrupted.
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun May 04, 2014 2:57 pm
by kartoFlane
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun May 04, 2014 3:00 pm
by Sinnaj63
kartoFlane wrote:@Sinnaj
Try
this
It worked, thank you!
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun May 04, 2014 9:13 pm
by huntlol10
hi guys i need help installing captains edition (just the base mod i dont want any other addons). whenever i install patch the mod my game stops working , whenever i try to go on it says assertion failed and then some other stuff. i tried reinstalling and deleting backups and everything else people said to do. i have the drm free version i got from the website by the way. when i validate the mod i get this , no idea if it will help.
@ FTL Captains Edition 1.208b.ftl:
--------------------------------
> data/tooltips.xml.append
~ LF line endings (CR-LF is safest)
> data/events_rebel.xml.append
~ LF line endings (CR-LF is safest)
> data/events_crystal.xml.append
~ LF line endings (CR-LF is safest)
> data/events_pirate.xml.append
~ LF line endings (CR-LF is safest)
> data/events_nebula.xml.append
~ LF line endings (CR-LF is safest)
> data/autoBlueprints.xml.append
~ LF line endings (CR-LF is safest)
~ Strict XML Parser Issues:
! <!-- No other dashes should touch. -->
> data/events_boss.xml.append
~ LF line endings (CR-LF is safest)
> data/events_slug.xml.append
~ LF line endings (CR-LF is safest)
> data/events_fuel.xml.append
~ LF line endings (CR-LF is safest)
> data/events_imageList.xml.append
~ LF line endings (CR-LF is safest)
> data/events.xml.append
~ LF line endings (CR-LF is safest)
> data/blueprints.xml.append
~ LF line endings (CR-LF is safest)
> data/newEvents.xml.append
~ LF line endings (CR-LF is safest)
> data/events_ships.xml.append
~ LF line endings (CR-LF is safest)
> data/events_engi.xml.append
~ LF line endings (CR-LF is safest)
> data/sounds.xml.append
~ LF line endings (CR-LF is safest)
> data/sector_data.xml.append
~ LF line endings (CR-LF is safest)
> data/events_zoltan.xml.append
~ LF line endings (CR-LF is safest)
> data/events_mantis.xml.append
~ LF line endings (CR-LF is safest)
> data/events_rock.xml.append
~ LF line endings (CR-LF is safest)
Re: Slipstream Mod Manager v1.4 (2013-09-20)
Posted: Sun May 04, 2014 10:04 pm
by kartoFlane
@huntlol
Mod validation is only useful to mod authors to fix bugs related to the mod in question. In order for us to be able to help you, you need to provide us the contents of modman-log.txt (placed between [ code ][ /code ] tags for maximum readability)
However, the issue you're describing is quite common; most likely you either haven't updated FTL to AE (version 1.5.10), or you haven't updated SMM's backups -- to do the latter, follow the instructions
here.