FTL Captain's Edition 1.308/Inf 1.301b/EL 1.308

[Estel]

Also I recommend you to read the troubleshooting section at the first post of this thread. It if doesn't help, consult the "template" for asking question (aka - which details are a *must* for you to write in post asking for support), before asking the question again, please.

/Estel

[HarkintheMantis]

Just basics for CE
custom ships in game but not used at time of discovery

[stylesrj]

Just basics for CE
custom ships in game but not used at time of discovery

Did those custom ships modify the other ships in any way (for example, leaving the Kestrel with vanilla layouts?) Because Captain's Edition ships and their artillery are all custom.

[RAD-82]

I just downloaded 1.276 to work on a CE artillery addon for my Type-R Fleet. I noticed that there is a misc.xml.append file in it. That kind of defeats the purpose of the misc.xml.rawappend file that is also there. The files are different, so the contents of the .append file need to be copied to the .rawappend file before removing it.

edit#1:
I made a post last month about a Lanius Interceptor with bad doors. I've finally looked at the tb_anaerobic_interceptor.txt file and determined it has 4 bad doors. The two doors below the pilot room go off to the side rooms (weapons and shields) instead of the engines. The top door of the shield room goes to the engines instead of the pilot room. The bottom-left door of the shield room goes to the weapons room instead of the engines. I fixed the doors in the code below.

Code: Select all

X_OFFSET
0
Y_OFFSET
0
HORIZONTAL
0
VERTICAL
125
ELLIPSE
200
130
0
-95
ROOM
0
6
1
2
1
ROOM
1
3
0
2
1
ROOM
2
0
1
2
1
ROOM
3
2
0
1
2
ROOM
4
5
0
1
2
ROOM
5
3
1
2
2
DOOR
3
1
3
5
1
DOOR
4
1
1
5
0
DOOR
3
0
3
1
1
DOOR
6
1
4
0
1
DOOR
2
1
2
3
1
DOOR
5
0
1
4
1
DOOR
5
1
5
4
1
DOOR
3
1
1
5
0

[Sleeper Service]

I just downloaded 1.276 to work on a CE artillery addon for my Type-R Fleet. I noticed that there is a misc.xml.append file in it. That kind of defeats the purpose of the misc.xml.rawappend file that is also there. The files are different, so the contents of the .append file need to be copied to the .rawappend file before removing it.

I assumed that SMM can handle those files seperately, although I'm not sure whether this actually works. The question is whether the content of both files makes its way into the game right now... Thanks for pointing that out and thanks for the Lanius door fix, I'll see to this geting implemented.

Just basics for CE
custom ships in game but not used at time of discovery

Artillery seems to work without problems for the userbase, so chances are hight that the problem is caused by other mods your are. Potentially by one that overwrites player ships to their default, intentionally or not.

[kartoFlane]

*snip*

I assumed that SMM can handle those files seperately, although I'm not sure whether this actually works. The question is whether the content of both files makes its way into the game right now... Thanks for pointing that out and thanks for the Lanius door fix, I'll see to this geting implemented.

SMM does handle both files separately, however the order in which they are installed depends on the way the .ftl file has been packed (which may differ from tool to tool, system to system).
For the rawappend functionality to work, it should be applied after the normal append.

*checks CE's ftl*

Looks like that's the way it's packaged in CE... So all's well, I guess. Though it would still be better to test this in-game, to be sure.

[RAD-82]

It doesn't really matter if both are applied or not, or which order they are applied. The issue is that the .append file causes the spaces to disappear from existing text fields when it is applied, which is the whole point of the .rawappend existing.

[kartoFlane]

True. Though if the .rawappend contains all of the tags that have trailing spaces, then it's fine (though I doubt that it does).

[Sleeper Service]

Well at least that was the idea behind separating that part of the mod data between the .rawappend and the regular .append. The misc.rawappend contains weapon tooltips that before where displayed incorrectly as .appends. The misc.append contains all the weapon type tooltips, which where working fine as .appends. The question is whether there is an actual problem with any of those texts ingame right now. As far as I can tell not, but I'll check again.

[RAD-82]

True. Though if the .rawappend contains all of the tags that have trailing spaces, then it's fine (though I doubt that it does).

The misc.xml.rawappend in CE doesn't contain any tags with trailing spaces. It doesn't have to in order to do what it was designed for. The .rawappend was meant as a replacement for .append and never meant to be used with it. The .rawappend is supposed to preserve the trailing spaces in the original .xml file that the new data is being added to. By also having the .append file, the .rawappend becomes useless because the .append already removed the trailing spaces.

I don't know all of the mods used by Biohazard, but his game still shows missing spaces. http://i.imgur.com/UqOVtCr.jpg by3jumps

I'll just post a Vhati quote to see if that helps with any understanding of why the .append file has to be removed.

For every "*.xml" or "*.xml.append" or "*.append.xml" in a mod, the text is parsed into a tree of abstract objects that represent the xml tags. Spaces are omitted both during the parsing process and when the objects are ultimately printed back to text (just like indention and line breaks). Even when not appending, SMM 1.4 still parses the mod's file to tidy it into valid XML.

So currently any mod that touches "misc.xml" inadvertently strips the leading and trailing spaces from those strings.