SemiAdmin - Revision history

ReyalP: /* b_semiAdminCmds# */ cvars and cfgs

2007-04-24T02:23:17Z

‎b_semiAdminCmds#: cvars and cfgs

Nano at 18:18, 7 November 2006

2006-11-07T18:18:08Z

=FF=im2good4u: added set becase they dot work whitout it

2005-11-24T20:58:22Z

added set becase they dot work whitout it

WeblionX at 17:39, 5 November 2005

2005-11-05T17:39:12Z

Fusen at 15:43, 5 November 2005

2005-11-05T15:43:42Z

Fusen at 14:58, 5 November 2005

2005-11-05T14:58:17Z

Fusen at 14:50, 5 November 2005

2005-11-05T14:50:17Z

Fusen at 14:48, 5 November 2005

2005-11-05T14:48:57Z

New page

[[ETPro]] allows admins to use SemiAdmins. These are admins who can do some server commands without having full [[rcon]] access.

Semiadmin is split up in levels from 1 to 999 but you probably wont need them all, each level can have different commands.

----

First you need a server variable called:

''b_semiAdminLevels #''

This variable uses 1 number, it is the number of semiadmin levels you want use
the number can be from 0 to 999, where 0 is no semiadmins at all. Any value higher than 0 is the number of levels so if you have it set to 2 you will have 2 semiadmin levels.

----

The second thing you need is the password this is done by a variable called:
''b_semiAdminPass# "thepassword"''

The # is the level number you want to use for this password.
so b_semiadminpass2 "lol" will make lol the password to log into level 2, but b_semiadminlevels much be 2 or higher then 2 for level 2 to work.
Also every level must have its own password since the password is used to choose to witch level a person logs in like:
b_semiadminpass1 "omg"
b_semiadminpass2 "lol" this will make any1 that log in with lol a level 2 semiadmin and every1 that logs in with omg a level 1 semiadmin.

----

Third, you need the command that can be used by a level this is done by a variable called:

''b_semiAdminCmds# "command"''

The # is the level number you want to use for these commands.
each command must be separated with a space so:
b_semiadmincmds1 "say broadcast" allows any level 1 semiadmin to use both broadcast and say any arguments that are added to any of those commands are just send along so people could do things like /sa say "hello all"

Be careful with that in cases of b_semiadmincmds2 "exec vstr set" the level2 semiadmin can add any arguments to these commands so, they can exec any .cfg on the server using /sa exec filename.cfg. and, they can vstr any string using /sa vstr stringname and, they can also set any cvar using /sa set cvarname value this means they can even set rconpassword Very Happy
But this can be done a different way:
you can add the variable in the cmd list just like you wont need "set" in the server console.
For strings that you want to vstr you can add the string name in the cmd list then a semiadmin can /sa stringname to vstr it
this both allows you to limit the powers more specific like:
b_semiadmincmds3 "g_speed g_gravity m1 m2 m3"

For the rest of the cmds list can contain any console command and it will also be done as if it was typed in the server console itself with only 1 big exception:
Some command send information back like when you do /rcon status it will show the server status sadly this does not work for semiadmins, in case a semiadmin does a command like that it will do the command on the server only the text never reaches it back to the client. Rolling Eyes

Now when that is all done people should be able to log in, this is done by the command /semiadminlogin or short /sal like this:

''/semiadminlogin passwordofyourlevel''

If it succeeds it will broadcast ‘yourplayername has become a semiadmin’ and in your console it says seminadmin level yourlevel logged in. Now you can start being an evil admin.

To do server commands you use the command /semiadmin or /sa like:

''/semiadmin yourcommand''

If you don't know what commands you can do you can just type /sa to get your level number and your commands.
if the command is not in your command list (/sa) you cannot use it.

← Older revision		Revision as of 02:23, 24 April 2007
Line 41:		Line 41:
	set b_semiAdminCmds1 "clientkick say kick"		set b_semiAdminCmds1 "clientkick say kick"

		+	In addition to built in commands, you can permit semi-admins to exec .cfg files or vstr cvars.
		+	If blah is in b_semiAdminCmds# <code>sa blah</code> looks for a file named blah.cfg and then a cvar named blah.cvar, and finally a builtin command named blah.

	==Example configuration==		==Example configuration==

@@ Line 1: / Line 1: @@
-[[ETPro]] allows admins to use SemiAdmins. These are admins who can do some server commands without having full [[rcon]] access.
+'''Semi Admins''' are admins who can perform only certain commands without having full referee or rcon access.
-Semiadmin is split up in levels from 1 to 999 but you probably wont need them all, each level can have different commands.
+==cvar overview==
-== Setup ==
+{| cellspacing="2" cellpadding="2"
-First you need a server variable called:
+|- style="background: #CCCCFF;"
-This variable uses 1 number, it is the number of semiadmin levels you want use
+===b_semiAdminLevels===
-the number can be from 0 to 999, where 0 is no semiadmins at all. Any value higher than 0 is the number of levels so if you have it set to 2 you will have 2 semiadmin levels.
-== Setting Password ==
+===b_semiAdminPass#===
-The second thing you need is the password this is done by a variable called:
+Sets the password for each semiadmin level. # is the level to set the password for. Every level must have its own password.
-<pre>set b_semiAdminPass# "thepassword"</pre>
+ set b_semiAdminPass1 "foo"   // foo is the password to log in as a level 1 semiadmin
-The # is the level number you want to use for this password.
+A space-seperated list of commands a semiadmin with level # is allowed to perform. Be carefull with commands like <code>set</code>, <code>exec</code>, <code>vstr</code> etc.
-so b_semiadminpass2 "lol" will make 'lol' the password to log into level 2, but b_semiadminlevels must be 2 or higher than 2 for level 2 to work.
+ set b_semiAdminCmds1 "clientkick say kick"
-Also every level must have its own password, since the password is used to choose which level a person logs in like:
-''set b_semiadminpass1 "omg"''
-''set b_semiadminpass2 "lol"'' this will make anyone that logs in with 'lol' a level 2 semiadmin and everyone that logs in with 'omg' a level 1 semiadmin.
-== Commands ==
+==Example configuration==
-Third, you need the command that can be used by a level this is done by a variable called:
+The above lines will create 3 semiadmin levels. Each level has its own password and an own list of commands which can be used by a semiadmin with that level.
-The # is the level number you want to use for these commands.
+To log in as a semiadmin use the command <code>/semiadminlogin <password></code> or the shorter one <code>/sal <password></code>. Performing a command is done via the commands <code>/semiadmin <command></code> or <code>/sa <command></code>.
-Each command must be separated with a space so ''b_semiadmincmds1 "say broadcast"'' allows any level 1 semiadmin to use both 'broadcast' and 'say', any arguments that are added to any of those commands are also sent, so it's possible to do ''/sa say "hello all"''
-Be careful with that in cases of ''b_semiadmincmds2 "exec vstr set"'' the level2 semiadmin can add any arguments to these commands so, they can exec any .cfg on the server using ''/sa exec filename.cfg'' and, they can vstr any string using ''/sa vstr stringname'' and they can also set any cvar using ''/sa set cvarname value'' this means they can even set ''rconpassword Very Happy''
+Some commands send information back, like the rcon command <code>status</code>. These information will not be sent back to the semiadmin.
-But this can be done a different way, you can add the variable in the cmd list just like you wont need "set" in the server console.
-For strings that you want to vstr you can add the string name in the cmd list then a semiadmin can /sa stringname to vstr it
-This both allows you to limit the powers more specific e.g.
-<pre>set b_semiadmincmds3 "g_speed g_gravity m1 m2 m3"</pre>
-For the rest of the cmds list can contain any console command and it will also be done as if it was typed in the server console itself with only 1 big exception:
+Typing <code>/sa</code> without any parameters will give you a list of commands you’re allowed to perform.
-Some command send information back, such as when you do ''/rcon status'' it will show the server status, sadly this does not work for semiadmins, if a semiadmin does a command like that, it will do the command on the server only but the text will never reach it back to the client.
+ /sal baz                              // login with the password baz
-== Logging In ==
+ /semiadmin say Hello all              // perform the command "say Hello all"
+ /sa                                   // shows you a list of commands you’re able to perform
-Now when that is all done people should be able to log in, this is done by the command ''/semiadminlogin'' or short ''/sal'' like this:
-−
-<pre>/semiadminlogin passwordofyourlevel</pre>
-−
-−
-If it succeeds it will broadcast ''‘playername has become a semiadmin’'' and in your console it says ''seminadmin level yourlevel logged in''. Now you can start using the SemiAdmon commands.
-−
-To do server commands you use the command ''/semiadmin'' or ''/sa'' like:
-−
-<pre>/semiadmin yourcommand</pre>
-−
-−
-If you don't know what commands you can do you can just type /sa to get your level number and your commands.
-if the command is not in your command list (/sa) you cannot use it.
 [[Category:ETPro]]

@@ Line 16: / Line 16: @@
 The second thing you need is the password this is done by a variable called:
-<pre>b_semiAdminPass# "thepassword"</pre>
+<pre>set b_semiAdminPass# "thepassword"</pre>
@@ Line 22: / Line 22: @@
 so b_semiadminpass2 "lol" will make 'lol' the password to log into level 2, but b_semiadminlevels must be 2 or higher than 2 for level 2 to work.
 Also every level must have its own password, since the password is used to choose which level a person logs in like:
-''b_semiadminpass1 "omg"''
+''set b_semiadminpass1 "omg"''
-''b_semiadminpass2 "lol"'' this will make anyone that logs in with 'lol' a level 2 semiadmin and everyone that logs in with 'omg' a level 1 semiadmin.
+''set b_semiadminpass2 "lol"'' this will make anyone that logs in with 'lol' a level 2 semiadmin and everyone that logs in with 'omg' a level 1 semiadmin.
@@ Line 31: / Line 31: @@
 Third, you need the command that can be used by a level this is done by a variable called:
-<pre>b_semiAdminCmds# "command"</pre>
+<pre>set b_semiAdminCmds# "command"</pre>
@@ Line 41: / Line 41: @@
 For strings that you want to vstr you can add the string name in the cmd list then a semiadmin can /sa stringname to vstr it
 This both allows you to limit the powers more specific e.g.
-<pre>b_semiadmincmds3 "g_speed g_gravity m1 m2 m3"</pre>
+<pre>set b_semiadmincmds3 "g_speed g_gravity m1 m2 m3"</pre>
 For the rest of the cmds list can contain any console command and it will also be done as if it was typed in the server console itself with only 1 big exception:

← Older revision		Revision as of 17:39, 5 November 2005
Line 63:		Line 63:
	If you don't know what commands you can do you can just type /sa to get your level number and your commands.		If you don't know what commands you can do you can just type /sa to get your level number and your commands.
	if the command is not in your command list (/sa) you cannot use it.		if the command is not in your command list (/sa) you cannot use it.
		+
		+	[[Category:ETPro]]

@@ Line 3: / Line 3: @@
 Semiadmin is split up in levels from 1 to 999 but you probably wont need them all, each level can have different commands.
+== Setup ==
-----
-−
-−
 First you need a server variable called:
-''b_semiAdminLevels #''
+<pre>b_semiAdminLevels #</pre>
@@ Line 16: / Line 13: @@
-----
+== Setting Password ==
-−
 The second thing you need is the password this is done by a variable called:
-''b_semiAdminPass# "thepassword"''
+<pre>b_semiAdminPass# "thepassword"</pre>
@@ Line 30: / Line 26: @@
-----
+== Commands ==
 Third, you need the command that can be used by a level this is done by a variable called:
-''b_semiAdminCmds# "command"''
+<pre>b_semiAdminCmds# "command"</pre>
@@ Line 45: / Line 41: @@
 For strings that you want to vstr you can add the string name in the cmd list then a semiadmin can /sa stringname to vstr it
 This both allows you to limit the powers more specific e.g.
-''b_semiadmincmds3 "g_speed g_gravity m1 m2 m3"''
+<pre>b_semiadmincmds3 "g_speed g_gravity m1 m2 m3"</pre>
 For the rest of the cmds list can contain any console command and it will also be done as if it was typed in the server console itself with only 1 big exception:
@@ Line 51: / Line 47: @@
-----
+== Logging In ==
-−
 Now when that is all done people should be able to log in, this is done by the command ''/semiadminlogin'' or short ''/sal'' like this:
-''/semiadminlogin passwordofyourlevel''
+<pre>/semiadminlogin passwordofyourlevel</pre>
@@ Line 63: / Line 58: @@
 To do server commands you use the command ''/semiadmin'' or ''/sa'' like:
-''/semiadmin yourcommand''
+<pre>/semiadmin yourcommand</pre>
 If you don't know what commands you can do you can just type /sa to get your level number and your commands.
 if the command is not in your command list (/sa) you cannot use it.

@@ Line 40: / Line 40: @@
 The # is the level number you want to use for these commands.
 each command must be separated with a space so:
-b_semiadmincmds1 "say broadcast" allows any level 1 semiadmin to use both broadcast and say any arguments that are added to any of those commands are just send along so people could do things like /sa say "hello all"
+''b_semiadmincmds1 "say broadcast"'' allows any level 1 semiadmin to use both broadcast and say any arguments that are added to any of those commands are just send along so people could do things like ''/sa say "hello all"''
-Be careful with that in cases of b_semiadmincmds2 "exec vstr set" the level2 semiadmin can add any arguments to these commands so, they can exec any .cfg on the server using /sa exec filename.cfg. and, they can vstr any string using /sa vstr stringname and, they can also set any cvar using /sa set cvarname value this means they can even set rconpassword Very Happy
+Be careful with that in cases of ''b_semiadmincmds2 "exec vstr set"'' the level2 semiadmin can add any arguments to these commands so, they can exec any .cfg on the server using ''/sa exec filename.cfg''. and, they can vstr any string using ''/sa vstr stringname'' and, they can also set any cvar using ''/sa set cvarname value'' this means they can even set ''rconpassword Very Happy''
 But this can be done a different way:
 you can add the variable in the cmd list just like you wont need "set" in the server console.