In PWS .Good work Friznit. Congratulations

Perfect timing, I just uploaded a mission to my server last night for testing and release for the weekend.
Now I can pull out the intel scripts tonight, replace all my modules and still be ready to go.

Yeah, I saw the FB post earlier, was waiting for it to hit. At least I managed to get on my server and do a Server Save before the auto-update hit.

I had never seen the map Saint Kapaulio before. good to see that it is indexed. I think I have a new playground :D Maybe some Abu Sayyaf rebels in Phillipines? Maybe PLA Invasion of S. Chine Sea?

I'm going to have to play with it some :D

Wow yeah I hadn't seen Saint Kapaulio either. That looks great! I think that might have to be my groups next deployment after we insert freedom into Takistan

Yes! been waiting for this, thank you ALiVE team! :)

Nice ALiVE team!

Looking forward to test the new version. Damn shame won't be able to do that already today but only 20h from here. Eeh well, will have more time then any way :)

Does intel work in asymmetric warfare? How do i activate it or is it automatically on.

Also what does this mean in the changelog?
"ALiVE_PLACEMENT_CUSTOM_GROUPBLACKLIST"
Can i blacklist a certain group in a faction? Ie the 8 man groups in leights opfor insurgents?
Please say yes and tell me how to do it :)

Thanks will try later :)
Do you know what that changelog means that I posted above spyder?

So after quickly reading through that am i right in thinking as a way to spawn smaller groups i can blacklist a whole group, say the 8-10 man groups for LOP_AM.
Im trying to have the smaller 2-4 man available groups of insurgents running around.
Thanks

I had mine set to often last night and was teleporting around the map "testing" Massi's taliban in Kunduz. I never saw any intel as such, even with it set at often and eventually I ran out of targets. Am I looking for cellphones/documents or something else?

I did see a red dot map marker pop up at one stage showing an IED location but I don't know if that was just because I had debugging on or not.

I also ran into this error message but only once.