Skip to content

Certain scenarios start on the 2nd of January instead of the 1st #3547

@LeeSpork

Description

@LeeSpork

Version information:

  • Platform: Windows 10
  • Version: 25.11

Describe the bug
Certain scenarios appear to start one day later than the expected start date compared to vanilla.

In OpenLoco v25.11 using assets from Steam installation of the original game, 4 out of the first 11 of the vanilla scenarios have this issue:

Scenario name Day of January on start
Boulder's Breakers 1st
Sandbox Settler 2nd
Weatherworld 1st
Desert Delirium 1st
Great Britian & Ireland 1900 2nd
North America (East) 1900 2nd
North America (Midwest) 1920 2nd
North America (West) 1910 1st
Oil Oasis 1st
Smiley Isley 1st
Swiss Alps 1905 1st

This also affects custom scenarios, e.g. this one which I made in vanilla's scenario editor: Voidton.zip (not sure if all custom scenarios or just some of them.)

All of these scenarios start on the 1st of January in original Locomotion (according to the tooltip when hovering over the time toolbar).

To Reproduce

  1. Click Start New Game, and select one of the affected scenarios.
  2. Read the date displayed on bottom-right of the screen.

Expected behaviour
It should display Jan 1st for the first day period after starting the scenario, as per vanilla.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions