Silent Shrubbot - Revision history

Gaoesa: /* userxdb.db */

2015-10-15T14:08:47Z

userxdb.db

← Older revision		Revision as of 14:08, 15 October 2015
Line 1,434:		Line 1,434:
	== userxdb.db ==		== userxdb.db ==

	This is a file where silEnT stores less often needed information about the players. Such as personalized greetings. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify the file version for different silEnT versions and if necessary, silEnT will convert the file to a newer version. The old file will be ~~always~~ stored at the g_dbDirectory location with a _vxx added to ~~it's~~ name.		This is a file where silEnT stores less often needed information about the players. Such as personalized greetings. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify the file version for different silEnT versions and if necessary, silEnT will convert the file to a newer version. The old file will always be stored at the g_dbDirectory location with a _vxx added to its name.

	If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.		If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.

Gaoesa: /* userdb.db */

2015-10-15T14:08:27Z

userdb.db

← Older revision		Revision as of 14:08, 15 October 2015
Line 1,428:		Line 1,428:
	== userdb.db ==		== userdb.db ==

	This is a file where the silEnT stores information of the players. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify ~~this~~ file version for different silEnT versions and if necessary silEnT will convert the file to a newer version. The old file will be ~~always~~ stored at the g_dbDirectory location with a _vxx added to ~~it's~~ name.		This is a file where the silEnT stores information of the players. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify the file version for different silEnT versions and if necessary, silEnT will convert the file to a newer version. The old file will always be stored at the g_dbDirectory location with a _vxx added to its name.

	If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.		If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.

Gaoesa: /* userxdb.db */

2015-10-15T14:07:20Z

userxdb.db

← Older revision		Revision as of 14:07, 15 October 2015
Line 1,434:		Line 1,434:
	== userxdb.db ==		== userxdb.db ==

	This is a file where ~~the~~ silEnT stores information of the players ~~which is not needed for the most players~~. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify ~~this~~ file version for different silEnT versions and if necessary silEnT will convert the file to a newer version. The old file will be always stored at the g_dbDirectory location with a _vxx added to it's name.		This is a file where silEnT stores less often needed information about the players. Such as personalized greetings. This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify the file version for different silEnT versions and if necessary, silEnT will convert the file to a newer version. The old file will be always stored at the g_dbDirectory location with a _vxx added to it's name.

	If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.		If silEnT finds this file to be corrupted or unusable, it will not overwrite it. It will only refuse to initialize the shrubbot and therefore you must look at the logs if you encounter any problems with shrubbot. The error messages in the log are usually very descriptive.

Gaoesa: /* useradb.db */

2015-10-15T14:05:17Z

useradb.db

← Older revision		Revision as of 14:05, 15 October 2015
Line 1,440:		Line 1,440:
	== useradb.db ==		== useradb.db ==

	Starting from silEnT 0.6.0, this file holds the optional aliases database. To enable the database, g_dbMaxAliases cvar must be set to a positive integer. The aliases database can be disabled by setting g_dbMaxAliases to 0 ~~value~~ at any time and then re-~~enable the database~~ by setting the value back to a positive integer without any effect to the file. However, if the g_dbMaxAliases cvar is set to a smaller value ~~then~~ it was before, the aliases that exceed the threshold will be lost ~~unrecoverably~~.		Starting from silEnT 0.6.0, this file holds the optional aliases database. To enable the database, g_dbMaxAliases cvar must be set to a positive integer. The aliases database can be disabled by setting g_dbMaxAliases to 0 at any time and then re-enabled by setting the value back to a positive integer without any effect to the file. However, if the g_dbMaxAliases cvar is set to a smaller value than it was before, the aliases that exceed the threshold will be lost and cannot be recovered.

	This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify ~~this~~ file version for different silEnT versions and if necessary silEnT will convert the file to a newer version. The old file will be ~~always~~ stored at the g_dbDirectory location with a _vxx added to ~~it's~~ name.		This file is not hand editable. By editing this file by hand you risk it getting corrupted or causing error conditions. The silEnT will automatically identify the file version for different silEnT versions and if necessary, silEnT will convert the file to a newer version. The old file will always be stored at the g_dbDirectory location with a _vxx added to its name.

	If silEnT finds this file to be corrupted or unusable, it will not overwrite it. The error messages in the log are usually very descriptive about the ~~erros~~.		If silEnT finds this file to be corrupted or unusable, it will not overwrite it. The error messages in the log are usually very descriptive about the errors.

	= Shrubbot Limitations =		= Shrubbot Limitations =

Gaoesa: /* User Database & Commands */

2015-10-07T10:17:59Z

User Database & Commands

← Older revision		Revision as of 10:17, 7 October 2015
Line 897:		Line 897:
	User database is intended to store information of all the players that connect to the server. To enable user database g_dbDirectory must be set. The database stores information to identify different players and also XP data, rating data, overall stats data and shrubbot admin data. silEnT GUIDs are used to identify single players.		User database is intended to store information of all the players that connect to the server. To enable user database g_dbDirectory must be set. The database stores information to identify different players and also XP data, rating data, overall stats data and shrubbot admin data. silEnT GUIDs are used to identify single players.

	Shrubbot includes functionality for server admins to handle database userdata. All commands that handle users in the database will take the last 8 characters of the player ~~PunkBuster~~ GUID to identify the player to edit~~. This is not an unique identification but because EvenBalance has seen this to have enough uniqueness, it is good for the use of the database commands~~. Internally, the full GUID is used to identify the players.		Shrubbot includes functionality for server admins to handle database userdata. All commands that handle users in the database will take the last 8 characters of the player silEnT GUID to identify the player to edit. Internally, the full GUID is used to identify the players. Some commands have equivalent versions using last 8 characters of PunkBuster GUIDs to identify the player. These are needed for players who were stored into the database before the silEnT GUID was added and haven't connected to the server since.

	== !aliasesdel ==		== !aliasesdel ==

Gaoesa: /* User Database & Commands */

2015-10-07T10:14:24Z

User Database & Commands

← Older revision		Revision as of 10:14, 7 October 2015
Line 895:		Line 895:
	= User Database & Commands =		= User Database & Commands =

	User database is intended to store information of all the players that connect to the server. To enable user database g_dbDirectory must be set. The database stores information to identify different players and also XP data, rating data, overall stats data and shrubbot admin data. ~~PunkBuster~~ GUIDs are used to identify single players. If a player joining the server doesn't have a PB GUID, data about that player can not be saved. However, the user database can still be used to store data of those players who have enabled punkbuster on the client side.		User database is intended to store information of all the players that connect to the server. To enable user database g_dbDirectory must be set. The database stores information to identify different players and also XP data, rating data, overall stats data and shrubbot admin data. silEnT GUIDs are used to identify single players.

	Shrubbot includes functionality for server admins to handle database userdata. All commands that handle users in the database will take the last 8 characters of the player PunkBuster GUID to identify the player to edit. This is not an unique identification but because EvenBalance has seen this to have enough uniqueness, it is good for the use of the database commands. Internally, the full GUID is used to identify the players.		Shrubbot includes functionality for server admins to handle database userdata. All commands that handle users in the database will take the last 8 characters of the player PunkBuster GUID to identify the player to edit. This is not an unique identification but because EvenBalance has seen this to have enough uniqueness, it is good for the use of the database commands. Internally, the full GUID is used to identify the players.

Gaoesa: /* Shrubbot Limitations */

2015-10-07T10:06:10Z

Shrubbot Limitations

← Older revision		Revision as of 10:06, 7 October 2015
Line 1,456:		Line 1,456:
	'''Maximum number of player bans:''' 1023		'''Maximum number of player bans:''' 1023

	'''Maximum number of subnet bans:''' 128		'''Maximum number of subnet bans:''' 128 (512 since 0.9.0)

	'''Maximum length of ban reason:''' 1023		'''Maximum length of ban reason:''' 1023

Gaoesa: /* What Is Shrubbot */

2015-03-02T23:59:10Z

What Is Shrubbot

← Older revision		Revision as of 23:59, 2 March 2015
Line 1:		Line 1:
	= What Is Shrubbot=		= What Is Shrubbot=
	Shrubbot is an invention of Ryan Mannion. Shrubbot is an admin system that identifies the admin leveled players from PunkBuster GUIDs without the need for passwords. Shrubbot is also very flexible and allows creating many different admin levels with entirely different command sets. silEnT shrubbot is based on the work of the ETPub team. silEnT extends the functionality of the shrubbot where ever it is needed. Including user database that holds all the players that have visited the server. To access this database, new commands have been added to the original shrubbot command set. Some commands have been renamed to ease their use and so that they resemble commands from other ET mods that have advanced admin systems.		Shrubbot is an invention of Ryan Mannion. Shrubbot is an admin system that identifies the admin leveled players from silEnT and PunkBuster GUIDs without the need for passwords. Shrubbot is also very flexible and allows creating many different admin levels with entirely different command sets. silEnT shrubbot is based on the work of the ETPub team. silEnT extends the functionality of the shrubbot where ever it is needed. Including user database that holds all the players that have visited the server. To access this database, new commands have been added to the original shrubbot command set. Some commands have been renamed to ease their use and so that they resemble commands from other ET mods that have advanced admin systems.

	If you want to use shrubbot, the cvar g_dbDirectory must be set. If it is not set, the shrubbot will not be in use. If you want to edit the default levels, you must create or copy existing shrubbot.cfg file to the ~~folder~~ defined by g_dbDirectory setting. In case shrubbot command like !ban is used against a player and shrubbot.cfg file does not already exist, a new shrubbot.cfg file is created to store the needed data.		If you want to use shrubbot, the cvar g_dbDirectory must be set. If it is not set, the shrubbot will not be in use. If you want to edit the default levels, you must create or copy existing shrubbot.cfg file to the directory defined by the g_dbDirectory setting. In case shrubbot command like !ban is used against a player and a shrubbot.cfg file does not already exist, a new shrubbot.cfg file is created to store the needed data.

	The created file will also have the default level settings written to it. This file can be freely edited by hand and then after !readconfig command has been issued, the changes take effect on the server.		The created file will also have the default level settings written to it. This file can be freely edited by hand and then, after !readconfig command has been issued, the changes take effect on the server.

	= Shrubbot Commands =		= Shrubbot Commands =

Hellreturn: /* Sample shrubbot config */

2015-03-02T21:59:29Z

Sample shrubbot config

← Older revision		Revision as of 21:59, 2 March 2015
Line 1,498:		Line 1,498:
	[t] ammo for current weapon		[t] ammo for current weapon

	== Sample shrubbot config ==		= Sample shrubbot config =

	<pre>		<pre>

Hellreturn at 21:59, 2 March 2015

2015-03-02T21:59:07Z

← Older revision		Revision as of 21:59, 2 March 2015
Line 1,497:		Line 1,497:

	[t] ammo for current weapon		[t] ammo for current weapon

			== Sample shrubbot config ==

			<pre>

			// silEnT mod - Sample Shrubbot.cfg file

			[level]
			level = 0
			name = Prole
			flags = iBaPzI
			greeting =
			greeting_sound =

			[level]
			level = 1
			name = Level 1
			flags = iBaPzIW1
			greeting = Level 1 [n] ^7just connected
			greeting_sound =

			[level]
			level = 2
			name = Level2
			flags = iBaPzIW1mx
			greeting = Level 2 [n] ^7just connected
			greeting_sound =

			[level]
			level = 3
			name = Level 3
			flags = iBaPzIW1mxpZSAURKrwlLdX259
			greeting = Level 3 [n] ^7just connected
			greeting_sound =

			[level]
			level = 4
			name = Level 4
			flags = iBaPzIW1mxpZSAURKrwlLdX259kbcVNn34678
			greeting = Level 4 [n] ^7just connected
			greeting_sound =

			[level]
			level = 5
			name = Level 5
			flags = *
			greeting = Level 5 [n] ^7just connected
			greeting_sound =

			</pre>