Set - Revision history

Lettify: fixed revision

2020-10-12T18:42:28Z

fixed revision

← Older revision		Revision as of 18:42, 12 October 2020
Line 17:		Line 17:

	==Example==		==Example==
	~~Este ejemplo establece una configuración especificada con un valor~~. ~~Esta es una configuración~~ local ~~que pertenece al recurso en el que se ejecuta el código~~.		This example sets a specified setting with a Value. This is a ''local'' setting belonging to the resource that the code is run in.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function setAclRights(playerElement, commandName, acl, value, type)		function setAclRights(playerElement, commandName, acl, value, type)

PandFort: /* Example */

2020-10-12T18:18:10Z

Example

← Older revision		Revision as of 18:18, 12 October 2020
Line 17:		Line 17:

	==Example==		==Example==
	~~This example sets a specified setting with a Value~~. ~~This is a ''~~local~~'' setting belonging to the resource that the code is run in~~.		Este ejemplo establece una configuración especificada con un valor. Esta es una configuración local que pertenece al recurso en el que se ejecuta el código.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function setAclRights(playerElement, commandName, acl, value, type)		function setAclRights(playerElement, commandName, acl, value, type)

EAi: /* Example */ spelling

2010-05-04T01:04:56Z

Example: spelling

← Older revision		Revision as of 01:04, 4 May 2010
Line 27:		Line 27:
	print(getPlayerName(playerElement).." has changed "..acl.." to "..value)		print(getPlayerName(playerElement).." has changed "..acl.." to "..value)
	else		else
	outputChatBox("Error ~~happend~~ while changing the Acl "..acl.." value to "..value)		outputChatBox("Error happened while changing the Acl "..acl.." value to "..value)
	print(getPlayerName(playerElement).." ~~tryed~~ to change "..acl.." to "..value)		print(getPlayerName(playerElement).." tried to change "..acl.." to "..value)
	end		end
	end		end

Jason Gregory: /* Example */

2010-05-03T12:00:51Z

Example

← Older revision		Revision as of 12:00, 3 May 2010
Line 23:		Line 23:
	return outputChatBox("Syntax: /setacl <acl> <value>")		return outputChatBox("Syntax: /setacl <acl> <value>")
	end		end
	set ( acl, value )		if set ( acl, value ) then
	outputChatBox("Acl "..acl.." value set to "..value)		outputChatBox("Acl "..acl.." value set to "..value)
	print(getPlayerName(playerElement).." has changed "..acl.." to "..value)		print(getPlayerName(playerElement).." has changed "..acl.." to "..value)
			else
			outputChatBox("Error happend while changing the Acl "..acl.." value to "..value)
			print(getPlayerName(playerElement).." tryed to change "..acl.." to "..value)
			end
	end		end
	addCommandHandler("setacl", setAclRights)		addCommandHandler("setacl", setAclRights)
	</syntaxhighlight>		</syntaxhighlight>


	==See Also==		==See Also==
	{{Settings registry functions}}		{{Settings registry functions}}

Jason Gregory: Adding a example Command

2010-05-03T11:58:25Z

Adding a example Command

← Older revision		Revision as of 11:58, 3 May 2010
Line 17:		Line 17:

	==Example==		==Example==
	This example sets a setting ~~called ''respawnTime''~~ with a ~~value of 1000~~. This is a ''local'' setting belonging to the resource that the code is run in.		This example sets a specified setting with a Value. This is a ''local'' setting belonging to the resource that the code is run in.
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	set ( "~~respawnTime~~", ~~1000~~ )		function setAclRights(playerElement, commandName, acl, value, type)
			if not acl or not value then
			return outputChatBox("Syntax: /setacl <acl> <value>")
			end
			set ( acl, value )
			outputChatBox("Acl "..acl.." value set to "..value)
			print(getPlayerName(playerElement).." has changed "..acl.." to "..value)
			end
			addCommandHandler("setacl", setAclRights)
	</syntaxhighlight>		</syntaxhighlight>


	==See Also==		==See Also==
	{{Settings registry functions}}		{{Settings registry functions}}

Talidan at 18:10, 3 November 2008

2008-11-03T18:10:42Z

← Older revision		Revision as of 18:10, 3 November 2008
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Needs_Checking\|''get'' allows retrieval of multiple values if the setting has multiple values in the settings.xml (e.g. [ <nowiki>"hah1","hah2","hah3"</nowiki> ] retrieves "hah1","hah2","hah3"). ''set'' however does not allow for setting these multiple values, even though ''get'' can retrieve them. The only way to set multiple values to a setting is to modify the xml. Therefore unlimited params should be given to ''set''.}}
	{{Server function}}		{{Server function}}
	This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].		This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].

EAi at 14:57, 7 January 2008

2008-01-07T14:57:21Z

← Older revision		Revision as of 14:57, 7 January 2008
Line 4:		Line 4:
	This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].		This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].

			It's important to note that set ''always'' writes to the settings.xml file, even if [[get]] read the value from a resource's meta.xml. This means that the admin can specify settings in the settings.xml that override the resource's defaults, but that the defaults can still be retrieved if need be. As a general principle, resources should not be designed so that the admin is required to modify them, they should be 'black boxes'.
	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

EAi at 01:55, 3 January 2008

2008-01-03T01:55:43Z

← Older revision		Revision as of 01:55, 3 January 2008
Line 11:		Line 11:
	===Required Arguments===		===Required Arguments===
	*'''settingName:''' The name of the setting you want to set. See [[settings system#Setting names\|setting names]] for information on settings names.		*'''settingName:''' The name of the setting you want to set. See [[settings system#Setting names\|setting names]] for information on settings names.
	*'''value:''' The value to set the setting to. This can be any Lua data type, except for functions, most userdata (only [[resource]]s can be stored) and threads.		*'''value:''' The value to set the setting to. This can be any Lua data type, except for functions, most userdata (only [[resource]]s can't be stored) and threads.

	===Returns===		===Returns===

Talidan at 04:16, 22 December 2007

2007-12-22T04:16:46Z

← Older revision		Revision as of 04:16, 22 December 2007
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Needs_Checking\|''get'' allows retrieval of multiple values if the setting has multiple values in the settings.xml (e.g. [ "hah1","hah2","hah3" ] retrieves "hah1","hah2","hah3"). ''set'' however does not allow for setting these multiple values, even though ''get'' can retrieve them. The only way to set multiple values to a setting is to modify the xml. Therefore unlimited params should be given to ''set''.}}		{{Needs_Checking\|''get'' allows retrieval of multiple values if the setting has multiple values in the settings.xml (e.g. [ <nowiki>"hah1","hah2","hah3"</nowiki> ] retrieves "hah1","hah2","hah3"). ''set'' however does not allow for setting these multiple values, even though ''get'' can retrieve them. The only way to set multiple values to a setting is to modify the xml. Therefore unlimited params should be given to ''set''.}}
	{{Server function}}		{{Server function}}
	This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].		This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].

Talidan at 04:15, 22 December 2007

2007-12-22T04:15:53Z

← Older revision		Revision as of 04:15, 22 December 2007
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
			{{Needs_Checking\|''get'' allows retrieval of multiple values if the setting has multiple values in the settings.xml (e.g. [ "hah1","hah2","hah3" ] retrieves "hah1","hah2","hah3"). ''set'' however does not allow for setting these multiple values, even though ''get'' can retrieve them. The only way to set multiple values to a setting is to modify the xml. Therefore unlimited params should be given to ''set''.}}
	{{Server function}}		{{Server function}}
	This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].		This function is used to save arbitrary data under a certain name on the [[settings system\|settings registry]].