Rust server console commandsĪs well as launch parameters, there are a number of options admins can configure either via the console or by adding them to your server.cfg file and rebooting the server. If you have the server installed as a service, this will mean it restarts automatically. To collect errors from any server crashes. Players usually just put a random number, but you can also put a discovered seed from the map gallery or reuse previous seeds to recreate them. +edĪ map seed defines the layout and terrain of a map. Default is 3000, which is really too small for large to a medium number of players.
The size of the map the server generates. You may want to set this lower to avoid progress loss when your server crashes, but setting it too low will impact performance. The number of seconds before the server saves. You’d be surprised how demanding a Rust server can be, especially on the network. The higher this number, the higher RAM, CPU power, and internet speed you’ll need. The number here largely depends on your hardware. The maximum number of players allowed on your server at once. You’ll probably want to but some basic details about your server here, including any mods. The name of your server, as seen by others. Set it much higher than thirty, and it could strain your server. Set this too low, and players will notice a disconnect between what happens on their screen, which it typically 60fps, and the server-side outcome.
#Blue fang solutions server startup time update
At a tick rate of 30 (which Facepunch recommends), the location of players and objects will update 30 times a second. This is frequency per second at which your server updates the state of the game. Same as above, but for the rust RCON console. You’ll have to port forward whichever number you pick. By default, this number is 28015 and there’s little reason to change it. This ensures that when an incoming connection hits that port on the router, it’ll be forwarded to the relevant computer. To accept connections from other PCs, your server has to bind the application to a port that it will use to listen for and accept connections. server.port 28015Īnother fairly self-explanatory one – it sets the network port Rust uses. +rcon.ip x.x.x.xĪgain, leave this as 0.0.0.0 unless you have multiple IPs. The only time you need to set it manually is if you have multiple IPs. This will let it automatically adjust to your current IP address. However, less obvious is the fact it should be set to 0.0.0.0 for most setups. As you’d expect, it changes the IP address your users will connect to.
+rcon.web1Įnables the WebSocket for the Rust console, which enables more advanced functionality and metrics. Otherwise, it will be trivial for someone to make unauthorized changes to your server.
#Blue fang solutions server startup time password
It’s very important that you change this to a new password that you haven’t used anywhere else. This changes the password to your Rust server console, which won’t be secure by default. This one is first because it’s the most important parameter you can change. Rust command line parameters explained +rcon.password “supersecretpassword” If the file doesn’t exist or doesn’t have the relevant parameters, refer to our dedicated server guide for the correct setup. Typing nano rustserver.cfg should let you edit parameters to your heart's content. Linux users should be using LGSM to edit their config via command line. If you installed via Rust Server Manager, the config parameters will be under the 'Server Config' tab. Simply edit the text of the file with notepad or another suitable text editor. This will be located in the main server directory. In Windows, you can change parameters via the. First, though, it’s worth re-iterating how exactly to change Rust’s server configuration options.
0 kommentar(er)
