Version string format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
{| class="wikitable" | {| class="wikitable" | ||
| short | | [[Data_Types#short|short]] | ||
| Factorio's major version number (e.g. 0) | | Factorio's major version number (e.g. 0) | ||
|- | |- | ||
| short | | [[Data_Types#short|short]] | ||
| Factorio's minor version number (e.g. 14) | | Factorio's minor version number (e.g. 14) | ||
|- | |- | ||
| short | | [[Data_Types#short|short]] | ||
| Factorio's patch version number (e.g. 21) | | Factorio's patch version number (e.g. 21) | ||
|- | |- | ||
| short | | [[Data_Types#short|short]] | ||
| Unknown | | Unknown. Seems to be either 0 or 1. | ||
|} | |} | ||
Revision as of 01:48, 12 August 2017
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:
| short | Factorio's major version number (e.g. 0) |
| short | Factorio's minor version number (e.g. 14) |
| short | Factorio's patch version number (e.g. 21) |
| short | Unknown. Seems to be either 0 or 1. |