Version string format: Difference between revisions

From Official Factorio Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(5 intermediate revisions by 5 users not shown)
Line 4: Line 4:


{| class="wikitable"
{| class="wikitable"
| short
| [[Data_Types#unsigned short|unsigned short]]
| Factorio's major version number (e.g. 0)
| Factorio's major version number (e.g. 0)
|-
|-
| short
| [[Data_Types#unsigned short|unsigned short]]
| Factorio's minor version number (e.g. 14)
| Factorio's minor version number (e.g. 14)
|-
|-
| short
| [[Data_Types#unsigned short|unsigned short]]
| Factorio's patch version number (e.g. 21)
| Factorio's patch version number (e.g. 21)
|-
|-
| short
| [[Data_Types#unsigned short|unsigned short]]
| Unknown - seems to be 0.
| Factorio's developer version number
|}
|}

Latest revision as of 20:26, 20 March 2018


Factorio uses a common encoding method to serialize the version string in binary data that's present in multiple places, such as the map exchange string and save game file format. It consists of four consecutive 2-byte unsigned little-endian values. We'll use version 0.14.21 as an example:

unsigned short Factorio's major version number (e.g. 0)
unsigned short Factorio's minor version number (e.g. 14)
unsigned short Factorio's patch version number (e.g. 21)
unsigned short Factorio's developer version number