Can remoteexec be used as a client on a server without admin rights?

[alleycat 28]

Can remoteexec be used as a client on a server without admin rights? For example. if I start a script:

"hello" remoteExec ["hint"]; 

will that broadcast on all clients it the script is run on a non-admin client?

[Guest]

Yes it will.

You need to have your description. ext setup in order to have your function working.

[barbolani 198]

or not even touching it, so everything is allowed :)

[alleycat 28]

This is the most useful script command since 2001

[Guest]

Ewww. BIS_fnc_MP did the same thing...

[MarkCode82 21]

Alright general guidelines to configuring your description.ext

first you'll need a class definition called

https://community.bistudio.com/wiki/CfgRemoteExec

in your description.ext to reference it seperately from the remoteExec class you create a subclass of

class functions { };

class commands { };

and the file named cfgRemoteExec.hpp

in the description.ext add in the class cfgRemoteExec {

#include "directorysomething\cfgRemoteExec.hpp"

};

 

Now all of these cfgRemoteExec is again much easier to manage from the cfgFunctions.hpp which is why if you want to use

the remoteExec feature easily, you pretty much "HAVE" to use cfgFUnctions.hpp for any advanced code otherwise you can leave them blank and define the following.

lass CfgRemoteExec
{        
       // List of script functions allowed to be sent from client via remoteExec
       class Functions
       {
               // State of remoteExec: 0-turned off, 1-turned on, taking whitelist into account, 2-turned on, however, ignoring whitelists (default because of backward compatibility)
               mode = 2;
               // Ability to send jip messages: 0-disabled, 1-enabled (default)
               jip = 1;
               /*your functions here*/
               class YourFunction1
               {
                      allowedTargets=0; // can target anyone (default)
                      jip = 0; // sending jip messages is disabled for this function (overrides settings in the Functions class)
               };
               class YourFunction2 { allowedTargets=1; }; // can target only clients
               class YourFunction3 { allowedTargets=2; }; // can target only the server
       };        
       // List of script commands allowed to be sent from client via remoteExec
       class Commands
       {
              /*your commands here*/
              class hint { allowedTargets=1; jip=0; } /# 
              0: can target all machines (default)
              1: can target only clients, execution on server is denied
              2: can target only server, execution on clients is denied
              #/
	};
};

<params> remoteExec [<function>,(<target>,<isPersistent>)]; // This 

<params> remoteExecCall [<function>,(<target>,<isPersistent>)]; //This can be used but your command must execute quickly without backlogging.

so for your command you'd do,

"hello" remoteExec ["hint",player,1]; // the number 1 at the end enables or disables JIP messaging (Joining In progress)

That should allow you to do what you requested

MarkCode82 signing off.