Transport Tycoon Forums

Let's imagine described below situation:

- I create account on Bananas for new NewGRF set,
- I upload version 1.0 of this set,
- Player #1 downloads this version of my set and creates saved game,
- I update the set on Bananas to version 1.1 which in NOT compatible with 1.0,
- Player #2 downloads newer version of my set,
- Player #1 sends saved game (requires the earlier version of the set) to Player #2
- Player #2 attempts to run saved game

What happens? Does OTTD look for older version of required set and automatically downloads it from Bananas? I know that Bananas stores all uploaded versions... If not, what does Player #2 should do to run saved game? Should I create the new account for newer wersion of set?
I need answers to make right decision about the future of one old set...

TadeuszD wrote:Let's imagine described below situation:

- I create account on Bananas for new NewGRF set,
- I upload version 1.0 of this set,
- Player #1 downloads this version of my set and creates saved game,
- I update the set on Bananas to version 1.1 which in NOT compatible with 1.0,
- Player #2 downloads newer version of my set,
- Player #1 sends saved game (requires the earlier version of the set) to Player #2
- Player #2 attempts to run saved game

Does OTTD look for older version of required set and automatically downloads it from Bananas?

That exactly happens when searching for missing NewGRFs in the savegame load dialogue. The NewGRF needed for a particular savegame is identified by the grfID and the md5sum. OpenTTD will ask bananas whether it has that particular version of the NewGRF as needed by the savegame available and send it.
Players who go to the normal NewGRF dialogue as accessible from the game's main menu will only see your newest uploaded version of the NewGRF

EDIT: IMHO it's not necessary to create a new account for newer versions. Unless you believe that they both serve independent gameplay choices so that a player starting a new map shall be able to choose one or the other from ingame content download. But in that case I'd consider them separate NewGRFs which might want to use different grfIDs as well.

in other words: yes.

planetmaker wrote:That exactly happens when searching for missing NewGRFs in the savegame load dialogue. The NewGRF needed for a particular savegame is identified by the grfID and the md5sum.

Thanks! So, the older version (but most matched) of NewGRF file is downloaded even if the GRF property "min_compatible_version" was not changed (only graphics was updated, for example)?

TadeuszD wrote:

planetmaker wrote:That exactly happens when searching for missing NewGRFs in the savegame load dialogue. The NewGRF needed for a particular savegame is identified by the grfID and the md5sum.

Thanks! So, the older version (but most matched) of NewGRF file is downloaded even if the GRF property "min_compatible_version" was not changed (only graphics was updated, for example)?

It will first go for the same version as the save game. If that is not possible, it tries to load a compatible one (that is already on the computer) with a warning that it is not the same version. If that is also not possible, it might try to load it without the missing NewGRF, but you have to set some settings on a different value for that to be possible.

TadeuszD wrote:

planetmaker wrote:That exactly happens when searching for missing NewGRFs in the savegame load dialogue. The NewGRF needed for a particular savegame is identified by the grfID and the md5sum.

Thanks! So, the older version (but most matched) of NewGRF file is downloaded even if the GRF property "min_compatible_version" was not changed (only graphics was updated, for example)?

If no *exact* match is found, no download is offered in the load savegame dialogue.

Thanks all for quick answers!
Now I understand the whole process of downloading NewGRFs, I hope.

btw:

the "minimal version" in the GRF is related to the openTTD version, not to the GRF version, is that correct ?

yes. it defines which openttd versions get it offered for downloading

Phreeze wrote:btw:

the "minimal version" in the GRF is related to the openTTD version, not to the GRF version, is that correct ?

Uh... which?

The one which you define inside the NewGRF's code itself (grf / action14 block), the minimal_compatible_version refers to the NewGRF itself (as defined by its version variable in the grf / action14 block)
The one in the bananas website, when you upload a NewGRF, that refers to the OpenTTD version.