remoteExec – Talk
Jump to navigation
Jump to search
m (Added my name) |
|||
| Line 3: | Line 3: | ||
In my humble opinion, it would be senseful to call this command "remoteExec'''Spawn'''" since the other one is "remoteExec'''Call'''" and it would be clearer to the user that this command is actually spawning the remotely executed code. --Johnny | In my humble opinion, it would be senseful to call this command "remoteExec'''Spawn'''" since the other one is "remoteExec'''Call'''" and it would be clearer to the user that this command is actually spawning the remotely executed code. --Johnny | ||
== Question == | |||
[_unit, "sendSideChat works"] remoteExec ["sideChat", _owner, false]; | |||
I receive: | |||
"''Scripting function 'bis_fnc_execvm' is not allowed to be remotely executed.''" | |||
I understand that bis_fnc_execvm should not be whitelisted. Any solutions? | |||
Revision as of 04:06, 3 October 2019
Naming comventions
In my humble opinion, it would be senseful to call this command "remoteExecSpawn" since the other one is "remoteExecCall" and it would be clearer to the user that this command is actually spawning the remotely executed code. --Johnny
Question
[_unit, "sendSideChat works"] remoteExec ["sideChat", _owner, false]; I receive: "Scripting function 'bis_fnc_execvm' is not allowed to be remotely executed." I understand that bis_fnc_execvm should not be whitelisted. Any solutions?