OPENRCT2-CLI(6) | Games Manual | OPENRCT2-CLI(6) |
openrct2-cli
—
Headless server mode for OpenRCT2
openrct2-cli |
[-h | --help ]
[-v | --version ]
[--verbose ]
|
openrct2-cli |
host uri [--address
address] [--port
port] [--password
password]
|
OpenRCT2 supports a headless mode where the game will run as a console application with no UI. This is useful for running dedicated game servers.
Several objects are available in OpenRCT2's scripting interface that can be modified from its CLI:
• cheats Enable/disable various cheats
• climate Modify the climate and weather
• console Options for interacting with the stdout console
• context Core API for use by plugins
• date Getting or setting the in-game date
• map Manipulation of the map
• network Management of the server or interacting with clients
• park APIs for the park and its management
• scenario Information about the current scenario
• titleSequenceManager Create and edit title sequences (only available to clients that are not running in headless mode)
• ui APIs for controlling the user interface (only available to clients that are not running in headless mode)
For further information about OpenRCT2, its options and capabilities, please refer to the openrct2(6) manpage.
-h
|
--help
-v
|
--version
-n
|
--no-install
-a
|
--all
--about
openrct2-cli
.
--verbose
--port
port--address
address--password
password--user-data-path
path--openrct2-data-path
path--rct1-data-path
path--rct2-data-path
pathWith multiplayer, you might run into some bugs that do not occur in single player mode. If that happens, please report it on GitHub if the issue hasn't been reported already, and please say if the bug only occurs on multiplayer games.
In order for the server to successfully accept clients, the port must be open for the server's own firewall and any router's firewall the computer is behind. Additionally if the server is behind a router with NAT enabled, the router must be configured to have the port forwarded to the server's local address.
December 19, 2021 | Debian |