Silent FAQ - Revision history

Gaoesa: /* Mod Setup Questions */

2015-09-13T20:32:53Z

Mod Setup Questions

← Older revision		Revision as of 20:32, 13 September 2015
Line 232:		Line 232:
	read logs. The logs will inform all the needed changes for the loading screen. The modification is generally done by adding		read logs. The logs will inform all the needed changes for the loading screen. The modification is generally done by adding
	_silent to the name of the image file.		_silent to the name of the image file.

			== Voice Chats ==
			Q: I have uploaded custom voice chat menu to the server but when I'm on the server the original voice chat menu opens without my customizations.

			A: See [[Silent_Creating_Custom_Menu\|Creating Custom Menu]].

Gaoesa: /* Customizing Loading Screen */

2015-09-13T12:00:34Z

Customizing Loading Screen

← Older revision		Revision as of 12:00, 13 September 2015
Line 224:		Line 224:

	== Customizing Loading Screen ==		== Customizing Loading Screen ==
	Starting from silEnT 0.9.0, server admins can customize the loading screen. This is opposed to modifying the global loading screen.		Q: How do I customize the loading screen?

			A: Starting from silEnT 0.9.0, server admins can customize the loading screen. This is opposed to modifying the global loading screen.
	These modifications are loaded and used only when connecting to a server that references the custom loading screen.		These modifications are loaded and used only when connecting to a server that references the custom loading screen.

Gaoesa: /* Customizing Loading Screen */

2015-09-13T11:10:23Z

Customizing Loading Screen

← Older revision		Revision as of 11:10, 13 September 2015
Line 224:		Line 224:

	== Customizing Loading Screen ==		== Customizing Loading Screen ==
	Starting from silEnT 0.9.0, server admins can customize the loading screen. This is ~~oppsed~~ to modifying the global loading screen.		Starting from silEnT 0.9.0, server admins can customize the loading screen. This is opposed to modifying the global loading screen.
	These modifications are loaded and used only when connecting to a server that references the custom loading screen.		These modifications are loaded and used only when connecting to a server that references the custom loading screen.

Gaoesa at 11:05, 13 September 2015

2015-09-13T11:05:47Z

← Older revision		Revision as of 11:05, 13 September 2015
Line 222:		Line 222:
	syntax = [name\|number]		syntax = [name\|number]
	levels = 5 6 7 8 9 10		levels = 5 6 7 8 9 10

			== Customizing Loading Screen ==
			Starting from silEnT 0.9.0, server admins can customize the loading screen. This is oppsed to modifying the global loading screen.
			These modifications are loaded and used only when connecting to a server that references the custom loading screen.

			To convet existing loading screen customizations to silEnT mod, start a local server which references the old file and
			read logs. The logs will inform all the needed changes for the loading screen. The modification is generally done by adding
			_silent to the name of the image file.

Hellreturn: /* Player screenshots (PBSS) */

2015-07-28T20:52:28Z

Player screenshots (PBSS)

← Older revision		Revision as of 20:52, 28 July 2015
Line 210:		Line 210:
	To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.		To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.

	== Player screenshots ~~(PBSS)~~ ==		== Player screenshots ==
	Q: How do I take player screenshot? <br />		Q: How do I take player screenshot? <br />
	A: Currently we support 2.6b clients for taking player screenshots. You can add custom command in your shrubbot.cfg config to capture player screenshot. Through custom command you customize command alias and configure which level has permission to access it.		A: Currently we support 2.6b clients for taking player screenshots. You can add custom command in your shrubbot.cfg config to capture player screenshot. Through custom command you customize command alias and configure which level has permission to access it.
Line 217:		Line 217:

	[command]		[command]
	command = ~~pbss~~		command = ss
	exec = takess "[1?]" [i]		exec = takess "[1?]" [i]
	desc = take screenshot from someone		desc = take screenshot from someone
	syntax = [name\|number]		syntax = [name\|number]
	levels = 5 6 7 8 9 10		levels = 5 6 7 8 9 10

Hellreturn: /* Player screenshots (PBSS) */

2015-07-22T21:37:30Z

Player screenshots (PBSS)

← Older revision		Revision as of 21:37, 22 July 2015
Line 211:		Line 211:

	== Player screenshots (PBSS) ==		== Player screenshots (PBSS) ==
	Q: How do I take player screenshot?		Q: How do I take player screenshot? <br />
	A: Currently we support 2.6b clients for taking player screenshots. You can add custom command in your shrubbot.cfg config to capture player screenshot.		A: Currently we support 2.6b clients for taking player screenshots. You can add custom command in your shrubbot.cfg config to capture player screenshot. Through custom command you customize command alias and configure which level has permission to access it.

	''' Custom command '''		''' Custom command '''

Hellreturn at 21:36, 22 July 2015

2015-07-22T21:36:31Z

← Older revision		Revision as of 21:36, 22 July 2015
Line 209:		Line 209:

	To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.		To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.

			== Player screenshots (PBSS) ==
			Q: How do I take player screenshot?
			A: Currently we support 2.6b clients for taking player screenshots. You can add custom command in your shrubbot.cfg config to capture player screenshot.

			''' Custom command '''

			[command]
			command = pbss
			exec = takess "[1?]" [i]
			desc = take screenshot from someone
			syntax = [name\|number]
			levels = 5 6 7 8 9 10

Hellreturn: /* Forcecvar & sv_cvar */

2014-10-13T19:10:58Z

Forcecvar & sv_cvar

← Older revision		Revision as of 19:10, 13 October 2014
Line 209:		Line 209:

	To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.		To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.

	~~Example settings:~~
	~~<code>~~
	~~forcecvar r_drawfoliage "0"~~
	~~forcecvar cg_bloodFlash "0"~~
	~~forcecvar snaps 20~~
	~~forcecvar r_wolffog "0"~~
	~~forcecvar r_zfar 0~~
	~~forcecvar cl_wwwdownload 1~~
	~~forcecvar cl_allowdownload 1~~
	~~forcecvar r_softwareGL 0~~
	~~forcecvar cl_nodelta 0~~
	~~forcecvar cl_timenudge 0~~
	~~sv_cvar cg_fov IN 90 120~~
	~~sv_cvar cl_maxpackets IN 30 100~~
	~~sv_cvar com_maxfps IN 43 250~~
	~~sv_cvar rate IN 32000 50000~~
	~~sv_cvar r_rmse EQ 0~~
	~~sv_cvar r_clamptoedge EQ 1~~
	~~sv_cvar cl_packetdup IN 0 1~~
	~~</code>~~

Hellreturn: /* Forcecvar & sv_cvar */

2014-10-13T19:06:49Z

Forcecvar & sv_cvar

← Older revision		Revision as of 19:06, 13 October 2014
Line 209:		Line 209:

	To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.		To use the possibility, the g_mapConfigs must be set. All forcecvar and sv_cvar commands that are placed in the default.cfg, will be executed on every map start. Those settings can be overloaded by using a map specific cfg name [mapname].cfg. More help is available at silEnT forums.

			Example settings:
			<code>
			forcecvar r_drawfoliage "0"
			forcecvar cg_bloodFlash "0"
			forcecvar snaps 20
			forcecvar r_wolffog "0"
			forcecvar r_zfar 0
			forcecvar cl_wwwdownload 1
			forcecvar cl_allowdownload 1
			forcecvar r_softwareGL 0
			forcecvar cl_nodelta 0
			forcecvar cl_timenudge 0
			sv_cvar cg_fov IN 90 120
			sv_cvar cl_maxpackets IN 30 100
			sv_cvar com_maxfps IN 43 250
			sv_cvar rate IN 32000 50000
			sv_cvar r_rmse EQ 0
			sv_cvar r_clamptoedge EQ 1
			sv_cvar cl_packetdup IN 0 1
			</code>

Gaoesa at 02:26, 19 September 2014

2014-09-19T02:26:31Z

← Older revision		Revision as of 02:26, 19 September 2014
Line 31:		Line 31:
	If the server is configured to kick for spoofed client identification, it can happen legitimately if the client connects directly from one silEnT server to another. Or if the server they are playing shuts down and they instantly reconnect. Instantly reconnecting again after the Spoofed Client Identification kick will work and the spoofed kick is a single event. If you find out more of these cases, please share the information with the silEnT community on forums.		If the server is configured to kick for spoofed client identification, it can happen legitimately if the client connects directly from one silEnT server to another. Or if the server they are playing shuts down and they instantly reconnect. Instantly reconnecting again after the Spoofed Client Identification kick will work and the spoofed kick is a single event. If you find out more of these cases, please share the information with the silEnT community on forums.

	~~<br>~~

	~~= PunkBuster =~~

	Starting from the version 0.3.0, the silEnT mod admins can use g_punkBuster server cvar. With this cvar, admins can either force clients to enable PunkBuster or deny players without GUIDs to enter the server. The values cannot be used in combination and they have no effect if the server is running PunkBuster.

	The possibility to deny players without GUID to enter is important because the silEnT mod no longer enforces bans without GUIDs. Also, an informative message is displayed to the player as what was the real reason he couldn't connect.

	The possibility to enable the client PunkBuster is important for the servers without running the PunkBuster themselves. This allows the players to be stored in the database and save XP if they have PunkBuster GUID from playing some server with PunkBuster enabled. If the client doesn't have punkbuster installed, this flag has no effect and it doesn't deny the player from connecting to the server. Also, silEnT mod doesn't do anything else but enables the client PunkBuster. The GUID must be acquired in the normal way.

	~~The values cannot be used in combination because the player will get denied access to the server before his PunkBuster starts if the value 2 is set. ''g_punkBuster ''~~

	~~1 ; Enable client PunkBuster.~~

	~~2 ; Do not allow players without GUIDs to enter the server.~~

	~~''Important:'' Neither of the values should be used if the server is running the PunkBuster in the server side.~~

	~~<br>~~

	= Team Death Match =		= Team Death Match =