Server Optimization - Revision history

Trainzack: Add Server Header

2023-12-31T23:03:53Z

Add Server Header

← Older revision		Revision as of 16:03, 31 December 2023
Line 1:		Line 1:
	~~=Server Optimizations=~~		{{ServerResources}}
	~~[[Category:Server]]~~
	== Unit limits ==		== Unit limits ==
	=== emp_sv_max_buildings ===		=== emp_sv_max_buildings ===

Trainzack: Category:Server

2023-12-31T22:56:13Z

Category:Server

← Older revision		Revision as of 15:56, 31 December 2023
Line 1:		Line 1:
	=Server Optimizations=		=Server Optimizations=
			[[Category:Server]]
	== Unit limits ==		== Unit limits ==
	=== emp_sv_max_buildings ===		=== emp_sv_max_buildings ===

Gilmore110j: Updated page.

2011-01-19T11:12:52Z

Updated page.

← Older revision		Revision as of 04:12, 19 January 2011
Line 1:		Line 1:
	~~This page is just for some generalizations that help your server run at optimal speed, with minimal lag, and hopefully, max fun :D.~~		=Server Optimizations=

	== ~~Important CVARS~~ ==		== Unit limits ==
			=== emp_sv_max_buildings ===
			Building limit per team, includes all buildings except turrets.

	Ok, CVARS are variables that can be changed in game temporarily, or can be changed and saved in a on your computer which gets loaded every time the server starts. A CVAR's setting is almost always a number, which sets the CVAR to do a specific task. That's probably the worst possible explanation, but that's that examples are for :D.		Default value: 64

	~~Ok, the CVAR~~		=== emp_sv_max_turrets ===
			Turret building limit per team.

	~~'''emp_sv_max_vehicles'''~~		Default value: 24

	~~sets the maximum number of vehicles a~~ team ~~can have~~. ~~This CVAR is numerical based, so the default is~~		=== emp_sv_max_vehicles ===
			Vehicle limit per team.

	~~'''~~32~~'''.~~		{{Tip\|Set this to the number of players per team.}}
			Default value: 32

	~~That's a BIG number, because that means that if a griefer on each~~ team ~~spammed heavy tanks, there would be a total of '''64''' heavy tanks on the map~~. ~~That is ''a lot'' of tanks. So unless you have a QX6950 Quad Core processor hosting your server, there's no way your server would have a chance. So, since I host on a 594 MHz processor, I set this to~~		=== emp_sv_max_walls ===
			Wall limit per team.

	~~'''12'''.~~		Default value: 64

	~~That's a reasonable amount of~~ vehicles ~~per team~~, ~~and this~~ can ~~usually~~ be ~~associated with the number of max players~~ on ~~the server, I like '''24''' because that's 12~~ per ~~team, and thats how many vehicles that team can have, so it works out nicely~~.		== Self-destruction timers ==
			In order to prevent abandoned vehicles using up server resources, vehicles without a player in them will self-destruct after a certain time interval. These intervals can be set on a per-chassis basis.

	~~Next CVAR:~~		=== emp_sv_vehicle_JEEP_selfdestruct_time ===
			Empty [[Jeep\|Jeeps]] will self-destruct after this time limit (in seconds).

	~~'''emp_sv_max_buildings'''~~		{{Tip\|Set this to a low value such as 120 or 60. Jeeps are cheap and players often buy them off of their own wages.}}
			Default value: 300

	~~This is the max number of buildings per team, default is..~~.		=== emp_sv_vehicle_LT_selfdestruct_time ===
			Empty [[Light_Tank\|Light Tanks]] will self-destruct after this time limit (in seconds).

	~~'''32'''~~		Default value: 300

	~~...which I find to be a relatively stable number. You don't want this too high as many buildings~~ = ~~CPU inhalation, but too small and you won~~'~~t have a fun game with each team having only a VF and a armory. Maybe bring~~ this ~~down to 25 or so, but really no lower than that~~.		=== emp_sv_vehicle_AFV_selfdestruct_time ===
			Empty [[AFV\|AFV's]] will self-destruct after this time limit (in seconds).

	~~== End? ==~~		Default value: 300

	~~There really isn~~'t much to it at all, its all about finding a number that works good for you. Remember, if something is confusing, try changing the CVAR to 'extremes'. Like if you don't know what the "netvitdist" CVARS do, try setting them to 1, and see how the game reacts.		=== emp_sv_vehicle_APC_selfdestruct_time ===
			Empty [[APC\|APC's]] will self-destruct after this time limit (in seconds).

	~~There are many other CVARS that can be toyed with, so go crazy and play with them! If you find out something not in the Wiki yet, '''SAY IT HERE!!!!''~~'. ~~It takes 3 seconds to make an account~~, ~~and you could be helping the community greatly~~. ~~Who knows, if it's big enough, your name might be put somewhere important~~ :D.		{{Tip\|APC's act as mobile spawnpoints. If players complain about their parked APC suddenly self-destructing, increase this value.}}
			Default value: 300

	~~Have fun on your servers guys!~~		=== emp_sv_vehicle_MED_selfdestruct_time ===
			Empty [[Medium_Tank\|Medium Tanks]] and [[Imperial_Tank\|Imperial Tanks]] will self-destruct after this time limit (in seconds).

			Default value: 300

			=== emp_sv_vehicle_HEAVY_selfdestruct_time ===
			Empty [[Northern_Heavy_Tank\|Northern Heavy Tanks]] and [[Imperial_Heavy_Tank\|Imperial Heavy Tanks]] will self-destruct after this time limit (in seconds).

			Default value: 300

			=== emp_sv_vehicle_ARTY_selfdestruct_time ===
			Empty [[Artillery\|Artillery Tanks]] will self-destruct after this time limit (in seconds).

			Default value: 300

Administrator at 19:44, 21 January 2008

2008-01-21T19:44:30Z

← Older revision		Revision as of 12:44, 21 January 2008
Line 1:		Line 1:
	~~fgh~~		This page is just for some generalizations that help your server run at optimal speed, with minimal lag, and hopefully, max fun :D.

			== Important CVARS ==

			Ok, CVARS are variables that can be changed in game temporarily, or can be changed and saved in a on your computer which gets loaded every time the server starts. A CVAR's setting is almost always a number, which sets the CVAR to do a specific task. That's probably the worst possible explanation, but that's that examples are for :D.

			Ok, the CVAR

			'''emp_sv_max_vehicles'''

			sets the maximum number of vehicles a team can have. This CVAR is numerical based, so the default is

			'''32'''.

			That's a BIG number, because that means that if a griefer on each team spammed heavy tanks, there would be a total of '''64''' heavy tanks on the map. That is ''a lot'' of tanks. So unless you have a QX6950 Quad Core processor hosting your server, there's no way your server would have a chance. So, since I host on a 594 MHz processor, I set this to

			'''12'''.

			That's a reasonable amount of vehicles per team, and this can usually be associated with the number of max players on the server, I like '''24''' because that's 12 per team, and thats how many vehicles that team can have, so it works out nicely.

			Next CVAR:

			'''emp_sv_max_buildings'''

			This is the max number of buildings per team, default is...

			'''32'''

			...which I find to be a relatively stable number. You don't want this too high as many buildings = CPU inhalation, but too small and you won't have a fun game with each team having only a VF and a armory. Maybe bring this down to 25 or so, but really no lower than that.

			== End? ==

			There really isn't much to it at all, its all about finding a number that works good for you. Remember, if something is confusing, try changing the CVAR to 'extremes'. Like if you don't know what the "netvitdist" CVARS do, try setting them to 1, and see how the game reacts.

			There are many other CVARS that can be toyed with, so go crazy and play with them! If you find out something not in the Wiki yet, '''SAY IT HERE!!!!'''. It takes 3 seconds to make an account, and you could be helping the community greatly. Who knows, if it's big enough, your name might be put somewhere important :D.

			Have fun on your servers guys!

66.215.156.199: New page: fgh

2007-11-30T09:48:38Z

New page: fgh

New page

fgh