MediaWiki API result

{
    "warnings": {
        "query": {
            "*": "Formatting of continuation data will be changing soon. To continue using the current formatting, use the 'rawcontinue' parameter. To begin using the new format, pass an empty string for 'continue' in the initial query."
        }
    },
    "query-continue": {
        "allpages": {
            "gapcontinue": "Server_Configuration"
        }
    },
    "query": {
        "pages": {
            "1316": {
                "pageid": 1316,
                "ns": 0,
                "title": "SemiAdmin",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''Semi Admins''' are admins who can perform only certain commands without having full referee or rcon access.\nThe commands each semiadmin can perform and the password each needs for logging in are defined via cvars.\n\n==cvar overview==\n\n{| cellspacing=\"2\" cellpadding=\"2\"\n|- style=\"background: #CCCCFF;\"\n!width=\"200\"|cvar\n!width=\"100\"|default\n!description\n|- style=\"background-color: #F4F4F4;\"\n|<tt style=\"color: green;\">b_semiAdminLevels</tt>\n|align=\"center\"|0\n|The number of semiadmin levels.\n|- style=\"background-color: #EEEEEE;\"\n|<tt style=\"color: green;\">b_semiAdminPass#</tt>\n|align=\"center\" style=\"color: gray;\"|undefined\n|Defines the password for each semiadmin level, where # is the level to set the password for.\n|- style=\"background-color: #F4F4F4;\"\n|<tt style=\"color:green;\">b_semiAdminCmds#</tt>\n|align=\"center\" style=\"color: gray;\"|undefined\n|A space-seperated list of commands a level # semiadmin can use.\n|}\n\n\n==cvar descriptions==\n\n===b_semiAdminLevels===\n\nDefines the number of semiadmin levels to use. Valid values are 0\u2013999. The default value of 0 disables semiadmin functionality.\n set b_semiAdminLevels 3   // you will have 3 semiadmin levels\n\n===b_semiAdminPass#===\n\nSets the password for each semiadmin level. # is the level to set the password for. Every level must have its own password.\n set b_semiAdminPass1 \"foo\"   // foo is the password to log in as a level 1 semiadmin\n\n===b_semiAdminCmds#===\n\nA 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.\n set b_semiAdminCmds1 \"clientkick say kick\"\n\nIn addition to built in commands, you can permit semi-admins to exec .cfg files or vstr cvars. \nIf 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.\n\n==Example configuration==\n\n set b_semiAdminLevels   \"3\"                 // we will have 3 semiadmin levels\n set b_semiAdminPass1    \"foo\"               // foo is the password for level 1\n set b_semiAdminPass2    \"bar\"               // the password for level 2\n set b_semiAdminPass3    \"foobar\"\n <span style=\"color: red;\">set b_semiAdminPass4    \"wrong\"             // will not work since we have only defined 3 semiadmin levels</span>\n set b_semiAdminCmds1    \"say map_restart\"\n set b_semiAdminCmds2    \"kick say clientkick g_friendyfire\"         // level 2 is allowed to change the cvar g_friendlyfire\n set b_semiAdminCmds3    \"set kick clientkick exec\"\n\nThe 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.\n\n\n==Usage of the semiadmin functionality==\n\nTo 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>.\n\nSome commands send information back, like the rcon command <code>status</code>. These information will not be sent back to the semiadmin.\n\nTyping <code>/sa</code> without any parameters will give you a list of commands you\u2019re allowed to perform.\n\n /sal baz                              // login with the password baz\n /semiadmin say Hello all              // perform the command \"say Hello all\"\n /sa                                   // shows you a list of commands you\u2019re able to perform\n\n[[Category:ETPro]]"
                    }
                ]
            },
            "1381": {
                "pageid": 1381,
                "ns": 0,
                "title": "SendServerCommand",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "__NOEDITSECTION__\net.trap_SendServerCommand() is used to send a command from the server to one or more clients. The first argument is the slot number of the client the command will be sent to. If it's equal to -1, the command will be broadcast to all clients.\n\nThe following commands can be issued with this function:\n\n==Printing==\n===Print===\n* \"'''print''' \\\"''Message''\\n\\\"\"\n:'''print''' prints ''Message'' to the client's console.\n\n===Center Print MoO=== \n* \"'''cpm''' \\\"''Message''\\n\\\"\"<br>\n:'''cpm''' prints ''Message'' to the client's annoucement area and console.\n\n===Center Print===\n* \"'''cp''' \\\"''Message''\\n\\\"\"<br>\n:'''cp''' prints ''Message'' to the center of the client's screen.\n\n===Banner Print===\n* \"'''b''' ''locations'' \\\"''Message''\\n\\\"\"<br>\n:'''b''' prints ''Message'' to the client's banner ''locations''<br>\n:the ''locations'' can be a number from 0 to 248\n:For compatibility, the old-style locations (from 0-4) are also supported.<br>\n:8 - player chat area<br>                \n:16 - left popup area (not recommended)<br>\n:32 - centered above the chat area<br>\n:64 - console only<br>\n:128 - banner area (recommended)(top of screen)\n\n===Scores Print===\n* \"'''sc''' \\\"''Message''\\n\\\"\"<br>\n:'''sc''' prints ''Message'' to the client's console and writes it to the statsdump file.\n\n==Chatting==\n===Chat===\n* \"'''c''' ''ClientNum'' \\\"''Message''\\\"\"<br>\n:'''c''' prints ''Message'' as a global chat message on behalf of the client specified by ''ClientNum''.\n\n\n===Team Chat===\n* \"'''tc''' ''ClientNum'' \\\"''Message''\\\" ''X-Location'' ''Y-Location'' ''Z-Location''\"<br>\n:'''tc''' prints ''Message'' as a team chat message on behalf of the client specified by ''ClientNum'',<br>\n:the ''X,Y,Z-Location's'' are optional parematers that represent the client's location,<br>\n:if the ''X,Y,Z-Location's'' are left out then the message will be printed without a location.\n\n===Fireteam Chat===\n* \"'''bc''' ''ClientNum'' \\\"''Message''\\\" ''X-Location'' ''Y-Location'' ''Z-Location''\".<br>\n:'''bc''' prints ''Message'' as a fireteam chat message on behalf of the client specified by ''ClientNum'',<br>\n:the ''X,Y,Z-Location's'' are parematers that represent the client's location.\n\n===Global Message===\n* \"'''chat''' \\\"''Message''\\\"\"<br>\n:'''chat''' prints ''Message'' like global message via rcon (''qsay'' command).\n\n==Voice Chat==\n===Global Voice Chat===\n* \"'''vchat''' ''VoiceOnly'' ''ClientNum'' 50 ''Vsay-String'' ''Vsay-Number'' \\\"''Custom-Message''\\\"\".<br>\n:'''vchat''' sends a global voice chat ''Vsay-String'' on behalf of the client specified by ''ClientNum''.<br>\n:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>),<br> ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files.<br>\n:''Custom-Message'' is by default \\\"\\\" (empty), otherwise it's the message that gets printed in the chat area.\n:if ''VoiceOnly'' is 0 it will print a chat message on behalf of ''ClientNum'' contaning the message<br>\n:if ''VoiceOnly'' is 1 it will only do the sound but not the message\n\n===Team Voice Chat===\n* \"'''vtchat''' ''VoiceOnly'' ''ClientNum'' 50 ''Vsay-String'' ''X-Location'' ''Y-Location'' ''Z-Location'' ''Vsay-Number'' \\\"''Custom-Message''\\\"\"<br>\n:'''vchat''' sends a team voice chat ''Vsay-String'' a on behalf of client ''ClienNtum''.<br>\n:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>),<br> ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files.<br>\n:the ''X,Y,Z-Location's'' parematers the represent the clients location.<br>\n:''Custom-Message'' is by default \\\"\\\" (empty), otherwise it's the message that gets printed in the chat area.\n:if ''VoiceOnly'' is 0 it will print a chat message on behalf of ''ClientNum'' contaning the message<br>\n:if ''VoiceOnly'' is 1 it will only do the sound but not the message\n\n===Fireteam Voice Chat===\n* \"'''vtchat''' ''VoiceOnly'' ''ClientNum'' 50 ''Fireteam-String'' ''X-Location'' ''Y-Location'' ''Z-Location'' ''Vsay-Number'' \\\"''Custom-Message''\\\"\"<br>\n:'''vchat''' will team voice chat ''Vsay-String'' on behalf of client ''ClienNum''.<br>\n:''Vsay-Number'' is by default random, however, it can be set by the player by passing parameters to the vsay command (/vsay <''Vsay-Number''> <''Vsay-String''>),<br> ''Vsay-Number'' represents the vsay number of Vsay as listed in the .voice files.<br>\n:the ''X,Y,Z-Location's'' parematers the represent the clients location.<br>\n:''Custom-Message'' is by default \\\"\\\" (empty), otherwise it's the message that gets printed in the chat area.\n:if ''VoiceOnly'' is 0 it will print a chat message on behalf of ''ClientNum'' contaning the message<br>\n:if ''VoiceOnly'' is 1 it will only do the sound but not the message\n\n==Fireteam==\n===Application===\n* \"'''application''' ''Number''\"\n:'''application''' shows a fireteam invation message to the client.<br>\n:if ''Number'' > -1 - the \"accept ... application to join your fireteam\" message shows up. In this case ''Number'' is the ClientNum of the applying client.<br>\n:if ''Number'' == -1 - the \"your aplication has been submitted\" message shows up.<br>\n:if ''Number'' == -2 - the \"your aplication failed\" message shows up.<br>\n:if ''Number'' == -3 - the \"your aplication has been approved\" message shows up.<br>\n:if ''Number'' == -4 - the \"your aplication reply has been sent\" message shows up.\n\n===Proposition===\n* \"'''proposition''' ''Number'' ''Number2''\"\n:'''proposition''' shows a fireteam proposition message to the client.<br>\n:if ''Number'' > -1 - the \"accept ... proposition to invite ... to your fireteam\" message shows up. In this case ''Number'' is the ClientNum of the proposed client, and ''Number2'' is the ClientNum of the proposing player.<br>\n:if ''Number'' == -1 - the \"your proposition has been submitted\" message shows up.<br>\n:if ''Number'' == -2 - the \"your proposition was rejected\" message shows up.<br>\n:if ''Number'' == -3 - the \"your proposition was accepted\" message shows up.<br>\n:if ''Number'' == -4 - the \"your proposition reply has been sent\" message shows up.<br>\n:''Number2'' is an optional paramater only used when ''Number'' > -1.\n\n===Invitation===\n* \"'''invitation''' ''Number''\"\n:'''invitation''' shows the fireteam invation message to the client.<br>\n:if ''Number'' > -1 - the \"accept .. invitation to join your fireteam\" message shows up. In this case ''Number'' is the ClientNum of the applying client.<br>\n:if ''Number'' == -1 - the \"your invitation has been submitted\" message shows up.<br>\n:if ''Number'' == -2 - the \"your invitation rejected\" message shows up.<br>\n:if ''Number'' == -3 - the \"your invitation was accepted\" message shows up.<br>\n:if ''Number'' == -4 - the \"your invitation reply has been sent\" message shows up.\n\n==Others== \n===Complaining===\n* \"'''complaint''' ''Number''\"<br>\n:'''complaint''' shows the complaint vote message to the client.<br>\n:if ''Number'' > 1 - the vote shows up. In this case ''Number'' is the ClientNum of the teamkilling player.<br>\n:if ''Number'' == -1 - the \"complaint filed\" message shows up.<br>\n:if ''Number'' == -2 - the \"complaint dismissed\" message shows up.\n\n===Spawning===\n* \"'''setspawnpt''' ''Number''\"<br>\n:'''setspawnpt''' sets the client game selected spawnpoint to number ''number''.\n\n===Kicking===\n* \"'''disconnect''' \\\"''reason''\\\"\"<br>\n:'''disconnect''' will disconnect the client it has been send with a \"Server disconnected\" message<br>\n:''reason'' is an optional parameter to show a reason after \"Server disconnected\"\n'''note:''' use trap_DropClient instead.\n\n===Configstrings===\n* \"'''cs''' ''Number'' \\\"''String''\\\"\"<br>\n: '''cs''' will set the clients configstringnumber ''Number'' to the ''String''\n'''Note:''' Setting individual players configstrings this way is probably a Bad Idea.\n\n===Shaders===\n* \"'''remapShader''' \\\"''OldShader''\\\" \\\"''NewShader''\\\" ''#''\"<br>\n: '''remapShader''' replaces any texture ''OldShader'' with ''NewShader''<br>\n: ''#'' is the Timeoffset, which currently should be left as ''0''.\n\n[[Category:ETPro]]\n[[Category:ETPro:Mods]]"
                    }
                ]
            }
        }
    }
}