![]() ![]() When the server restarts, the first one in will now take the public "slot 0" position. Log into your server with your rcon password, then enter the following commands: For example, lets say you have a 16-player server: If you only wanted to do this occasionally, and you have telnet access into your server, you can log in and change the value, then restat the server, without messing with the config file. One caveat, if the player who occupies "Slot 0" (Index 0) leaves the game, then the game is no longer in private mode until all players leave and the server restarts. Briefly, you set the value "gam_ctPrivateSlots" to be one less than "gam_ctMaxPlayers". I will occasionally run mine in that mode to keep the game so only my friends can join. In this mode, the first person to join the server occupies "Slot 0" and nobody else can join the server unless they are in the Slot 0 player's friends list (i.e., they have to join via the "Join Game" menu option under the Steam friends list). However, one of the guys in our clan figured out how to operate the server in a sort-of private fashion using "reserved slots". I haven't found a use for any of the "net_" settings. I have tried numerous things with the commands provided, same as rubregg, and none of them seem to work. I have the same question/observation regarding passwords for the server. Removing the if clause that checks for the binary name fixed these errors for me (in my case lines 13-17 of runSam3_DedicatedServer.sh, might change with updates). Server crashing with memory access error - runSam3_DedicatedServer.sh Line 17.If you're running your server on Linux, just copy the config file over to your server (not 100% sure if it's a "must", but having unix-type line endings and UTF-8 encoding can't hurt if you're editing your config file on Windows you can use, for example, Notepad2 [for stuff like that). If you're running it in the background, kill it with signal 2 (SIGINT = Ctrl-C), not signal 15 (SIGTERM).Īngelo on seriouszone for creating server config files. If you're running it in the foreground, shut it down with Ctrl-C. I found this information on the site I've already linked to above [in the Daemon Sam section (this is for Linux). (If you get errors, some of them might not appear in the server log, only in the console log.) Bin/runSam3_DedicatedServer.sh +exec sam.cfg +gameoptions &> Log/Sam3_console.log &This will run your server in the background and all console output will be written to. You'll find it in the 'Help' folder of your server installation.Įxample line to launch your server on linux: I also found some useful information here If you're running the server on linux, that FAQ also has the link to Valve's SteamCMD instructions (the old installation method via hldsupdatetool is obsolete, you'll have to use SteamCMD now, with appid 41080). Start on the official FAQ, currently 1.6 and 1.10. But for us newcomers I thought I'd start this topic to keep information on running Serious Sam 3 dedicated servers in one place.Ī few things have been popping up here and there, and it's probably better to keep it all together in one noobs-like-me: Ask you-veterans-out-there: Please help us on our way and correct us where we wander astray. I suspect that many things about Sam3 Servers are very similar to the older Serious Sam games so a lot of this might be utterly obvious to you veterans. I'm figuring out things as I go along myself and while I'm not new to running servers I surely am very new to Sam (instant love). First of all: I am not the expert here (the experts are at ). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |