So I'm working on making mission on CLAfghan where instead of a traditional Assymetric Insurgency, I want to make the playable force a Spec Ops team that receives C2ISTAR generated tasks (but also requires to player to do typical Assymetric prevention stuff along the way). But I'm noticing that the entire C2ISTAR system seems really buggy and I'm wondering if there's any realistic way to mitigate that.
1. With auto tasking enabled, without question the first set of tasks never shows up on my map. The tasks themselves generate, but since there are no markers there's obviously no way for me to accept the mission. Also, there's no "set task" option for these initial missions in the "Task" menu. This means I always need to delete the initial tasks and request a new one (then everything seems to work).
2. Two tasks always generate on mission start but they are always identical, except with different phrases being used. Is that intended? And one of them is always not allowed to be deleted.
3. Is there any way within the mod files to restrict which kind of missions get generated?
4. In the future, could we get the option to blacklist map areas where tasks can be generated? If auto tasks generate within the enemy's mil/civ obj blacklisted area, the mission will spawn but no enemies will.
I love the idea of C2ISTAR and when it works it's an INCREDIBLE change of pace from basic patrolling. But, it's sort of buggy and not something I think I can commit to unless I can figure out some workarounds for this stuff. Any help or insight would be GREATLY appreciated.