- #Savage xr lan cfg update
- #Savage xr lan cfg password
- #Savage xr lan cfg download
- #Savage xr lan cfg windows
With the release of 1.03, Savage clients can download maps that they don't have.
#Savage xr lan cfg password
You set the sv_refereePassword cvar to be the password people use, and clients can do the following: You can set a ref password to allow special people to drop in and take over as ref. If you want to disable guess referees, you should set sv_allowGuestRef 0 in your autoexec.cfg. The guest referee can change the races and the map on the server.
Savage has a referee system, where the first person to join a server gets appointed the guest referee.
#Savage xr lan cfg update
You can edit dedicated_server.bat or dedicated_server.sh to disable running the updater if you don't want to ever update your server. Please note that even if you disable auto-patching, the default dedicated server files will still run the updater the next time you restart the game. If you want to disable this, "set sv_autopatchmyserver 0". If they have a game going, they quit at the end of the match. If they are empty, they quit immediately. This is because when we release a new patch, we send a notification to all running servers to tell them there is an update available. Since we release patches, we have a system where when servers quit, they run the updater and then restart. NOTE: You will get a long server frame on startup, and if you scroll the console window in Windows, it will freeze the application while you scroll, which will result in a long server frame message (and a pause for everyone on the server). You either need to lower the number of players on the server, kill other programs that are using CPU, or get a faster machine to run the server. If you are running the server and see "long server frame" messages, it probably means your CPU is drowning. Note that you could do: set autoexec "exec /myconfig.cfg" to have it run a cfg file in the game/ directory after running autoexec.cfg, so you don't have to put all the settings on the command line The autoexec cvar is a special cvar we added that is evaluated after autoexec.cfg is run, so you can override settings in autoexec.cfg using that variable. If you want to pass in things on the command line that will be evaluated after the game has finished starting up, you can do the following: silverback.exe set autoexec "command here" It is ALWAYS safe to put the variable settings in autoexec.cfg.Ĭommands you pass in on the command line will be run right after startup.cfg is loaded, far before many variables have been registered. autoexec.cfg is loaded after everything has been initialized, so all the variables are sure to exist at this point. Here's a general rule for setting variables in Savage: svr_ variables are in the core engine, and usually it's fine to put them in startup.cfg sv_ variables are in the game code, and they should be put in autoexec.cfg in the game/ directory. You have about 30 chars that display in the client. To set the name of the server, you want to set the svr_name cvar to the name you want to appear. You can set the maximum number of clients by setting the svr_maxclients cvar either on the command line (like silverback.exe set svr_maxclients 16), or in a file called startup.cfg in your Savage directory (or in ~/.savage/ if you are running a Linux server). We run 48 player servers on a 1 GHz P3 easily though, and it uses around 50-80% cpu. CPU usage will be inconsistent, but it might spike high if people are doing a lot of shots against buildings (which does per-poly collision tests). The server will probably never use more than 90 megs of ram, it doesn't really grow much with players, so ram shouldn't be an issue on servers. Incoming bandwidth is usually around 1-4 kilobytes/sec per player. So a 32-player game will use up to about 500 kbytes / sec. If a player is using the DSL/LAN settings (most are), they will suck down between 8 and 15 kilobytes / sec. Savage servers take a fair amount of uploading bandwidth. In Linux, to run a dedicated server you run.
#Savage xr lan cfg windows
To run a Windows dedicated server, just run dedicated_server.bat. 1.6 Administering Your Server Remotely:.
0 kommentar(er)
