Skip to main content ↑ ↓
Topic: Anomalies with version.h (Read 1717 times) previous topic - next topic

Anomalies with version.h

Looking at the latest nightly of Simutrans-Standard (trunk, not the RC branch), version.h looks like this:

Code: [Select]
#ifndef simversion_h
#define simversion_h

#define MAKEOBJ_VERSION "50"

#define VERSION_NUMBER "102.3 Nightly"
#define WIDE_VERSION_NUMBER L"102.3 Nightly"

#define VERSION_DATE __DATE__

#define SAVEGAME_PREFIX  "Simutrans "
#define XML_SAVEGAME_PREFIX  "<?xml version=\"1.0\"?>"

#define SAVEGAME_VER_NR  "0.102.2"
#define SAVEGAME_VERSION (SAVEGAME_PREFIX SAVEGAME_VER_NR)

#define RES_VERSION_NUMBER  0, 102, 2, 1

#endif

The displayed version number is 102.3 - the savegame number is 0.102.2 and the RES version number is 0.102.2.1. Should the latter two not be 0.102.3 and 0.102.3.0 respectively?
Download Simutrans-Extended.

Want to help with development? See here for things to do for coding, and here for information on how to make graphics/objects.

Follow Simutrans-Extended on Facebook.
 

Re: Anomalies with version.h

Reply #1 –
The res version number was forgotten. And it will be most likely a 103 when finished.

ANd savegame number are only stepped, when we are sure, that the savegame is finished. Otherwise, because of the nightly system, many people will have broken savegames.