Skip to content

Change Wacky Worlds and Time Twister's scenario names to match their park names.#21214

Merged
Gymnasiast merged 1 commit into
OpenRCT2:developfrom
HtotheTML:ww_tt_scenario_names
May 18, 2024
Merged

Change Wacky Worlds and Time Twister's scenario names to match their park names.#21214
Gymnasiast merged 1 commit into
OpenRCT2:developfrom
HtotheTML:ww_tt_scenario_names

Conversation

@HtotheTML

Copy link
Copy Markdown
Contributor

The names for WW and TT's scenarios are quite lengthy and don't follow the usual naming conventions of the vanilla scenarios. In addition, some inaccuracies or inconveniences are created by their current names. Below are a few examples.

"Great Wall of China" would be more succinct than "Asia - Great Wall of China Tourism Enhancement."
The same is also true of "North America - Rollercoaster Heaven" vs. "Rollercoaster Heaven."

The primary structure displayed inside the park boundaries of "South America - Inca Lost City" is the Chichén Itzá, which is a Mayan structure in Mexico. This scenario is neither in South America nor Incan. Changing it to "Lost City Founder" would resolve this.

Hawaii is not located inside of North America. Changing "N. America - Extreme Hawaiian Island" to "Wacky Waikiki" fixes this.

"Future World" is already a scenario that exists in Added Attractions/Corkscrew Follies. Changing "Future - Future World" to "Gemini City" would resolve this confusion.

The scenario name "Rock 'n' Roll - Rock 'n' Roll" is a redundancy. Changing it to "Rock 'n' Roll Revival" clears this up.

wackyworlds1
wackyworlds2

timetwister1
timetwister2

The .SC6 scenario filenames would still retain their original names.

@AaronVanGeffen

AaronVanGeffen commented Jan 17, 2024

Copy link
Copy Markdown
Member

I think this is a marked improvement. However, I wonder if the old name should show up somewhere. I don't think we have any secondary fields to use for such purposes, though. (I know the filenames will still show the original name, but those are hidden unless debug tools are active.)

@karst

karst commented Jan 17, 2024

Copy link
Copy Markdown
Member

We could list them in the description. With the UCES scenarios I put "Author: ######" at the bottom of each description since there's no such field for scenarios.
I think we could perhaps say "Original Name: ###### - ##############"

@Gymnasiast

Copy link
Copy Markdown
Member

@karst Hard disagree, I’m afraid. That just takes away immersion in my opinion.

I think the game should look and feel like one piece, adding trivia like that takes that away.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

We could list them in the description. With the UCES scenarios I put "Author: ######" at the bottom of each description since there's no such field for scenarios. I think we could perhaps say "Original Name: ###### - ##############"

While that would be nice, it would also feel very much out of place being put there, sadly.

@MASHzj

MASHzj commented Jan 18, 2024

Copy link
Copy Markdown

Why should the park name always be the same as the scenario name? Vanilla base RCT2 already allows to give those a different name. So is that a problem? I'm against changing those if that's the only reason. I'm ok with it for specific parks if there is a better reason like the redundancy with rock and roll.
If the theme (continent or time era) will not be visible anymore, I would like to see it somewhere in the side. That theme also indicates which scenery theme and rides you will get. Because of that the argument of Inca Lost City and Extreme Hawaiian Island being in the wrong continent is a bit farfetched in my opinion. Especially for Hawaii: the islands may not be geographically in North America but it belongs to the USA which is in North America. And not everything in a game should be super realistic. The Antarctic theme for example has some objects that are actually arctic which is odd but also funny.

@HtotheTML

HtotheTML commented Jan 18, 2024

Copy link
Copy Markdown
Contributor Author

Why should the park name always be the same as the scenario name? Vanilla base RCT2 already allows to give those a different name. So is that a problem? I'm against changing those if that's the only reason. I'm ok with it for specific parks if there is a better reason like the redundancy with rock and roll. If the theme (continent or time era) will not be visible anymore, I would like to see it somewhere in the side. That theme also indicates which scenery theme and rides you will get. Because of that the argument of Inca Lost City and Extreme Hawaiian Island being in the wrong continent is a bit farfetched in my opinion. Especially for Hawaii: the islands may not be geographically in North America but it belongs to the USA which is in North America. And not everything in a game should be super realistic. The Antarctic theme for example has some objects that are actually arctic which is odd but also funny.

So something along the lines of keeping the categorization prefix, but changing the sub-header for each where it is needed?
ex: (Future - Gemini City)

Going into this PR I fully expected pushback, and am completely okay with this going either way. I don't think a change of this significance should proceed without a conversation first.

@karst

karst commented Jan 18, 2024

Copy link
Copy Markdown
Member

@karst Hard disagree, I’m afraid. That just takes away immersion in my opinion.

I think the game should look and feel like one piece, adding trivia like that takes that away.

What about Timeline for TT and Location for WW? Or that still be too much trivia?
IDM either way with or without.

Perhaps the names could resemble the old names without the timeline/location in the name with the exception of confusing ones like you mentioned before.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

The other option I could think of would be adding an overall toggle between scenario names and park names, but that would be a bigger thing to implement.

@karst

karst commented Jan 18, 2024

Copy link
Copy Markdown
Member

The other option I could think of would be adding an overall toggle between scenario names and park names, but that would be a bigger thing to implement.

Nah, I don't think we should give that option. It's unnecessary.

@karst

karst commented Jan 18, 2024

Copy link
Copy Markdown
Member

What about this:

<Africa - African Diamond Mine>
STR_SCNR    :African Diamond Mine
STR_PARK    :Mines of Africa
STR_DTLS    :Location: Africa{NEWLINE}You inherited a disused diamond mine, and find a valuable diamond.  You decide to invest that money to build a world-famous theme park.
<Dark Age - Castle>
STR_SCNR    :Castle
STR_PARK    :Cliffside Castle
STR_DTLS    :Timeline: Dark Age{NEWLINE}Local members of the battle re-enactment society are rather serious about their hobby. They’ve entrusted you with the job of constructing a Dark Age theme park on the grounds of Cliffside Castle.

It almost makes them sound like missions, which I think adds to the immersion.

@Gymnasiast

Copy link
Copy Markdown
Member

I don’t think that would improve anything. Most themes are already evident from the title or description to begin with, and for the cases where they aren’t (like Beach Barbecue Blast), it’s a surprise to the player. Which is fine in my book - we don’t need to pre-chew everything.

I know you are big on adding trivia, but let’s just keep this simple ;-)

@karst

karst commented Jan 18, 2024

Copy link
Copy Markdown
Member

That's fine! Then I recommend just keeping the old names without their location/timeline, with the exception of confusing names.

@ZehMatt

ZehMatt commented Jan 18, 2024

Copy link
Copy Markdown
Contributor

I'm against changing the names, there are probably a lot of things that reference it by their current name and changing that will cause just confusion.

@MASHzj

MASHzj commented Jan 18, 2024

Copy link
Copy Markdown

That's fine! Then I recommend just keeping the old names without their location/timeline, with the exception of confusing names.

I agree with keeping most of the scenario names. I would be sad to see those thrown away. Although I would like the themes somewhere in the side if those would be removed from the scenario name. I would like to have an easy overview, even as a quite experienced player that knows the scenarios.

@HtotheTML

HtotheTML commented Jan 19, 2024

Copy link
Copy Markdown
Contributor Author

Another idea would be to drop the title descriptors, but keep most of the original names, with the exception of ones like Future World (Gemini City) and Rock 'n' Roll (Rock 'n' Roll Revival).

@Gymnasiast

Copy link
Copy Markdown
Member

Maybe we should just put up a poll on Reddit for a week, then. I really like this change and I think most people would like it once they get used to it. (That is, if they care for the WW/TT scenarios in the first place.)

@MASHzj

MASHzj commented Jan 25, 2024

Copy link
Copy Markdown

Maybe, but if this proposal would be voted for, I still question how this change is made, when I look to the changed files: it makes all scenario name strings the same as the park name strings, resulting in redundant strings. So I wonder if it would be better then to keep the current names internally but use the park name strings in the overview. That would have 2 advantages:

  • reduced chance of ZehMatt's concern about breaking references
  • The current/old name could be shown somewhere in the side (what I would REALLY like if this change will pass) without needing extra fields or strings.

@HtotheTML

HtotheTML commented Jan 26, 2024

Copy link
Copy Markdown
Contributor Author

Maybe we should just put up a poll on Reddit for a week, then. I really like this change and I think most people would like it once they get used to it. (That is, if they care for the WW/TT scenarios in the first place.)

So something along the lines of showing the options in full, and asking which ones everyone prefers?

Keep Original
old

Drop Categorization, keep scenario names
dropcategory

Drop Categorization, use park names
parkname

Drop Categorization, use a mix of park and scenario names (this example prioritizes needed location names & catchier titles)
hybrid

@karst

karst commented Jan 26, 2024

Copy link
Copy Markdown
Member

I personally prefer the hybrid

@HtotheTML

HtotheTML commented Jan 26, 2024

Copy link
Copy Markdown
Contributor Author

A suggestion was brought up in the discord to synchronize the park names and scenario names in all cases, even for the hybrid choice, as significant differences there become an obstacle for finding your save file, like looking for a file named "Over The Edge" for the scenario titled "Victoria Falls".

@HtotheTML

Copy link
Copy Markdown
Contributor Author

Maybe we should just put up a poll on Reddit for a week, then. I really like this change and I think most people would like it once they get used to it. (That is, if they care for the WW/TT scenarios in the first place.)

here's that poll in proper: https://docs.google.com/forms/d/e/1FAIpQLSdL3LIeomzNDP3gbEJyJDDul1MgAnOxeP59zqXxtlOtCMOwyQ/viewform

It's been posted on reddit, the openrct2 forums, rctgo, and a couple different discord servers.
I'll check back on it in about a week.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

We're roughly a week out since i began the poll (I shared it here 2 days after I initially opened it), and votes have slowed down significantly.

Here's what we've got.

image

@HtotheTML

Copy link
Copy Markdown
Contributor Author

Seems like the majority are for changing it.

Only thing I'm concerned about is Victoria Falls and Inca Lost City, as their park names don't quite work as scenario names?

But otherwise it seems like we're good to go.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

Part of me thinks this change shouldn't be pushed through until the list for the scenario order is finalized, so it's one simultaneous big change to the list, rather than having to deal with it twice.

@ZehMatt

ZehMatt commented Feb 3, 2024

Copy link
Copy Markdown
Contributor

I still don't think that changing the scenario names is a good idea. People are used to what it is and guidelines will have the name that it currently is, so why change it?

@HtotheTML

Copy link
Copy Markdown
Contributor Author

By guidelines, are you meaning what the scenario names are referred to as in various other parts of the code & documents?

@MASHzj

MASHzj commented Feb 3, 2024

Copy link
Copy Markdown

By guidelines, are you meaning what the scenario names are referred to as in various other parts of the code & documents?

There is for example also the RCT wiki, which will still have to refer to the original names for people who play vanilla. So I still think it's a bad idea to just throw away those official names, and I would rather do a change like I posted in my previous comment here.

@Gymnasiast

Copy link
Copy Markdown
Member

I still don't think that changing the scenario names is a good idea. People are used to what it is and guidelines will have the name that it currently is, so why change it?

Because the majority is clearly in favour of it. That was the whole purpose of that poll. As for existing documentation: pretty much the only place where this would be a thing is the RCT Wiki, and the problem is solved by adding a few redirects (and adding those is a good idea anyway, even without this change). Since I’m a bureaucrat for that Wiki, I think I can safely say that adding a few redirects is really no problem at all.

@ZehMatt

ZehMatt commented Feb 4, 2024

Copy link
Copy Markdown
Contributor

I still don't think that changing the scenario names is a good idea. People are used to what it is and guidelines will have the name that it currently is, so why change it?

Because the majority is clearly in favour of it. That was the whole purpose of that poll. As for existing documentation: pretty much the only place where this would be a thing is the RCT Wiki, and the problem is solved by adding a few redirects (and adding those is a good idea anyway, even without this change). Since I’m a bureaucrat for that Wiki, I think I can safely say that adding a few redirects is really no problem at all.

I'm still against it, there are also hard prints that have those names in it, there are plenty other sources such as this https://www.ign.com/wikis/rollercoaster-tycoon/Scenarios, it will just create confusion and I still see no real justification other than "people want it" which isn't a good justification, we are not exactly in a position to rename content created by someone else, that was the decision and we should stick to it.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

You make a good point there; I don't know what the whole legal stance on modifying the names is.
I want to say at minimum Future - Future World should be adjusted to clear up confusion between two scenarios sharing the same name, but ultimately this decision is in your hands; all I can do is provide polling data.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

I wonder if it would be at all possible to do a couple minor changes such as tacking on "Revival" to Rock 'n' Roll - Rock 'n' Roll, and adding "Cliffside" to Dark Age - Castle.

Next benchmark of change would be changing Future - Future World to Future - Gemini City, and dropping "Tourism Enhancement" from Asia - Great Wall of China.

After that would be dropping the categorization.

If none of these benchmarks are possible or they're all too risky, then the only remaining option would be to close the PR.

@github-actions

Copy link
Copy Markdown

This pull request has been marked as stale and will be closed in 14 days if no action is taken. To keep it open, leave a comment or remove the stale-pr label. If you're awaiting feedback from a developer, please send us a reminder (either here or on Discord).

@HtotheTML

Copy link
Copy Markdown
Contributor Author

I'd like to keep this open, if only to reduce the changes to a small fix for confusing or inconsistent names.

@github-actions github-actions Bot removed the stale-pr label Mar 12, 2024
@Gymnasiast

Copy link
Copy Markdown
Member

I still want to merge it as-is, for the reasons I mentioned. I’ll make sure it gets properly discussed in the code review channel, rather than Matt and I duking it out here ;-)

@Gymnasiast Gymnasiast added the on hold A PR that should not be merged as is, waiting for a prerequisite. label Mar 14, 2024
@HtotheTML

Copy link
Copy Markdown
Contributor Author

That makes sense! The on deck PR for the scenario order change for WW also ended up having the same scenery theme appear multiple times in each difficulty category, so the whole arrangement of themes would also get a bit muddled if they were kept.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

I had an idea just now; since several of the park names use the naming schemes of scenarios, and several of the scenario names are simple descriptors for the parks, why not just swap them? I know that'd be antithetical to the original intention of this PR, but it'd be a way to satisfy keeping the old names and searchability while still allowing the scenario select screen to appear more cohesive.

@HtotheTML

Copy link
Copy Markdown
Contributor Author

That would look something like this on the scenario select screen:
swap

@MASHzj

MASHzj commented Mar 27, 2024

Copy link
Copy Markdown

I had an idea just now; since several of the park names use the naming schemes of scenarios, and several of the scenario names are simple descriptors for the parks, why not just swap them? I know that'd be antithetical to the original intention of this PR, but it'd be a way to satisfy keeping the old names and searchability while still allowing the scenario select screen to appear more cohesive.

Do you mean swapping all of them or only for those scenarios where that makes sense?

@HtotheTML

Copy link
Copy Markdown
Contributor Author

Just the ones where it makes sense.

@Gymnasiast

Copy link
Copy Markdown
Member

I think that waters it down completely. I am still in favour of the original set-up, i.e. using the park names in the scenario screen.

@github-actions

Copy link
Copy Markdown

This pull request has been marked as stale and will be closed in 14 days if no action is taken. To keep it open, leave a comment or remove the stale-pr label. If you're awaiting feedback from a developer, please send us a reminder (either here or on Discord).

@733737

733737 commented May 16, 2024

Copy link
Copy Markdown
Contributor

keep open

@AaronVanGeffen AaronVanGeffen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still want to merge it as-is, for the reasons I mentioned. I’ll make sure it gets properly discussed in the code review channel, rather than Matt and I duking it out here ;-)

For what it's worth, 👍 from me.

@Gymnasiast Gymnasiast force-pushed the ww_tt_scenario_names branch from 9bfd1a8 to 28fab08 Compare May 18, 2024 19:35
@Gymnasiast Gymnasiast merged commit c907d02 into OpenRCT2:develop May 18, 2024
@Gymnasiast Gymnasiast added this to the v0.4.12 milestone May 18, 2024
@Gymnasiast Gymnasiast removed the on hold A PR that should not be merged as is, waiting for a prerequisite. label May 18, 2024
Gymnasiast added a commit to OpenRCT2/Localisation that referenced this pull request May 18, 2024
janisozaur added a commit that referenced this pull request Jul 7, 2024
- Feature: [#622] Add option to align the top toolbar buttons horizontally centred (off by default).
- Feature: [#20263] Ability to increase the size of the map in the (0, 0) direction.
- Feature: [#21714] [Plugin] Costume assignment is now tailored to each staff type.
- Feature: [#21853] Enlarged UI mode.
- Feature: [#21893, #22065] On launch, the game now indicates what system is being initialised.
- Feature: [#21913] [Plugin] Allow precise and safe control of peep animations.
- Feature: [#22046] [Plugin] Add interface for crashed vehicle particle.
- Feature: [#22085] [Plugin] The result of actions that create banners now includes the bannerIndex.
- Feature: [#22087] [Plugin] Expose guests’ favourite rides to the plugin API.
- Feature: [#22090] [Plugin] Allow writing of paused state in non-networked settings.
- Feature: [#22140] Add option to automatically close dropdown menus if Enlarged UI is enabled.
- Feature: [#22150] [Plugin] Expose monthly expenditure history to the plugin API.
- Feature: [#22210] [Plugin] Peeps can now be made stationary or completely frozen.
- Feature: [#22210] [Plugin] The direction in which a peep is facing can now be manipulated.
- Improved: [#19870] Allow using new colours in UI themes.
- Improved: [#21774] The Alpine Coaster now supports using the alternative colour schemes.
- Improved: [#21853] Dropdowns now automatically use multiple columns if they are too tall for the screen.
- Improved: [#21981] Rendering performance of the map window has been improved considerably.
- Improved: [#21981] The map window now defaults to showing as much of the map as fits the screen.
- Improved: [#21983] Taking a screenshot now shows a message again, closing when taking another.
- Improved: [#22026] The options window now stays centred when window scaling is changed.
- Improved: [#22060] [Plugin] The scroll wheel can now be used to modify spinner widget values in custom/script windows.
- Improved: [#22065] Joining a network game now indicates progress using coaster trains.
- Improved: [#22075] [Plugin] Plugins can now use G1 Icons.
- Improved: [#22084] The game now temporarily pauses while the load/save window is open.
- Improved: [#22217] See-through items are ignored again in viewport/pointer interaction.
- Improved: [objects#238] Add preview image for invisible queue.
- Improved: [objects#329] Add RCT1AA lay-down coaster trains (for import only).
- Change: [#7248] Small mini-maps are now centred in the map window.
- Change: [#20240] Heavy snow and blizzards now make guests buy and use umbrellas.
- Change: [#21043] The new music styles are no longer added to old parks automatically.
- Change: [#21214] Wacky Worlds and Time Twister’s scenario names now match their park names.
- Change: [#21991] UI themes JSON now use colour names and a translucency bool, instead of a number (old themes still work).
- Change: [#22057] Reorder Time Twister’s scenarios and adjust their difficulty classification.
- Change: [#22173] Patrol path selection is visible over existing patrol paths.
- Change: [#22196] Make track navigation buttons holdable.
- Change: [#22227] [Plugin] Ride prices are now constrained for plugins as well.
- Fix: [#13234] Vehicle weight sometimes wrong after using Remove All Guests cheat.
- Fix: [#13294] Map corners are cut off in some directions (original bug).
- Fix: [#14630] Non-ASCII thousands and decimal separators not processed correctly.
- Fix: [#21496] Some RCT1 scenery is hidden after saving and reloading.
- Fix: [#21533] Support glitches on Hybrid Coaster.
- Fix: [#21974] No reason specified when attempting to place benches, lamps, or bins on path with no unconnected edges (original bug).
- Fix: [#21987] [Plugin] API cannot handle negative removal prices.
- Fix: [#22008] Uninverted Lay-down roller coaster uses the wrong support type.
- Fix: [#22012] [Plugin] Images on ImgButton widgets cannot be updated.
- Fix: [#22121] Some news items in the “Recent Messages” window have the wrong text colour.
- Fix: [#22152] [Plugin] Negative signed integers are truncated.
- Fix: [#22161] Using arrow keys in textboxes crashes the game.
- Fix: [#22174] Cheats are reset when starting a server.
- Fix: [#22185] Intensity and nausea are incorrectly sorted in the rides list after ratings invalidation.
- Fix: [#22226] Red traffic light shows incorrect sprite when pressed.
- Fix: [objects#323] Incorrect wall boundaries on large WW/TT scenery objects.
- Fix: [objects#331] Incorrect hover car capacity string.
- Fix: [objects#334] Incorrect school bus capacity string.
- Fix: [objects#337] Swan Boats use an incorrect third remap colour (original bug).
tupaschoal added a commit to tupaschoal/OpenRCT2 that referenced this pull request Aug 11, 2024
tupaschoal added a commit to tupaschoal/OpenRCT2 that referenced this pull request Aug 19, 2024
Sadret pushed a commit to Sadret/OpenRCT2 that referenced this pull request Sep 7, 2024
CorySanin added a commit to CorySanin/OpenRCT2 that referenced this pull request Feb 3, 2025
Release v0.4.12

- Feature: [OpenRCT2#622] Add option to align the top toolbar buttons horizontally centred (off by default).
- Feature: [OpenRCT2#20263] Ability to increase the size of the map in the (0, 0) direction.
- Feature: [OpenRCT2#21714] [Plugin] Costume assignment is now tailored to each staff type.
- Feature: [OpenRCT2#21853] Enlarged UI mode.
- Feature: [OpenRCT2#21893, OpenRCT2#22065] On launch, the game now indicates what system is being initialised.
- Feature: [OpenRCT2#21913] [Plugin] Allow precise and safe control of peep animations.
- Feature: [OpenRCT2#22046] [Plugin] Add interface for crashed vehicle particle.
- Feature: [OpenRCT2#22085] [Plugin] The result of actions that create banners now includes the bannerIndex.
- Feature: [OpenRCT2#22087] [Plugin] Expose guests’ favourite rides to the plugin API.
- Feature: [OpenRCT2#22090] [Plugin] Allow writing of paused state in non-networked settings.
- Feature: [OpenRCT2#22140] Add option to automatically close dropdown menus if Enlarged UI is enabled.
- Feature: [OpenRCT2#22150] [Plugin] Expose monthly expenditure history to the plugin API.
- Feature: [OpenRCT2#22210] [Plugin] Peeps can now be made stationary or completely frozen.
- Feature: [OpenRCT2#22210] [Plugin] The direction in which a peep is facing can now be manipulated.
- Improved: [OpenRCT2#19870] Allow using new colours in UI themes.
- Improved: [OpenRCT2#21774] The Alpine Coaster now supports using the alternative colour schemes.
- Improved: [OpenRCT2#21853] Dropdowns now automatically use multiple columns if they are too tall for the screen.
- Improved: [OpenRCT2#21981] Rendering performance of the map window has been improved considerably.
- Improved: [OpenRCT2#21981] The map window now defaults to showing as much of the map as fits the screen.
- Improved: [OpenRCT2#21983] Taking a screenshot now shows a message again, closing when taking another.
- Improved: [OpenRCT2#22026] The options window now stays centred when window scaling is changed.
- Improved: [OpenRCT2#22060] [Plugin] The scroll wheel can now be used to modify spinner widget values in custom/script windows.
- Improved: [OpenRCT2#22065] Joining a network game now indicates progress using coaster trains.
- Improved: [OpenRCT2#22075] [Plugin] Plugins can now use G1 Icons.
- Improved: [OpenRCT2#22084] The game now temporarily pauses while the load/save window is open.
- Improved: [OpenRCT2#22217] See-through items are ignored again in viewport/pointer interaction.
- Improved: [objects#238] Add preview image for invisible queue.
- Improved: [objects#329] Add RCT1AA lay-down coaster trains (for import only).
- Change: [OpenRCT2#7248] Small mini-maps are now centred in the map window.
- Change: [OpenRCT2#20240] Heavy snow and blizzards now make guests buy and use umbrellas.
- Change: [OpenRCT2#21043] The new music styles are no longer added to old parks automatically.
- Change: [OpenRCT2#21214] Wacky Worlds and Time Twister’s scenario names now match their park names.
- Change: [OpenRCT2#21991] UI themes JSON now use colour names and a translucency bool, instead of a number (old themes still work).
- Change: [OpenRCT2#22057] Reorder Time Twister’s scenarios and adjust their difficulty classification.
- Change: [OpenRCT2#22173] Patrol path selection is visible over existing patrol paths.
- Change: [OpenRCT2#22196] Make track navigation buttons holdable.
- Change: [OpenRCT2#22227] [Plugin] Ride prices are now constrained for plugins as well.
- Fix: [OpenRCT2#13234] Vehicle weight sometimes wrong after using Remove All Guests cheat.
- Fix: [OpenRCT2#13294] Map corners are cut off in some directions (original bug).
- Fix: [OpenRCT2#14630] Non-ASCII thousands and decimal separators not processed correctly.
- Fix: [OpenRCT2#21496] Some RCT1 scenery is hidden after saving and reloading.
- Fix: [OpenRCT2#21533] Support glitches on Hybrid Coaster.
- Fix: [OpenRCT2#21974] No reason specified when attempting to place benches, lamps, or bins on path with no unconnected edges (original bug).
- Fix: [OpenRCT2#21987] [Plugin] API cannot handle negative removal prices.
- Fix: [OpenRCT2#22008] Uninverted Lay-down roller coaster uses the wrong support type.
- Fix: [OpenRCT2#22012] [Plugin] Images on ImgButton widgets cannot be updated.
- Fix: [OpenRCT2#22121] Some news items in the “Recent Messages” window have the wrong text colour.
- Fix: [OpenRCT2#22152] [Plugin] Negative signed integers are truncated.
- Fix: [OpenRCT2#22161] Using arrow keys in textboxes crashes the game.
- Fix: [OpenRCT2#22174] Cheats are reset when starting a server.
- Fix: [OpenRCT2#22185] Intensity and nausea are incorrectly sorted in the rides list after ratings invalidation.
- Fix: [OpenRCT2#22226] Red traffic light shows incorrect sprite when pressed.
- Fix: [objects#323] Incorrect wall boundaries on large WW/TT scenery objects.
- Fix: [objects#331] Incorrect hover car capacity string.
- Fix: [objects#334] Incorrect school bus capacity string.
- Fix: [objects#337] Swan Boats use an incorrect third remap colour (original bug).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants