Call - Revision history

Tails at 17:25, 24 June 2026

2026-06-24T17:25:01Z

@@ Line 77: / Line 77: @@
 ==Example==
 <section name="Server" class="server" show="true">
 This extract shows adding of a "kills" column to the scoreboard resource. This then sets the ''gameShowKills'' variable to true(or false), telling the rest of the script to start outputting kills.
@@ Line 124: / Line 94: @@
 end
 </syntaxhighlight>
-'''scoreboard Resource:'''
+'''Scoreboard resource:'''
 <syntaxhighlight lang="lua">
 function removeScoreboardColumn(columnName)
@@ Line 133: / Line 103: @@
      -- What ever scripted ...
 end
 </syntaxhighlight>
 </section>

Srslyyyy: Merge note

2024-12-14T22:06:58Z

Merge note

← Older revision		Revision as of 22:06, 14 December 2024
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server client function}}		{{Server client function}}
	{{Important Note\|Calls (exports) may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource. Do not use exports in render events (like [[onClientRender]]), or in fast processing logic, unless you want to kill performance.}}		{{Important Note\|
	~~{{Important Note\|~~The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}		* Calls (exports) may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource. Do not use exports in render events (like [[onClientRender]]), or in fast processing logic, unless you want to kill performance.
	~~{{Important Note\|~~Using this function straight away on resource start might cause elements to not be passed properly, use [[setTimer]] in order to delay function execution and to avoid this issue.}}		* The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:
			* Using this function straight away on resource start might cause elements to not be passed properly, use [[setTimer]] in order to delay function execution and to avoid this issue.}}

	This function is used to call a function from another resource (which must be running).		This function is used to call a function from another resource (which must be running).

Srslyyyy: Add information about not using exports in render events

2024-11-22T17:10:19Z

Add information about not using exports in render events

← Older revision		Revision as of 17:10, 22 November 2024
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server client function}}		{{Server client function}}
	{{Note\|Calls may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource.}}		{{Important Note\|Calls (exports) may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource. Do not use exports in render events (like [[onClientRender]]), or in fast processing logic, unless you want to kill performance.}}
	{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}		{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}
	{{Important Note\|Using this function straight away on resource start might cause elements to not be passed properly, use [[setTimer]] in order to delay function execution and to avoid this issue.}}		{{Important Note\|Using this function straight away on resource start might cause elements to not be passed properly, use [[setTimer]] in order to delay function execution and to avoid this issue.}}

Srslyyyy at 15:25, 16 December 2023

2023-12-16T15:25:14Z

← Older revision		Revision as of 15:25, 16 December 2023
Line 3:		Line 3:
	{{Note\|Calls may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource.}}		{{Note\|Calls may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource.}}
	{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}		{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}
	{{Important Note\|Using this function straight away on resource start might cause elements to not be passed properly - use [[setTimer]] in order to delay function execution and to ~~fix~~ this issue.}}		{{Important Note\|Using this function straight away on resource start might cause elements to not be passed properly, use [[setTimer]] in order to delay function execution and to avoid this issue.}}

	This function is used to call a function from another resource (which must be running).		This function is used to call a function from another resource (which must be running).

Srslyyyy: Add note about elements not being passed properly.

2023-06-02T15:19:58Z

Add note about elements not being passed properly.

← Older revision		Revision as of 15:19, 2 June 2023
Line 3:		Line 3:
	{{Note\|Calls may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource.}}		{{Note\|Calls may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource.}}
	{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}		{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}
			{{Important Note\|Using this function straight away on resource start might cause elements to not be passed properly - use [[setTimer]] in order to delay function execution and to fix this issue.}}

	This function is used to call a function from another resource (which must be running).		This function is used to call a function from another resource (which must be running).

506: Coordinate

2022-02-08T15:13:10Z

Coordinate

← Older revision		Revision as of 15:13, 8 February 2022
Line 103:		Line 103:
	</syntaxhighlight>		</syntaxhighlight>
	</section>		</section>


	<section name="Server" class="server" show="true">		<section name="Server" class="server" show="true">

506: Better explaination of the first and second examples

2022-02-08T15:10:35Z

Better explaination of the first and second examples

← Older revision		Revision as of 15:10, 8 February 2022
Line 78:		Line 78:
	This extract shows adding of a "kills" column to the scoreboard resource. This then sets the ''gameShowKills'' variable to true(or false), telling the rest of the script to start outputting kills.		This extract shows adding of a "kills" column to the scoreboard resource. This then sets the ''gameShowKills'' variable to true(or false), telling the rest of the script to start outputting kills.

			'''Main Resource:'''
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function showKills ( option )		function showKills ( option )
Line 89:		Line 90:
	end		end
	gameShowKills = option		gameShowKills = option
			end
			</syntaxhighlight>
			'''scoreboard Resource:'''
			<syntaxhighlight lang="lua">
			function removeScoreboardColumn(columnName)
			-- What ever scripted ...
			end

			function addScoreboardColumn(columnName)
			-- What ever scripted ...
	end		end
	</syntaxhighlight>		</syntaxhighlight>
	</section>		</section>

	<section name="Server" class="server" show="~~false~~">		<section name="Server" class="server" show="true">
	This extract shows adding of a "kills" column to the scoreboard resource. This then sets the ''gameShowKills'' variable to true(or false), telling the rest of the script to start outputting kills.		This extract shows adding of a "kills" column to the scoreboard resource. This then sets the ''gameShowKills'' variable to true(or false), telling the rest of the script to start outputting kills.

			'''Main Resource:'''
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	function showKills ( option )		function showKills ( option )
Line 107:		Line 119:
	end		end
	gameShowKills = option		gameShowKills = option
			end
			</syntaxhighlight>
			'''scoreboard Resource:'''
			<syntaxhighlight lang="lua">
			function removeScoreboardColumn(columnName)
			-- What ever scripted ...
			end

			function addScoreboardColumn(columnName)
			-- What ever scripted ...
	end		end
	</syntaxhighlight>		</syntaxhighlight>

Botder at 23:25, 29 May 2019

2019-05-29T23:25:40Z

← Older revision		Revision as of 23:25, 29 May 2019
Line 57:		Line 57:
	==Syntax==		==Syntax==
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	exports.["resource_name"]:exportedFunction([ arguments... ])		exports["resource_name"]:exportedFunction([ arguments... ])
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">

Qaisjp: reword call note

2019-05-08T05:22:15Z

reword call note

← Older revision		Revision as of 05:22, 8 May 2019
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server client function}}		{{Server client function}}
	{{Note\|~~Call's~~ are ~~very slow due~~ to the ~~fact that every~~ resource ~~has it's own LuaVM~~}}		{{Note\|Calls may incur a performance overhead - they are not equivalent in performance to calling functions in the same resource.}}
	{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}		{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}

Pirulax at 11:37, 15 August 2018

2018-08-15T11:37:34Z

← Older revision		Revision as of 11:37, 15 August 2018
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server client function}}		{{Server client function}}
	{{Note\|~~Rewriting~~ the ~~original ''~~'~~call'''-function will disable call functionality within the scope (exports.: will also not work).~~}}		{{Note\|Call's are very slow due to the fact that every resource has it's own LuaVM}}
	{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}		{{Important Note\|The sourceResource and sourceResourceRoot "hidden" variables are available even if you use exports.:}}