Version string format: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
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 [https://en.wikipedia.org/wiki/Endianness#Little-endian little-endian] values. We'll use version 0.14.21 as an example: | 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 [https://en.wikipedia.org/wiki/Endianness#Little-endian little-endian] values. We'll use version 0.14.21 as an example: | ||
| Line 16: | Line 14: | ||
| Factorio's developer version number | | Factorio's developer version number | ||
|} | |} | ||
[[Category:Technical]] | |||
Revision as of 09:10, 12 November 2023
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 |