Jump to content
beno_83au

[Release] Remote Detonator Function

Recommended Posts

Hello, as part of a campaign I've been making for some mates and I, I'd made a scenario involving a small defensive engagement and wanted to give each player the ability to detonate claymores that were laid out in front of the position. The idea was to do something similar to having a firing device linked to a claymore, that anyone could activate. But with the lack of an M57 (firing device) I went for a tablet that was linked to a number of claymores. Anyway, someone saw a short video I did demonstrating it and asked if they could use it, so I turned it from a bodgey, mission specific thing into something easy to use in any mission.

 

Download:

MIL_remoteDet - Dropbox / Armaholic

 

 

Description:

Uses addActions on an editor placed "firing device" to detonate editor placed mines.

 

Features:

- SP/MP

- Detonate mines using an object (firing device) via addActions.

- Have multiple mines linked to the firing device.

- Customise addAction menu description of mines.

- Can be used by multiple players.

- Group (text) chat and vanilla sounds to indicate arming, firing and disarming.

 

To use:

- Copy the folder MIL_remoteDet to your mission folder.

- Place an object to interact with as the clacker/firing device and name it.

- Place and name claymore/s.

- Run this command anywhere (e.g. initServer.sqf) before the mission starts:

nul = [] execVM "MIL_remoteDet\init.sqf";

- To create the addActions, run this command where the mines are local (e.g. server for editor placed firing device and mines):

[_firingDevice,[[_mineDescription,_mineName],[_mineDescription,_mineName]]] remoteExec ["MIL_fnc_remoteDet",_players];

    _firingDevice - object - name given to your firing device.
    _mineDescription - string - description of which claymore to fire (e.g Fire Claymore - _mineDescription).
    _mineName - object - name given to _mineDescription claymore.
    _players - array - list of all players to be using the firing device.

 

Example:

waitUntil {!isNil "MIL_fnc_remoteDet"};
nul = [
	clacker,
	[["Near Left",mine1],["Near Right",mine2],["Far Left",mine3],["Far Right",mine4]]
] remoteExec ["MIL_fnc_remoteDet",call BIS_fnc_listPlayers];

 

Demo (23s):

 

 

If anyone finds any problems please let me know. I threw this together fairly quickly over the weekend but I managed to have it working fine when I tested everything this morning.

 

Thank you.

  • Like 3

Share this post


Link to post
Share on other sites
On 6/19/2017 at 8:13 AM, beno_83au said:

waitUntil {!isNil "MIL_fnc_remoteDet"}; nul = [ clacker, [["Near Left",mine1],["Near Right",mine2],["Far Left",mine3],["Far Right",mine4]] ] remoteExec ["MIL_fnc_remoteDet",call BIS_fnc_listPlayers];

Nice work.  Smart to parameterize the name of each mine, so mission designer can name them in whatever way fits the mission best.

  • Like 1

Share this post


Link to post
Share on other sites
39 minutes ago, johnnyboy said:

Nice work.  Smart to parameterize the name of each mine, so mission designer can name them in whatever way fits the mission best.

Thanks. @natoed saw the original and wanted to be able to use it, so i had to get off my arse and do it properly :rthumb:

  • Like 2

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

×