Jump to content
Sign in to follow this  
tinter

cfgRemoteExecCommands, Why?

Recommended Posts

When Bohemia implemented the changes to bis_fnc_mp to allow for execution of commands and not just functions, why did they decide to only allow certain commands?

I don't really see what this accomplishes as any command can already be run using the bis_fnc_spawn function, just in a more roundabout way. Allowing certain commands only leads to complicate scripting for multiplayer where in some situations you want to run only 1 command on a machine but you have to either use bis_fnc_spawn or define a function to then use. Being able to allow commands is nice, but there's no easy way to allow all the commands currently allowed and then another one.

Personally I see no reason to have this.

Share this post


Link to post
Share on other sites

How is it a security concern? If you have access to bis_fnc_mp then the fact that spawn isn't allowed isn't gonna stop you from just using the function.

Share this post


Link to post
Share on other sites

Imagine this example:

//BE createvehicle.txt

5 B_quadbike_F

// kiddie injection

[['B_quadbike_F',position player,[],0,'NONE'],"createVehicle",TRUE,FALSE] call BIS_fnc_MP;

Share this post


Link to post
Share on other sites

Yeah and that can still be done using bis_fnc_spawn like this:

[{createVehicle ['B_quadbike_01_F',position player,[],0,'NONE']},"bis_fnc_spawn",TRUE,FALSE] call BIS_fnc_MP;

Share this post


Link to post
Share on other sites

Does anyone know why this is in place? It seems like BIS should just remove it, honestly.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×