Subset Games Forum

KarlssoNN wrote:"Extended Pursuit Indicator x24 with numbers" is not working for me [...] been using the latest beta game version 1.6.2. Mentioned mod was working with older Slipstream version 1.6.

It sounds like you're saying a mod that had been made for FTL 1.5.13... isn't working on FTL 1.6.2?

*clickety-click*

Confirmed. That is the case.
SMM 1.9 can still successfully apply that mod to FTL 1.5.13.
SMM 1.9 w/ FTL 1.6.2 shows no visible changes.

That mod only contains one file ("img/ipad/map/map_warningcircle_point.png"). Vanilla FTL 1.6.2 no longer has such a file, so the result is you're modding something the game isn't paying attention to - hence no effect.

Not my fault. You should reply to the author's thread about releasing a variant specifically for FTL 1.6.2.

KarlssoNN wrote:Thanks for your fine service!!! Havin't tried vanilla but this game modded is a blast!!!

*Takes a bow*

Figured that was a possibility, should have done some testing, Thanks for your time!

slowriderxcorps wrote:... because we're kind of running out of version numbers to go up to!

... not quite. Versioning that go 1.10 from 1.9 isn't quite unheard of. And that might be the next version they're going to, depending on how they number their version

My slipstream mod manager isnt working properly and keeps asking me to find this file:
(FTL dir)/reasources/data.dat
What does this mean can someone help me

Gearbull42 wrote:My slipstream mod manager isnt working properly and keeps asking me to find this file:
(FTL dir)/reasources/data.dat
What does this mean can someone help me

The Mod Manager is up to 1.9 now, which asks a slightly different question.
It supports FTL 1.6.1+ but still works with FTL 1.01-1.5.13.

My previous stable release, SMM 1.6, only supported FTL 1.01-1.5.13.

As for the meaning... The mod manager splices in new images & text into the game. FTL keeps that stuff in the directory where you (or Steam) installed it. Older editions of FTL had a file named "data.dat". The new FTL 1.6.1+ has a file named "ftl.dat" that had a different file format than before - hence the need for a newer mod manager to recognize it.

Once it knows where to find the game's resources, Slipstream can start patching in mods.

.
.
v1.9.1 has been released:

• Edited a comment in boilerplate mod metadata to include AE ships.
• Made the comments in boilerplace mod metadata optional.
• Fixed omitted Validate warnings for PNG files.
• Disabled XML escaping when reencoding to ensure invalid chars cause an error.
• Added Validate warnings about FTL 1.6.1+ for TTF, MP3, and PNG files.
• Added a Validate warning about FTL 1.5.13 for chars outside windows-1252.
• Changed logging framework to SLF4J/Logback.
• Changed command line parser to picocli.
• Migrated to the Apache HttpComponents library.
• Made launcher scripts on OSX find java the recommended way.

This update is primarily for mod developers.

The Validate button will generate migration-related warnings for FTL 1.6.1+ and backward compatibility warnings for FTL 1.5.13.
.
.
.
.

Very useful, thank you!

I've also been having issues using the Extended Pursuit Indicator indicator mod with the Slipstream mod manager. I have only recently started playing again and decided to download this mod. I followed the instructions on the Subset games Mods page but I recieve an error whenever I try to validate the mod:
@ Extended Pursuit Indicater x24 with numbers v.1.2.ftl:
------------------------------------------------------

~ This mod doesn't append. It clobbers.


FTL itself can tolerate lots of XML typos and still run. But malformed XML may break tools that do proper parsing, and it hinders the development of new tools.

Since v1.2, Slipstream will try to parse XML while patching: first strictly, then failing over to a sloppy parser. The sloppy parser will tolerate similar errors, at the risk of unforseen behavior, so satisfying the strict parser is advised.

Does anyone know a fix?

@Lebebzio: I posted a response in that thread.

7636kei wrote: Versioning that go 1.10 from 1.9 isn't quite unheard of. And that might be the next version they're going to, depending on how they number their version

Disregard, I apparently can't read.

I am relatively certain that bunch of our favorite FTL modders/mod tools creators are competent enough for being able to *properly* count from 1 to 10. So, I assume that such blasphemy won't fall upon us, now or ever. Delicious Friend.
(seriously though, I know such things happen, but versioning like that, from x.10 to x.9 is literally dumbest practice that may happen, breaking everything, from auto-sorting to update scripts).

BTW, thank you OP for keeping the tool alive, even after all those years and such unexpected update (I am only one that think they're cleaning for Android release?)!