OpenRCT2 / OpenRCT2/OpenRCT2

Mechanic will inspect lift/boat hire even though it cannot break down

Open
#18,121 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Operating System

Windows 11 64 bit

OpenRCT2 build

OpenRCT2, v0.4.1-361-ga8073f6 (a8073f6 on develop) provided by GitHub

Describe the issue

In original rct2 and openrct2 mechanic does ignore the ride that cannot break down like crooked house.

However, they still inspect lift and boat hire (rowing boats, swans, and canoes boat hire cannot break).

Screenshot (1)
In original rct2

Screenshot 2022-09-28 000411
In openrct2

I suspect that because lift and boat hire have breakdown type, the mechanic will inspect them, but they do not check if the ride can actually break.

Area(s) with issue?

The bug also exists in RCT2 (vanilla)

Steps to reproduce
  1. has a park with enough mechanic to inspect all ride and unbreakable ride with lift and boat hire (rowing boats, swans, and canoes)
  2. Run the park for very long time
  3. check the ride that cannot break (Marcel has video for them)
  4. All unbreakable ride will have very high time since last inspection, except lift and boat hire which has time within inspection range.
Attachments

My park use in testing
Testbreak.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 tracing the mechanic inspection behavior described in the issue, focusing on lifts and boat hire for rowing boats, swans, and canoes. Reproduce the report with Testbreak.zip and compare the inspection timing with other rides that cannot break down; done means these rides are no longer inspected unnecessarily.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.