Ship file - Revision history

Erandelax: /* Exterior props */

2018-02-15T01:07:04Z

‎Exterior props

Erandelax: /* Interior props */

2018-02-15T00:55:37Z

‎Interior props

Erandelax: /* Interior props */

2018-02-15T00:53:30Z

‎Interior props

Erandelax: Ship.xml description added

2018-02-15T00:52:20Z

Ship.xml description added

Erandelax at 00:16, 15 February 2018

2018-02-15T00:16:11Z

Erandelax: Page creation

2018-02-15T00:15:29Z

Page creation

New page

Exportable ship configuration file ('''*.shipz''') is a zip-like archive that is basically used to transfer ship blueprints between players outside of the Steam Workshop. However you can use it to process your ship with some external programs as well.

=== Archive structure ===
Currently (0.1.55d) the ship file archive contains such a list of text files:
# '''authorId''' - plain text file contains a steamID of the ship creator account. Ends with a line feed symbol.
# '''authorName''' - plain text file in theory, should contain the creator's name, but for now it contains just two new line symbols.
# '''device''' - JSON file describes the current state of all on-board devices and their configuration, access group lists and other stuff.
# '''displayName''' - plain text file contains a ship name. You can use game color codes to make it colorful, but beware - game loading screens and search filters do not get along with these too much. File ends with a line feed symbol.
# '''hash''' - plain text file contains a 64-byte hash md5-like hash of something. File ends with a line feed symbol.
# '''IRversion''' - plain text file contains current game version (aka "0.1.55d") when the save was taken. Ends with a line feed symbol.
# '''name''' - plain text file currently contains just two line feed symbols.
# '''publishedfileid''' - plain text file contains steamID of the Workshop item the ship file represents. For saves that have been never uploaded to the Steam Workshop it's "0". Two saves with the same "publishedfileid" will upload their content as a same workshop item, so if you want to upload several versions of the same ship to the Workshop, just export it, change "publishedfileid" to 0, import and upload as a new workshop item! File ends with a line feed symbol.
# '''ship''' - XML file contains a list of ship rooms, list of exterior props (type + position + color) and the history of the interior changes (so called "instructions"). However if you want to use it in order to cancel several changes of the ship interior, beware not to mess with the device file which should be edited as well.
# '''shipVersion''' - plain text file contains an integer number that increments each time ship is uploaded to the Workshop, so that game knows if the ship on your PC is older than the one you have online. File ends with a line feed symbol.

@@ Line 33: / Line 33: @@
    </CExteriorProp>
 '''PropTypeString''' defines the type of the exterior prop, '''PaletteIndex''' - used color scheme (seems like you can repaint all the ship with at once using "search and replace" function), '''Position''' - its coordinates and '''Transform''' - its position (direction). Complete assignment of each '''Transform''' subfield is not yet clear.
 ==== Interior props ====
 Interior props section has a '''PropManager''' header with same '''UseEditorModels''' and '''CreateDevices''' as in exterior section, but also has '''CurrentActivePalette''' field which corresponds to the selected color scheme you had while saving the ship in your editor.

@@ Line 35: / Line 35: @@
 ==== Interior props ====
 Interior props section has a '''PropManager''' header with same '''UseEditorModels''' and '''CreateDevices''' as in exterior section, but also has '''CurrentActivePalette''' field which corresponds to the selected color scheme you had while saving the ship in your editor.
-Second subsection is a '''RoomManager/Rooms''' which contains a list of ship rooms. Example:
+Second subsection is a '''RoomManager/Rooms''' which contains a list of ship rooms. Each room is marked as '''item''':
    <item>
      <key>

@@ Line 48: / Line 48: @@
      </value>
    </item>
-Here ''int''' and '''roomId''' contain the room id (the same exact number) and '''Name''' defines the room's name.
+Here '''int''' and '''roomId''' contain the room id (the same exact number) and '''Name''' defines the room's name.
 Third subsection is '''SavedInstructions''' which contains a list of so called '''ShipInterior_Instruction''' and is, basically, the history of all your interior edits. Feels like when game loads the ship file it simulates all the actions chain to "recreate" the ship. A list of known instructions:

@@ Line 1: / Line 1: @@
-Exportable ship configuration file ('''*.shipz''') is a zip-like archive that is basically used to transfer ship blueprints between players outside of the Steam Workshop. However you can use it to process your ship with some external programs as well.
+Exportable ship configuration file ('''*.shipz''') is a FAT-deflate zip-like archive that is basically used to transfer ship blueprints between players outside of the Steam Workshop. However you can use it to process your ship with some external programs as well.
 === Archive structure ===
@@ Line 13: / Line 13: @@
 # '''ship''' - XML file contains a list of ship rooms, list of exterior props (type + position + color) and the history of the interior changes (so called "instructions"). However if you want to use it in order to cancel several changes of the ship interior, beware not to mess with the device file which should be edited as well.
 # '''shipVersion''' - plain text file contains an integer number that increments each time ship is uploaded to the Workshop, so that game knows if the ship on your PC is older than the one you have online. File ends with a line feed symbol.

@@ Line 7: / Line 7: @@
 # '''device''' - JSON file describes the current state of all on-board devices and their configuration, access group lists and other stuff.
 # '''displayName''' - plain text file contains a ship name. You can use game color codes to make it colorful, but beware - game loading screens and search filters do not get along with these too much. File ends with a line feed symbol.
-# '''hash''' - plain text file contains a 64-byte hash md5-like hash of something. File ends with a line feed symbol.
+# '''hash''' - plain text file contains a 64-byte md5-like hash of something. File ends with a line feed symbol.
 # '''IRversion''' - plain text file contains current game version (aka "0.1.55d") when the save was taken. Ends with a line feed symbol.
 # '''name''' - plain text file currently contains just two line feed symbols.