1
0
mirror of https://github.com/OpenRCT2/OpenRCT2 synced 2026-01-06 06:32:56 +01:00

Updated Increasing of game limits (markdown)

Michael Steenbeek
2020-05-20 10:22:15 +02:00
parent d38d6e1c60
commit 8f35150e7a

@@ -1,12 +1,10 @@
# Can OpenRCT2 increase the number of ...
Not yet... OpenRCT2 is committed to maintaining compatibility with vanilla game at least until all of existing features get implemented.
The technical restrictions exist because:
Not yet. OpenRCT2 currently still uses the SV6 format that RCT2 used, which is quite a rigid format. While it has the advantage of being able to export games to vanilla RCT2, it also comes with technical restrictions:
* Some of the game structures only allow usually one or two bytes for indexing.
* The space allocated for these structures is fixed in the original game memory.
* Saved games and scenarios would no longer be compatible with rct2.
* The space allocated for these structures is fixed in the original game memory, so we can't just raise it.
* Changing structures would lead to saved games and scenarios would no longer be compatible with RCT2.
When all of the features we can implement without breaking compatibility with vanilla game and we move on to our own format, these limits will be raised.
As such, we need a wholly new save format. As part of that, we plan to massively increase limits and also allow for a more flexible format in general.
# Limits
* 128 ride types
@@ -16,7 +14,7 @@ When all of the features we can implement without breaking compatibility with va
* 32 banner types
* 16 path types
* 15 path accessory types
* 19 scenery sets
* 19 scenery groups
* 1 park entrance type
* 255 rides
* 200 staff members