grubes

Thanks for the tip! Works perfectly. Still *slightly* disappointed in the need for the workaround, but I'll take what I can get

When enabling only @cba_a3 and @CAF, all Independent soldier classes are overwritten and have absolutely no EventHandlers populated. This means that no XEH code will run on any Independent units. Not even sure how or why this would happen since CAF doesn't add any INDFOR units. Please help? Is it possible to get this fixed? If not, is the CAF source code available to fork so we can fix it ourselves? Is CAF even still under development? Is anyone out there paying attention to this?

Would it be possible to add support for extended event handlers? I see in CAF_AG_AFR_P_Base you've overridden the Init event handler to call the Random.sqf script. Is it possible to just add the call to fire the SLX init function after the randomize script? Then your init handler would look something like: (_this select 0) execVM "\caf_ag_factions\africa\pirates\Random.sqf _this call SLX_XEH_EH_Init; I'm working on a script that utilizes XEH to call functions during unit init, and because the XEH call is omitted, none of it works for CAF units.

I realize this was forever ago, but did you ever resolve this? Trying to build my first module and having the exact same problem. I'm looking at the ACE and TFAR repos on GitHub, and it looks to me like I have exactly the same setup - no dice, though.

If you, as a player, observe an enemy move behind a tree or bush or rock, what do you do? Do you forget about them and stop firing? No; you suppress the hell out of the tree or bush or rock so that supporting units can close and destroy, even if you can't actually SEE the enemy. Can we please stop being mad at the AI for doing exactly what we would do?

Cheers!

Glad it's helping! I've only got the one more topic (performance/optimization) at the moment, so I'd be interested in hearing what you guys would like to read about next.

Just added the latest installment of the series: Troubleshooting Enjoy!

Sorry this thread has been quiet for awhile. I've been stopped up at work a bit. I plan on finishing the Troubleshooting section this weekend. This will include screenshots and explanations of what each module's Debug setting does, among other things. Also to make it easier for readers to figure out where they are and what's next in the tutorial, every post now contains a Table of Contents section that has a link to every other article in the series as well as an indication of where you currently are. Enjoy!

Added the Playable Forces tutorial: https://medium.com/the-creation-of-alive-uprising/alive-uprising-playable-forces-6dcd14b54b61

Added the Attacking force tutorial. Super short and simple.

I've also started a Github repo where you can follow the development and download the latest versions of Uprising. Note that there are no complete official releases yet, I am still building it as I'm writing the articles.

I've added the Asymmetrical portion of the tutorial: https://medium.com/the-creation-of-alive-uprising/alive-uprising-creating-an-asymmetrical-force-71a8ba606c2e There are the most unknowns here as I didn't get things to work as they are documented, but still I was able to get a really fun scenario brewing. Can't wait to add in some nice touches for the playable units.

Link away! I appreciate it; I wrote it so I could share it! I've already added the Civilian Population article this week. I'll be writing up the Asymmetric Warfare side this weekend for those of you interested (SPOILER ALERT: it's actually extremely simple, but you have to be really patient to see it in action). Appreciate any feedback you've got; let me know how I can improve the work. I've also decided to add a section specifically about what the Debug switch does for each of the modules involved so other mission makers get familiar with how to read all of the symbols. ---------- Post added at 06:28 ---------- Previous post was at 05:56 ---------- The right syntax for what you are trying would be but I don't think that is actually the fix you want. That will make it only run on the server. I'm extremely rusty on my multiplayer scripting, but I'll see if I can work something up if no one else gets you an answer soon.

I've updated my Linux server install tutorial with all of the latest changes. I've added new links, removed outdated commands/settings, and added some new steps. Find it here: https://medium.com/arma-3-server-administration/installation-and-configuration-of-an-arma-3-linux-dedicated-server-7875c9030b7 I repeated all of my steps on Ubuntu 14.04 and installed CBA as a test, and I am now connected and mucking around successfully inside the server. Let me know if you have thoughts on how I can improve the instructions.