FS#6474 - New game start date set to date of loaded scenario
Attached to Project:
OpenTTD
Opened by Ricardo (Samu) - Wednesday, 01 June 2016, 22:49 GMT
Last edited by andythenorth (andythenorth) - Sunday, 20 August 2017, 19:43 GMT
Opened by Ricardo (Samu) - Wednesday, 01 June 2016, 22:49 GMT
Last edited by andythenorth (andythenorth) - Sunday, 20 August 2017, 19:43 GMT
|
DetailsThe Start Date year from the last loaded scenario in Scenario Editor is copied over to the New Game Start Date window.
Steps: 1) Check what's the current start Date when you click New Game from OpenTTD main menu. - Launch OpenTTD - Click New Game (don't start it) - See what's the value of Date in there and memorize it (let's say it's 1950) - Close the World Generation window 2) Launch Scenario Editor, and change the Date. - Click Scenario Editor - The start Date should still be the same (1950) when coming from Step 1 - Change the Date to some other value (like 1965), and memorize this value as well 3) Save the scenario, then abandon Scenario Editor to see if the Date is still the same as it was seen on Step 1. - Click Save Scenario and Click Save - Click Abandon scenario editor and click Yes - Click New Game (don't start it) - The value of Date in there is still the same as it was in Step 1 (1950) - Close the World Generation window The bug: 4) Load the saved scenario, then go back to main menu to see the Date becoming that of the loaded scenario. - Click Scenario Editor - The value of Date in there is still the same as it was in Step 1 (1950) - Click Load scenario - Select the saved scenario from step 3 and click Load - The value of Date is now that of the saved scenario in Step 2 (1965) - Click Abandon scenario editor and click Yes - Click New Game (don't start it)... ... BUG: the value of the Date is now that of the loaded scenario (1965) instead of that of Step 1 (1950) |
This task depends upon

So the bug is "new game start date set to date of loaded scenario". I wonder if more than just date is affected though.

Not same, but related concern: /task/6604