Talk:CallServerFunction

I would rather use this variant for both calling client and server functions..

[lua]
-- client side
addEvent("onServerRequest", true)
addEventHandler("onServerRequest", rootElement,
	function (funcname, ...)
		 _G[funcname](...)
	end
)
-- server side
addEvent("onClientRequest", true)
addEventHandler("onClientRequest", rootElement,
	function (funcname, ...)
		 _G[funcname](...)
	end
)
-- @see down below for this
--and call them like
--	triggerServerEvent("onClientRequest", rootElement, "changeResStateS", resource, state)
-- while I have defined a function changeResStateS(resource, state) end on server side and vice versa.

LordAzamath 19:47, 14 May 2009 (CEST)

---

Yeah, nice idea to save some space except for the trigger-Event solution. CallClient/ServerFunction should enshorten this. NeonBlack 20:23, 15 May 2009 (CEST)
By the way: I think the yellow note isn't needed since there is no way hacking mta to call some function. To get the possibility for calling functions the scripter needs adding this possibility manually. So this note would be just as well be added to banPlayer. NeonBlack 20:37, 15 May 2009 (CEST)

• The yellow box is needed. If, for example this is added to the Admin resource (which has full admin access) then any resource could trigger this event and have full admin rights.

In that case the triggerEvent part should be replaced with

[lua]
function callServerFunction(functionName, ...)
	return triggerServerEvent("onClientRequest", rootElement, functionName, ...)
end
-- and
function callClientFunction( player, functionName, ...)
        if getElementType(player) = "player" then
		return triggerClientEvent(player, "onClientRequest", rootElement, functionName, ...)
	else -- while here player will actually be the function name and functionName the first argument given actually
		return triggerClientEvent("onClientRequest", rootElement, player, functionName, ...)
	end
end

LordAzamath 08:20, 16 May 2009 (CEST)