Okay, for anyone reading this now, the issue was an error in the instructions of setting up the mod (my bad) - the latest GitHub version has corrected that. Thanks again @ski2060!

Thanks! I'll take a look in more detail tomorrow but it looks like the functions aren't being defined correctly. This could happen if they have already defined a cfgFunctions in the description.ext file before adding my script or have incorrectly added the undercover script files. In which case, can you ask them to verify their description.ext files are set up correctly? Or even paste them here and I'll troubleshoot?

I'm more than happy to give them a hand setting it up if you want to PM me their missions.

If you can post an example of their missions that would really help too. I have a working PC nearby for the time being and I'd be fascinated to see where / if they are going wrong. All I've heard so far is issues from people who haven't got it working (and not a single bloody debug report to determine what the issue is). In fact, yours might well be the first hint that anybody other than me has it working fine in any mission whatsoever! Which is pretty weird considering how much I tested it and how reliably it has been working for me so far. I guess this is the issue with not being in a unit as a modder though!

Could you post your debug feedback and I can hopefully tell you what is wrong (enable debug in the settings and let me know what it says on screen)? I could make a sample mission but I'm away from my Arma computer for a while.

The playable character needs to be the true side of the undercover unit. So if you are fighting for Blufor, the unit needs to be Blufor.

Hi guys, apologies for the delay in responding - been away a fair bit recently.

@ski2060 There's a variable in there which you can tweak but it's a little bit fiddly as I haven't got it in the settings just yet. Basically, in the /func/ folder, you'll find a file called fn_undercoverTrespassRadiusLoop.sqf. Open that up and on line 3 you'll see this:

params [["_undercoverUnit",player],["_regEnySide",east],["_asymEnySide",independent],["_radius1",15],["_radius2",25],["_radius3",60],["_radius4",150]];

_radius1 is the radius in meters that regular troops will detect you if they can see you.
_radius2 is the radius in meters that asymmetric forces will detect you if they can see you.

So if you want to change the radius for regular forces to 25 from 15, you could use ["_radius1",25] instead of ["_radius1",15].

Does that make sense? I'll add a ticket on GitHub so I remember to add in a parameter in the settings.

@GhostOne It will never work with civilian editor-placed units. They have to be a side that is recognised as an enemy to whichever side you are fighting. Change the clothes to civilian ones in the editor by all means, but use Blufor, Ind or Opfor units as your undercover guys.

As for it not working, the chances are your guy is wearing something prohibited (like Night Vision Goggles or a naughty backpack). Enable debug mode in the settings and let me know what it says if you could? Also, a paste of your settings file and your unit load out wouldn't go amiss if the issue is what I think it is.

I wouldn't worry about it, Arma is a beast! Pretty hard to understand all of it. I still have no idea how most launchers work. And as for engaging targets form the air... no clue. But yeah, as long as you have batteries in your designator, a single left click will activate the laser and show the laser dot in night vision and a little red icon at the top of the display.

Haha yeah I forgot about that! Maybe I should mention that in the description. I thought it always added batteries no?

No cancel that - there is an on-screen indicator when you are lasing a target using vanilla! Sorry, got confused. It's a little red laser icon at the top. Point that at whatever you want to kill and follow the prompts. There's a video now up on the release page that should go through roughly what you have to do. Let me know if you have any questions dude!

Thanks, great work!