GetCommandHandlers: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{ | {{Shared function}} | ||
__NOTOC__ | __NOTOC__ | ||
{{New items|3.0153|1.5.3| | {{New items|3.0153|1.5.3| | ||
This function is used to retrieve a list of all the registered command handlers of a given resource (or of all resources). | This function is used to retrieve a list of all the registered command handlers of a given resource (or of all resources). | ||
}} | }} | ||
{{New feature/item|3.0157|1.5.6|16256|Function also added client-side.}} | |||
==Syntax== | ==Syntax== | ||
Line 18: | Line 19: | ||
==Example== | ==Example== | ||
This example add a command to output list of all commands in the chat. | This example add a command to output list of all commands in the chat. | ||
<syntaxhighlight lang="lua"> | <syntaxhighlight lang="lua"> | ||
Line 50: | Line 50: | ||
) | ) | ||
</syntaxhighlight> | </syntaxhighlight> | ||
This example add a command to output list of all commands for the resource in the chat. Syntax: /commands [resource-name] | This example add a command to output list of all commands for the resource in the chat. Syntax: /commands [resource-name] | ||
<syntaxhighlight lang="lua"> | <syntaxhighlight lang="lua"> | ||
Line 67: | Line 65: | ||
) | ) | ||
</syntaxhighlight> | </syntaxhighlight> | ||
==See Also== | ==See Also== | ||
{{Server functions}} | {{Server functions}} |
Latest revision as of 09:53, 7 January 2019
This function is used to retrieve a list of all the registered command handlers of a given resource (or of all resources). Function also added client-side.
Syntax
table getCommandHandlers ( [ resource theResource ] )
Optional Arguments
NOTE: When using optional arguments, you might need to supply all arguments before the one you wish to use. For more information on optional arguments, see optional arguments.
- theResource: The resource from which you wish to retrieve all command handlers. Or leave it empty to retrieve command handlers of all resources.
Returns
Returns a table containing all the commands of the given resource or a table with subtables containing the command and theResource pointer ( { "command", theResource } ). See examples below if you don't understand it.
Example
This example add a command to output list of all commands in the chat.
addCommandHandler( "commands", function(player) local commandsList = {} --table to store commands --store/sort commands in the table where key is resource and value is table with commands for _, subtable in pairs( getCommandHandlers() ) do local commandName = subtable[1] local theResource = subtable[2] if not commandsList[theResource] then commandsList[theResource] = {} end table.insert( commandsList[theResource], commandName ) end --output sorted information in the chat for theResource, commands in pairs( commandsList ) do local resourceName = getResourceInfo( theResource, "name" ) or getResourceName( theResource ) --try to get full name, if no full name - use short name outputChatBox( "== "..resourceName.. " ==", player, 0, 255, 0 ) --output list of commands for _, command in pairs( commands ) do outputChatBox( "/"..command, player, 255, 255, 255 ) end end end )
This example add a command to output list of all commands for the resource in the chat. Syntax: /commands [resource-name]
addCommandHandler("commands", function( player, _, resourceName) local theResource = (resourceName and getResourceFromName(resourceName)) or resource outputChatBox( "* Commands from "..getResourceName(theResource).." resource", player, 0, 255, 0 ) local commands = getCommandHandlers( theResource ) for _, command in pairs( commands ) do outputChatBox( "/"..command, player, 255, 255, 255 ) end end )
See Also
- getMaxPlayers
- getServerConfigSetting
- getServerHttpPort
- getServerName
- getServerPassword
- getServerPort
- isGlitchEnabled
- setGlitchEnabled
- setMaxPlayers
- setServerConfigSetting
- setServerPassword
- shutdown