eggs/game_eggs/tycoon_games/openrct2

OpenRCT2

Note: OpenRCT2 only recently (Jan. 2022) updated to support non-interactive Docker environments, and development is ongoing to improve it. Please understand future updates may be unstable, or this Egg may update in the future to accommodate changes.

---

Authors / Contributors

Red-Thirten 💻 🔨

parkervcp 💻 💡

janisozaur 💻 💡

---

Game Description

From OpenRCT2's Website:

OpenRCT2 is an open-source re-implementation of RollerCoaster Tycoon 2 (RCT2), expanding the game with new features, fixing bugs and raising game limits. The gameplay revolves around building and maintaining an amusement park containing attractions, shops and facilities. The player must try to make a profit and maintain a good park reputation whilst keeping the guests happy. OpenRCT2 allows for both scenario and sandbox play. Scenarios require the player to complete a certain objective in a set time limit whilst sandbox allows the player to build a more flexible park with optionally no restrictions or finance.

---

Server Ports

Port	Default (TCP)
Game	11753

---

Installation/System Requirements

	Minimum
Processor	Recent x86/64 (AMD/Intel) processor. No ARM support.
RAM	256-512 MiB (depends on # of clients & park size)
Storage	80 MB
RCT2 Files	Not required

---

Save Files

Save files and autosaves are located in this directory:

/home/container/ServerData/save/

If the "Load Latest Autosave" startup variable is enabled, and the autosave/ directory exists, the server will load the latest autosave instead of the specified Save File.

---

Console Commands

As of OpenRCT2 v0.3.5.1, entering commands via Pterodactyl do nothing. Hopefully this will be resolved in a future OpenRCT2 update.

---

Becoming an Admin on the Server

Unfortunately, because console commands currently do not register, becoming the first admin on the server takes some steps, listed below:

1. Ensure the "Log Server Actions" startup variable is set to "true".
2. Start the server and join it with the client you want to make an admin.
3. Open ServerData/serverlogs/<Server Name>/<Latest Date>.txt and copy the SHA1 hash next to your client's username (note the username as well).
4. Then, open ServerData/users.json. Paste the hash into the "hash" value, and change the "name" value to your client's username.
5. Reboot the server, re-join it, and you should be an admin!

After becoming an admin, you can use the in-game users management window to add additional admins (or groups) more easily if you wish.

---

Known Issues

The following are known issues that are unique to running OpenRCT2 on Pterodactyl, but likely can only be fixed by further development/updates from OpenRCT2.

• Only building from source from the develop branch currently yields a package that is bootable. This will no longer be true for any OpenRCT2 releases after v.0.3.5.1.
  • This also means that clients joining the server must be on the latest develop branch as well.
• Configuring a password on the server disallows non-admin clients from entering in a password in their client to connect; it just disconnects them. Admin clients can still join normally.
• You may rarely run into the server crashing on start due to a "Floating point exception(core dumped)" error. If this occurs to you, please help with OpenRCT2 development by doing the following:
  1. Add the following to the beginning of your server's startup command: SEGFAULT_SIGNALS=fpe LD_PRELOAD=/lib/x86_64-linux-gnu/libSegFault.so
  2. Start the server. If it boots normally, nothing extra will print. If it crashes, it will print a stack trace to the console.
  3. If a crash occurs, copy the entire stack trace, and save it to a log sharing website (like Hastebin).
  4. Open a new Bug Report Issue with OpenRCT2 and share your logs with them.