Subset Games Forum

This sounds like the data.dat and/or resource.dat aren't packed correctly. Might be worth asking over on the mod manager thread. Since I'm using windows, I'm not sure what the difference would be for ubuntu. You could try re-installing the mod if you haven't already. Are you able to use other mods, is mine the only one that's not working?

DrkTemplar wrote:

Fatty Limes wrote:I'm on ubuntu, and as soon as I select my ship and go to get started, the game immediately crashes with no error. Happens in 4.3 and 4.4. Tutorial works fine. Any ideas?

This sounds like the data.dat and/or resource.dat aren't packed correctly. Might be worth asking over on the mod manager thread.

@ Infinite Space_0.4.4.ftl: see below
  ------------------------------------
> data/autoBlueprints.xml.append
! <!-- No other dashes should touch. -->
! <teleporter..."room="9"...>
! <drones..."room="2"...>
! <teleporter..."room="9"...>
! <drones..."room="2"...>
! <shipBlueprint>...</ship>
  Done

> data/blueprints.xml.append
! <!-- No other dashes should touch. -->
! <tooltip...>...</desc>
! <speed...>...</image>
  Done

> data/events.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! <choice... hidden=... hidden=...>
! <textList>...</text>
! Fix this and try again:
  mismatched tag: line 882, column 3
  ~  ~  ~  ~  ~
  	</choice>
  ~  ~  ~  ~  ~

> data/events_crystal.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! <text...>...</event>
  Done

> data/events_engi.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! <text...>...</event>
! Fix this and try again:
  mismatched tag: line 432, column 2
  ~  ~  ~  ~  ~
  </choice>
  ~  ~  ~  ~  ~

> data/events_fuel.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! Fix this and try again:
  mismatched tag: line 528, column 2
  ~  ~  ~  ~  ~
  </event>
  ~  ~  ~  ~  ~

> data/events_mantis.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! <text...>...</event>
! Fix this and try again:
  mismatched tag: line 487, column 2
  ~  ~  ~  ~  ~
  </text>
  ~  ~  ~  ~  ~

> data/events_nebula.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! <choice... hidden=... hidden=...>
  Done

> data/events_pirate.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
  Done

> data/events_rebel.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
  Done

> data/events_rock.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
  Done

> data/events_ships.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! Fix this and try again:
  mismatched tag: line 405, column 3
  ~  ~  ~  ~  ~
  	</destroyed>
  ~  ~  ~  ~  ~

> data/events_slug.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! Fix this and try again:
  mismatched tag: line 247, column 3
  ~  ~  ~  ~  ~
  	</event>
  ~  ~  ~  ~  ~

> data/events_zoltan.xml
~ Unicode UTF-8 BOM detected. (ascii is safer)
! <!-- No other dashes should touch. -->
! Fix this and try again:
  mismatched tag: line 534, column 2
  ~  ~  ~  ~  ~
  </event>
  ~  ~  ~  ~  ~

> data/sector_data.xml.append
! <sectorDescription>...</sectorDescrption>
  Done

MrSmite wrote:Still enjoying this mod, just have one question: is it possible to make an event have a random outcome?

Example:

I repeatedly get an event about a prison riot [since the forums don't support SPOILER tags I'll stop there]... I get the same result. Always. As you can tell this gets monotonous after a while. Is it possible to have a player's choice pick a random result from a table:

Vhati wrote:

DrkTemplar wrote:

Fatty Limes wrote:I'm on ubuntu, and as soon as I select my ship and go to get started, the game immediately crashes with no error. Happens in 4.3 and 4.4. Tutorial works fine. Any ideas?

This sounds like the data.dat and/or resource.dat aren't packed correctly. Might be worth asking over on the mod manager thread.

It's probably the unicode, specifically the optional binary junk (BOM) at the start of such files (to identify the text inside as UTF-8, which is generally assumed anyway, and often identical to ascii which never has such binary). GMM 1.6 appends one file onto another, but doesn't strip the binary that then ends up in the middle of the combined document. GMM 1.7 will finally handle that; it'll also introduce diagnostic reports like this..

Other than the unicode interacting with GMM, all those are problems also present in vanilla, which don't crash the game, but are good to fix anyway.

Vhati wrote:It's probably the unicode, specifically the optional binary junk (BOM) at the start of such files (to identify the text inside as UTF-8, which is generally assumed anyway, and often identical to ascii which never has such binary). GMM 1.6 appends one file onto another, but doesn't strip the binary that then ends up in the middle of the combined document. GMM 1.7 will finally handle that; it'll also introduce diagnostic reports like this...

Other than the unicode interacting with GMM, all those are problems also present in vanilla, which don't crash the game, but are good to fix anyway.

DrkTemplar wrote:

Vhati wrote:GMM 1.6 appends one file onto another, but doesn't strip the binary that then ends up in the middle of the combined document.

I assume that means I should change the encoding for the files that aren't .append? [...] The originals are UTF, so I didn't change them until I had to (.append) for the mod manager.

DrkTemplar wrote:I admit I have little experience working with ANSI and UTF, so I don't know the difference really.

• ASCII ~ Plain unaccented latin alphabet, numbers, limited symbols... one byte per char.
  .
• ANSI ~ A family of single-byte variants like Windows-1252 that probably encode plain chars the same as ASCII; plus accents and such (whose bytes may have different meanings in each variant). The variants have no header and are often very similar, so it's difficult to tell which standard should be used to decode a file, unless you and the writer stick to a convention. Or read everything as one assumed variant and hope for the best.
  .
• UTF-8 w/o BOM ~ The plain characters are read/written as exactly the same bytes as ASCII. But extra exotic chars are also possible (which may be multiple bytes wide), like slanted quotes. Most apps should be using this by default these days.
  .
• UTF-8 w/BOM ~ The same as UTF-8, but with 0xEF,0xBB,0xBF binary at the start to identify that its chars are encoded as UTF-8. Lots of apps have trouble with this, because they assume one of the above and get surprised by the binary.
  Text editors that do support it may only write BOMs when resaving a file that had a header to begin with, and write new files without one. Apps in-the-know tend to hide the existence of BOMs from the user, which makes recognizing when it's causing problems in other apps 'fun'.
  .
• UTF-16 w/BOM ~ Every char is encoded as at least two bytes per letter to make room for loads more exotic chars. Comparing to UTF-8 for traditional chars, this amounts to 0x00 inserted after every byte as filler. There is always a BOM header, which additionally indicates whether each individual char's multiple bytes are in reverse order (hence the name ByteOrderMark). This occurs in Windows sometimes.
  .
• UTF-32 w/BOM ~ Every char is encoded as at least four bytes per letter to make room for an absurd amount of exotic chars. Lots of 0x00 padding in its bytes. There is always a BOM header, for the same purpose as UTF-16.