openrct2plugins.org

What is OpenRCT2 Plug-ins Directory?

OpenRCT2 Plug-ins Directory is a community-run catalog of add-ons for OpenRCT2, the open-source reimplementation of RollerCoaster Tycoon 2. Rather than hosting the plug-ins itself, it indexes them and links out to their project pages. Listings show the plug-in name, a short description, the author, a star count and the last-updated date, plus a license tag such as MIT or GNU GPLv3.

The page surfaces two browsable views:

• Newest plug-ins — recent arrivals like a litter-property editor, a fireworks-show tool, a guest-tracking inspector and a shop-info viewer.
• Most starred plug-ins — the most popular entries, including ride-price management, scenery copy-and-paste, park-rating breakdown and path-furniture automation.

Who it suits

• Players who want to change how the game behaves — automating prices, inspecting guest behaviour, editing vehicles mid-ride — without writing code.
• Plugin authors looking for prior art, conventions and license examples before publishing their own work.
• Returning players who want to see what the scene has produced recently, not just the long-standing favourites.

How to use it

Treat the star count as a rough popularity signal, not a quality guarantee, and check the last-updated date before installing: an older plug-in may still work, but it has had less recent attention. The license tag matters if you plan to modify or redistribute anything. If you want a concrete starting point, search the most-starred list for the specific annoyance you have — ride pricing, path clutter, park rating — and read that plug-in's own project page for install steps and compatibility notes.

How do I install a plug-in from this directory into OpenRCT2?

The directory itself is a catalog, not an installer: you browse it to find a plug-in, then follow that plug-in's own repository or release page to download it. OpenRCT2 loads plug-ins from a local folder on your computer, so installation means placing the plug-in files in the right folder and restarting the game.

The general flow

1. Open the plug-in's entry in the directory and follow the link to its source or release page.
2. Download the plug-in as a .js file, or as a .zip/archive if the author packages it that way.
3. If you downloaded an archive, extract it. The file OpenRCT2 actually loads is the JavaScript file, usually named something like plugin.js or matching the plug-in name.
4. Copy that file into the OpenRCT2 plug-in folder:
   • Windows: Documents\OpenRCT2\plugin
   • macOS: Library/Application Support/OpenRCT2/plugin
   • Linux: ~/.config/OpenRCT2/plugin If the plugin folder doesn't exist, create it.
5. Start (or restart) OpenRCT2. Plug-ins are read at launch, so a running game won't see a newly added file.
6. Check the in-game plug-in list or the relevant menu item to confirm the plug-in loaded and to enable or configure it.

A single plug-in may ship as one file or as a folder containing a plugin.js plus supporting files. If the download contains a folder, keep that folder intact inside the plugin directory rather than pulling one file out of it.

Choosing what to install

The directory's two lists serve different purposes, and that difference matters more than any single entry.

For a first install, a heavily starred, narrowly scoped plug-in is the safer test case — it's easier to tell whether it worked. Examples from the directory include price management, scenery copy-and-paste, park rating breakdowns, and vehicle editing, each of which does one visible thing you can verify in-game.

Practical checks before you commit

• Compatibility: OpenRCT2 plug-ins depend on the game's plug-in API, which changes over time. A plug-in last updated several years ago may still work, but treat that as something to test rather than assume.
• Version match: Install the release that matches your OpenRCT2 version if the author publishes separate builds.
• License: Entries list licenses such as MIT or GNU GPLv3. This mostly matters if you plan to modify or redistribute the code.
• Conflicts: Two plug-ins that both manage ride prices or both alter footpaths can fight each other. Install one at a time and confirm behavior before adding the next.

If it doesn't appear

Recheck the folder path first — a plugin folder inside the OpenRCT2 install directory instead of your user documents folder is the most common mistake. Then confirm the file extension is .js and not a renamed archive, and that you fully restarted the game. If it still fails, the plug-in's own repository issue tracker is the place to look, since the directory only catalogs entries and doesn't host support.

As a starting point, browse OpenRCT2 Plug-ins Directory to pick a plug-in, then work through the steps above with a single well-starred entry before adding more.

Which plug-ins are most popular or highly rated by the community?

The directory's own "Most starred plug-ins" list is the clearest popularity signal here: these are the plug-ins that other OpenRCT2 players have starred most often on their project pages. Star counts reflect long-term visibility and usefulness rather than any formal rating.

Most-starred plug-ins on the page

Two patterns stand out. First, price management is the single most popular category, with two separate plug-ins in the top three — useful if you run large parks and dislike adjusting every ride manually. Second, the rest are "inspection and convenience" tools: they either explain a hidden number (park rating) or remove repetitive building work (scenery, benches and bins). That is a good indicator of what the community actually values day to day.

Newer plug-ins worth watching

The "Newest plug-ins" list is a different signal — recency, not endorsement. Standouts include Guest-Inspector, which follows individual guests so you can see why they behave as they do, and OpenRCT2-FireworksPlugin for building and viewing fireworks shows. These have far fewer stars simply because they are new.

A practical decision rule: if you want a proven, widely used tool, start with the most-starred list, since a long track record usually means fewer rough edges. If you want a specific capability the older tools don't cover — guest-level tracking, for instance — browse the newest list instead and accept that you may be an early tester.

Next step: pick one problem you keep solving by hand, such as pricing or path furniture, and install just that plug-in first. Browse the full directory at OpenRCT2 Plug-ins Directory.

What plug-in can automatically manage ride prices and shop prices in my park?

For automatic pricing across both rides and shops, the closest match is openrct2-price-manager by Sadret, listed among the most-starred plug-ins in the OpenRCT2 Plug-ins Directory. Its description states that it manages and automatically updates prices for park entry, rides and shops — the only entry in the directory's evidence that covers all three at once.

A narrower alternative is openrct2-ride-price-manager by mgovea, the directory's most-starred plug-in. It handles ride prices only, so shops and entry fees stay manual.

Both are written in TypeScript and licensed under GNU GPLv3, so either can be inspected or modified if the automatic behaviour doesn't suit your playstyle.

Deciding between them

If your goal is to stop micro-managing every stall and entrance fee, the broader price manager saves the most clicking. If you enjoy tuning shop prices yourself — for example, keeping balloon stalls cheap for guest happiness while squeezing more from food — the ride-only plug-in leaves that part of the game untouched.

A practical next step: install one, run a busy park for a few in-game months, and watch whether guest happiness and park rating hold steady. Automatic pricing can drift away from what your specific guest mix will pay, so treat the first season as a test rather than a permanent setting.

What plug-in helps me understand and improve my park rating?

The plug-in built for that job is OpenRCT2-ParkRatingInspector, listed in the Most starred plug-ins section of the OpenRCT2 Plug-ins Directory. Its description says it helps you break down your park rating, so instead of watching the number rise and fall and guessing why, you get a component-by-component view of what is helping or hurting you.

How to use it in practice

Say your park rating is stuck around 600 and guests are drifting away. Open the inspector, check which factors are weak, then act:

• Low ride variety or excitement — build or retheme a ride, or fix a stale one.
• Bad path layout or litter — clean up and reconnect paths; litterEditor, also in the directory, lets you modify litter properties.
• Guests unhappy or lost — Guest-Inspector follows individual guests so you can see where their behaviour goes wrong.
• Prices too high — openrct2-ride-price-manager and openrct2-price-manager automate ride, shop and entry pricing.

Choosing between the rating tools

Start with ParkRatingInspector to find the weak factor, then reach for a specialist plug-in only for that factor. If the breakdown points at litter or guest behaviour rather than rides or prices, the guest and litter tools above are the more targeted fix.

How can I edit vehicles on rides or copy and paste scenery using plug-ins?

For vehicle editing, use OpenRCT2-RideVehicleEditor; for scenery duplication, use openrct2-scenery-manager. Both are listed in the OpenRCT2 Plug-ins Directory, which sorts plug-ins by recency and by star count, so you can judge how actively each one is used.

Editing vehicles on rides

OpenRCT2-RideVehicleEditor is described as letting you edit vehicles on any ride in your park on the fly. In practice, that suits a player who wants to change how an existing coaster or flat ride looks and behaves without demolishing and rebuilding it — for example, swapping the vehicle type on a tracked ride, or adjusting a train you have already placed. It appears in the most-starred list, which suggests it has been widely adopted by the community.

Copying and pasting scenery

openrct2-scenery-manager is described as a plug-in to copy and paste scenery with many more features. This is the one to reach for when you have built a detailed area — a plaza, a themed queue line, a garden — and want to repeat it elsewhere without placing every piece again. It also appears among the most-starred plug-ins.

Choosing between them

These solve different problems, so many players install both. Neither is a general-purpose editor; each targets one part of the park.

A practical next step

Open the directory and use its two lists for different purposes. The "Most starred plug-ins" list is the better starting point for established, widely used tools like these, while "Newest plug-ins" is where you look when you want something recent — for instance OpenRCT2-FireworksPlugin or Guest-Inspector, both of which appear there. Before installing, check the licence shown next to each entry (the scenery manager is GNU GPLv3, for example) and the last-updated date, since a plug-in that has not been touched in years may lag behind current OpenRCT2 builds.