OpenRCT2 / OpenRCT2/OpenRCT2

Starting `openrct2 --headless` without any other arguments initializes a glitched empty park

Open
#25,904 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
16.2k
Forks
1.9k
Avg merge
1d 20h
Merged PRs (30d)
80

Description

Operating System

Windows 10, 64-bit

OpenRCT2 build

OpenRCT2, v0.4.30 (9099047a5b on develop) provided by GitHub

Base game

RollerCoaster Tycoon 2

Area(s) with this issue?

No response

Describe the issue

Starting a headless instance without passing any other arguments, then running a console command inside the headless instance to save the park, saves a glitched park without any objects selected which will crash the game when opening the park information window, opening the guest information window, or hiring any staff.

Steps to reproduce
  1. Start OpenRCT2 with openrct2 --headless without passing any other arguments.
  2. Save the park and exit by running this command: console.executeLegacy("save_park 25904_test"); console.executeLegacy("exit")
  3. Open OpenRCT2 again normally.
  4. Find 25904_test.park and load it.
Attachments

The glitched empty park in question: 25904_test.zip

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with openrct2 --headless, the provided console.executeLegacy save-and-exit command, and the attached 25904_test.park. Inspect the headless startup and park-saving path to determine why no objects are selected; done means the saved park loads normally and the listed park, guest, and staff actions no longer crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.