Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

rct1.ride.spinning_cars

Open
#3,435 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
localization

Research direction

Start with the object translation files and compare the existing rct1.ride.spinning_cars entry across the checked locales. Translate the same name, description, and capacity strings for an unchecked locale, then mark that locale updated when its translation is complete.

Written by the indexing model from the issue text.

Description

new field

We just added this new train type to the object translation file.

    },
    "rct1.ride.spinning_cars": {
        "reference-name": "Spinning Cars",
        "name": "Spinning Cars",
        "reference-description": "Circular roller coaster cars which are free to spin around their central axis.",
        "description": "Circular roller coaster cars which are free to spin around their central axis.",
        "reference-capacity": "4 passengers per car",
        "capacity": "4 passengers per car"
    },

Updated in:

  • ar-EG
  • ca-ES
  • cs-CZ
  • da-DK
  • de-DE
  • en-US
  • eo-ZZ
  • es-ES
  • fi-FI
  • fr-FR
  • gl-ES
  • hu-HU
  • it-IT
  • ja-JP
  • ko-KR
  • nb-NO
  • nl-NL
  • pl-PL
  • pt-BR
  • ru-RU
  • sv-SE
  • tr-TR
  • uk-UA
  • vi-VN
  • zh-CN
  • zh-TW

Notification when new strings arrive:
@OmarAglan @J0anJosep @tygrysek90 @LPSGizmo @Wuzzy2 @tellovishous @dimateos @rmnvgr @ninjum @LucaRed @telk5093 @Gymnasiast @arekdurlik @Tupaschoal @andOlga @mrmagic2020 @daihakken

Dominant language
No language data
Stars
72
Forks
212
Avg merge
17h 44m
Merged PRs (30d)
21

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from OpenRCT2/Localisation

All issues in OpenRCT2/Localisation

Similar issues

More Localization issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.