Rubidium wrote:

How do you load a scenario on a dedicated server? As far as I am aware that's not quite possible.

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6037

muxy wrote:

like this : openttd -D -g scenario_path

But it seems to be BAD.

if it's better to start a scenario as normal game, then perform a save game, then use the savegame in the dedicated server, i will do it this way and check.

Edit 18:38 (GMT+1 DST)
Well, it's the same when using a savegame from the scenario started on local game. The server settings comes from the openttd.cfg file. Strange behavoir for starting_year who is set to 1970. Starting_year in the savegame/scenario has been set to 1955 and also in the server openttd.cfg and the server setting returns 1970. Can be seen server state at http://www.openttd.org/en/server/150

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6038

Rubidium wrote:

I've just tried to reproduce it. However,
a) starting a scenario works and uses the settings from the scenario; if I change the starting year in the config file the scenario still starts at the old year, starting a new game starts at the new starting year.
b) all (advanced) settings I've changed in the scenario are still like in the scenario; if I change the config file those settings do not change, except the settings that are not stored in the savegame, but those settings do not influence the game only visual things.
c) I wasn't able to reproduce it or you are expecting things to be stored in the scenario that aren't stored in the scenario file (like the server name or the port to listen on).

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6075

muxy wrote:

Ok, then

a) create a scenario 64x64 with some towns and industries
b) start this scenario on dedicated server with map_x, map_y set to 11
c) from console ask for setting map_x and map_y, it returns 11 for both : value from openttd.cfg

I failed to reproduce with this procedure the problem with starting_year, i got it from another scenario, i will investigate.

This "bug" could be converted in an functionnal request : improve the way settings are functionning :

each setting should have 2 values : the ingame value, and a "next" value. if next value is not set, it will return ingame value.
when requesting setting value, it will return both value : ingame and next.
The next value will be used on the next game restart (automatic or newgame console)

when using saveconfig command without parameter will save ingame value, and with a particular parameter will save next value.

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6076

muxy wrote:

With this attached scenario, you can check the problem with starting_year.

The starting_year is set in the scenario in 1955.

When you start this scenario in a dedicated server, the year count displays -15 in the server list window.

In that case, if you request the starting_year setting it returns 1970.

Attachments

• SouthWestFrancev0.9c.scn (198.21 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6077

Rubidium wrote:

map_x/map_y aren't saved as settings in the savegame; those settings are never needed anymore. As such they get some stub values loaded. It's at least not wrong.

About the starting year thingy; looks like it doesn't update the starting year setting in the scenario, but only the 'current' year. It doesn't get the starting year from openttd.cfg.

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6078

Rubidium wrote:

The scenario starting year bug cause has been fixed. You have to (re)set the starting year of the given scenario in the scenario editor via the toolbar.

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885#comment6079

Yexo closed the ticket.

Reason for closing: Implemented

In r18943

This comment was imported from FlySpray: https://bugs.openttd.org/task/2885