HETMAN - Artificial Commander

[Rydygier 1317]

HAC 1.47 released.

 

HAC 1.47 (Dropbox)

INTRODUCTION

The addon â€HAC†is intended to enliven the battlefield in the same way that having a human leader would do. HAC does not deal with the manner in which orders are executed (unit level), but deals with the issuing of orders. In other words, this addon gives one or both sides of a conflict a field-commander level AI.

One of most important goals of this addon is to keep high compatibility level with other addons, in particular those that extend the possibilities of AI for units and groups. HAC control is mostly based on issuing waypoints, and as far as possible HAC avoids interfering with low-level AI. In other words, HAC focuses on giving orders, rather than on the way in which orders will be executed.

HAC gives new, higher level AI, rather than changing the existing AI. There are only a very few exceptions to this rule. HAC should therefore enrich the gaming experience with new features, without conflicts with other addons. HAC is intended to complement their effects rather than to compete with them for control over units (at least for those addons that do not mess with waypoints).

HAC can serve as an instant battle generator as well as a general player opponent, or as base for complex missions and/or gameplay modes.

1.4 and above versions needs OA (CO) 1.62 or higher.

Addon version requires Community Base Addons.

-----

USAGE

To activate HAC for one side, one of the units of that side must be named LeaderHQ. Essential also is the placement on the map of any object (for example, an empty trigger) named RydHQ_Obj1. The location is entirely your choice. Its position will designate a target point which the Artificial Commander will try to conquer at first (for example, a spot near the leader of the opposing side).

Analogously, there should be placed in freely chosen areas (eg in cities, strategic positions or simply nearby opposite Leader) three other objectives (RydHQ_Obj2, RydHQ_Obj3, RydHQ_Obj4), which will be conquered in numerical order. If the mission designer wants less than four objectives, then simply place the unneeded objectives at same position as the ultimate objective.

For the script version only, to initialize HAC the following code should also be executed in some way, e.g., by placing the following script in the init field of any object (for example, in the activation field of an empty trigger or waypoint):

nul = [] execVM "RydHQInit.sqf";

Alternatively, that line may be placed at the end of a mission's init.sqf. Init.sqf is recommended place for init config variables (beacuse of better readability), especially for bigger configs, eg containing RHQ arrays.

For MP client-side compatibility (script is run only on server, but client-side players should have visible tasks assignd by Leader) needed is always function module on map, and, for BB only, RydHQ_MC trigger (customized battlefield area).

See included manual for all details, and there is lots of them.

-----

RHQ CONFIGS THREAD

For easy copy&paste at once all RHQ array sets with class names of new units. Use RHQ array as any other HAC's init config variable. Best: paste needed RHQ as is into init.sqf file (before nul = [] execVM "RydHQInit.sqf"; line, if HAC script version is used, same as for any other init config). Note, that for big arrays as RHQ can be, good practice is additional syntax check. Errors do happen.

-----

ONLINE MANUAL

Online manual for users, where anybody can leave own comments, notes, ideas and corrections visible to all other.

-----

ALTERNATIVE SOUND SETS FOR RADIO CHATTER

SoundSets (4)

-----

HETMAN FOR ARMA 3 PROJECT

Led by: zorrobyte (Thanks! 🙂 )

"My ultimate goal is to simply get working as much as the A2 code possible in A3 while providing bug reports and documentation along the way to help development of official version."

Repository

Contact for interested:

Skype: ross.fisher91

Forum

-----

TO DO (closed for new ideas - HAC enters maintenance stage)

 

- fix problems with Recon air usage (shouldn't be treated as recon reserve);

- fix problems with assigning empty vehicles;

- fix limited control mode by TL's naming;

- improve capturing;

- add more demos for latest features;

- battle radio ambient chatter.

- mechanized groups return into APC after the recon mission (other missions too);

- to fix: HAC's tasks overwrite pre-made briefing tasks;

- a way to exclude chosen empty vehicle from cargo usage;

- debug/comm active for MP dedicated (experimental);

- Ammo chute drops from special chosen air support units;

- new sniper mission behavior;

- SpecFor category with own mission kind to eliminate most valuable enemy or guard own HQ if idle or chosen by user for it;

- Optional invisible LZ helipad for cargo choppers to help them not crash in difficult terrain;

- Include optional RHQ arrays for OA, BAF, PMC and ACR that can be used with single boolean variable;

- improved capturing objectives handling, that will speed up conquering objectives;

- customizable main BB cycle interval;

- "CargoOnly" and "NoCargo" arrays;

- optional repositioning for air units, that's landing became too far from current leader's position - can be useful for BB on big maps to keep air support close of whole army;

- improved defense reinforcements behavior;

- optional "dynamic formation" feature, that changes on the fly group's formation and behavior if in possible danger (experimental).

- optional simplified BB debug - movement arrows and markings for current/past firefights (?); dynamic markings, that will show real BB's divisions movement as a whole with arrows, and spotted enemy concentrations/fights with special markers (BETA)

- weather & daytime factors impact on issuing CAS, arty, recon orders... (?);

- optional "attractors" to have control, where should concentrate idle and exhausted;

- optional time manipulating and pause before new order for human player.

- invisible helipads for air cargo (?);

- to correct morale calculation when new group is included;

- fix some issues with CFF execution that occurs in certain circumstancies;

- surface check for idle patrol waypoints.

- incorporation of modernized FAW script for full internal AI arty handling (?);

- distance factor in risk calculations for AA and AT;

- further development of infantry waypoint level path finding;

- to correct influence of recon/FO/sniper units on garrisoned group behavior;

- to enhance reserve activity;

- enhance manual content;

- better attack coordination (?); (experimental - implemented, but not quite reliable, may cause problems. Disabled by default. Used variable shared for all Leaders: RydHQ_SynchroAttack = (true/false));

- improve Leader's relocating, so he will not continue march towards objective, if objective was rapidly lost (currently checked every reset) (?);

- allow the Leader's group to do more "stuff", as garrisoning(?); (I do not know, what reasonable this would be);

- add flare/smoke grenades handling also for OPFOR weaponry;

- investigate and eliminate cause of sometimes spotted doubled orders for human controlled TL;

- fix issues with "custom objectives only" mode;

- custom map center point and area (?) - (used RydBB_MC - this may be global init variable that contain coordinates of custom map center (then another variable, number, RydBB_MapLng, contains width of the square area) or name of a trigger. In this case width will be equal to trigger's width. Width should be in both cases divisible by 500). This can be useful for quickening of BB initialization, when not whole map will be used (eg to exclude water). If not used - whole map will be sectorized;

- morale report on screen for debug mode.

- HAC should not take control over formations, smoke usage and vehicle engine for groups led by human controlled units. (following wasn't HAC issue) Engines shouldn't be turned off for planes in air (probably cause: HAC issuing idle order for air groups while shouldn't?);

- adding RydHQ_Smoke variable to manual content;

- RHQs arrays for subtraction default classnames from given category;

- to fix disembarking crew issue for grouped cargo vehicles;

- to fix rev.sqf code;

- to fix "blindness issue" (?); (for 90% not HAC issue, same problem without HAC for newest OA patch found described on forum...

- cyclical comparing forces routine during fight and withdrawning when to big enemy advantage (?);

- big boss;

- to make speed of groups movement adjustable;

- new manual content (internal variables documantation);

- to make "idle" orders optional;Added new config variable: RydHQ_IdleOrd; if true (default) idle orders will be issued, otherwise reserve units will do nothing

- better defensive bahaviour - usage of objectives as perimeters centers;

- to exclude infantry manning static weaponry from taking orders;

- HAC should take into account assigned to group vehicle even, if all group is outside, when categorizing groups;(now assigned vehicle is checked, but learned, that editor placed mechanized group's (eg USMC inf with AAV) units, except crew, aren't assigned to group's vehicle until get in, then are assigned even, if later will get out back)

- civilians friendly to opponent shouldn't be considered as known enemy unit; (ignored as enemies and allies are now by default "CIV","CIV_RU","BIS_TK_CIV","BIS_CIV_special" factions, but this list, holded by RydHQ_CivF config array may be changed by manipulating with the content of this variable (ignored will be default factions, OR only included in this config array, if defined - defined Array will be repacement, not suplement for default list), so user can set any list of ignored by Leader of given side factions ("ignored", means that Leader of this side will not take into account the existence of units of listed in this array faction in his decisions, however, of course, if units of this Leader will encounter units of "ignored" faction, still will act accordingly to realtions between both factions);

- captives should be ignored;

- rebalance for morale calculations;(new formula, now morale will slowly grow with time. Is also more important - implemented system of flee/panic due to low morale. Chance for panic is very low, but the more groups "in panic" and the lower is morale, the more chance for panic to others. Panic group will loose all waypoints and is unavailable for HAC. Also will have greatest possible fleeing parameter. There is very small chance to calm down for panicked unit, all this is tested every cycle. Not panicked group also may flee from battle if morale is low enough and casaulties high enough. New config variable, RydHQ_Muu (don't ask...), by default equal to 1, may be used to manually change of "determination" of given side. This is multiplier of allowFleeing parameter. This parameter is randomized in dependency of army morale. Set to 0 will make side's groups totally invulnerable on morale drop. Regardless of multiplier's value, value of this parameter will be never bigger than 1)

- new overall army behavior - chance for flee in panic, when morale is broken (instead of surrender?), chance for fleeing dependant on morale and on some feedback loop (more groups in panic/fleeing means more chance for panic/fleeing for each other); see above, optional, may be turned off and on by variable RydHQ_Flee, default set as "true";

- scripted help for withdrawal and air cargo transport by temporary allowFleeing or courage skill manipulating?;

- repair&improve or removal of surrendering functionality;

- more complex situational judgement, when AA and AT enemy weapons should be ignored and aerial/armor units sent regardless of presence of such weaponry on map (out of range and desperate situations - enemy close to Leader's position perhaps). Currently "desperate situations" implemented. If too many known enemies are closer than allies to Leader's unit, and if average distance is small enough, and when any enemy is very close to Leader, Reclessness attribute of Leader temporary and rapidly increases, so there is big chance for orders, that in other circumstancies would be considered by HAC too risky;

- optional flare usage;

- integrated artillery handling (proper usage of HE, smoke and illum) (?);

- morale drop when current leader unit dies (?);

- additional pause before next cycle, if new leader is replacing killed previous;

- distinction between aerial and land support vehicles for choosing apriopriate kind depending on distance and terrain;

- to add optional hint info about Leader's staff death (when HAC's control ends);

- try to make bombers drop bomb via lasertarget method;

- operational, but empty (without crew) enemy vehicle shouldn't be counted as enemy when status of objective is checked;

- fix syntax error in "combining groups" routine (wip4);

- fix addon version from earlier wips (wip4).

-----

SAMPLE MISSIONS

Created any kind of mission utilizes Hetman? Let me know, so I could link it here.

LAST TRUCK

Kind: SP

Map: Chernarus

Required game version: A2 CO 1.62

Addons needed: none

Addons recommended: JSRS

Estimated play time: 10-30 minutes

Author: Rydygier

Description:

 

Short mission. You are a MTVR truck driver. Your task is to evacuate Gorka village before OPFOR break our defenses. Civilians to rescue is more, than room in your truck. Time is short and valuable - bought with currency of blood by defending soldiers of B company, known also as Black Company. Enemy is overwhelming and constantly pushes forward. It is only up to you, if you risk own life and return for more people once again, or not. The only judge of that decision would be your conscience. Number of saved civilians is the only important mission factor. Doesn't matter, if you survive. Read the briefing for more details.

When off the truck, you have two custom actions available: gather nearby people, to make near civilians board your truck (present as long there is empty cargo space in yours vehicle), and disembark to unload passangers - do it inside marked LZ area to complete their evacuation.

Civilians are controlled by some exprimental code, that gives them independence and situation awareness, some may refuse follow your call (may help, if you wait with another call, until all currently called are boarded), some, if in panic, may run. There are also old, slow moving persons, that will slow down the process. Truck can hold up to 12 civilians. Save as many, as you can.

Do not leave mission area.

Battle raging on the south is controlled by HAC, so it is fully dynamic.

To finish the mission enter small red circle marked as "end mission" area. After that, or if you die, there will be no typical debriefing. Instead, thanks to another experimental piece of code, you can spectate further evacuation process and/or interesting spots of the whole battlefield chosen dynamically by the camera, as long, as you wish. To end - use "esc" menu.

-----

MY THANKS

 

For HAC in MSO module: Tupolov, Wollfy.au, friznit2 and anyone else involved.

For HAC in demo of HC extensions addon: DomZ;

For HAC in COWarMod: Günter Severloh;

For HAC in EBSS: subroc;

For help with kbTell code: gammadust.

For mirrors: Foxhound, Old Bear.

For video tutorial: Hobbesy.

For language corrections: Orcinus and Lucidity.

For voice acting: DuddBudda, SiC_Disaster, nettrucker;

For testing, bug hunting, many good ideas, RHQs and advices: Katipo66, Mjolnir66, DaveP, Mikey74, Kremator, andersson, SAbre4809, Humvee28, Taro8, SteveA360, Georilla, Igneous01, mankyle, Mr_Centipede, subroc, stupidwhitekid75, Orcinus, Hobbesy, lecholas, friznit2, gammadust, fabrizio_T, _William, Wollfy.au, RAINF, Fenrisulven, CaptainBravo, Snafu, XALIENAx, TeilX, Astrosammy, gunterlund21, Jingle, DomZ, kelzekyr, Lucidity, meltedping, Anthropoid, DeclaredEvol, tank000, SavageCDN, zemanel, EvilMooseofDoom, ACE1434, la_Vieille, jiltedjock, Odyseus, THEBLITZ6794, InstaGoat, kutya, Sixt, ssechaud, metalcraze.

For motivation and interest: All above mentioned and: stubs, thearies, Munger, KeyCat, Neopas, zwobot, colosso, froggyluv, postman84, dcal, Big Morgan, and to all, I forgot (sorry, if so).

-----

Earlier versions:

 

HAC 1.43 (Zippyshare)

HAC 1.33 (Zippyshare)

HAC 1.3 (Zippyshare)

HAC 1.21 (Zippyshare)

HAC 1.2hotfix (Zippyshare)

HAC 1.2 beta2 (Zippyshare)

HAC 1.2 beta (Zippyshare)

HAC 1.1 (Armaholic)

HAC 1.1 (Armed Assault Info)

HAC 1.1 (Zippyshare)

HAC 1.1 alpha 4 (demo mission)

HAC 1.1 alpha 3.1

HAC 1.1 alpha 2

HAC 1.1 alpha 1

HAC v. 1.0 beta2 (multiupload)

HAC v. 1.0 beta (multiupload)

Addon was created "by player for players", source scripts you can freely modify, copy, "cannibalize", to use in your projects. It is released under APL-SA license. I'll be grateful for notification about each such usage.

I will be grateful for bug reports.

Enjoy being under control.

Rydygier

[katipo66 94]

This sounds great, gonna try it out.

Edit* Hey Rydygier, i gave it a quick spin before work, this is really great, i always wanted to be able to place what ever units i wanted on a map and let them sort them selves out, and i think this does just that, does the leaderHQ join the battle? maybe need to hide them away somewhere.

I havent tested a lot but what i did see looked fkn awesome!

Edited December 21, 2011 by Katipo66

[Rydygier 1317]

I'm glad you like it, Katipo66. LeaderHQ will hold its position if is AI-controlled (script assigns him a waypoint "hold" on his position). Yes, you better hide him somewhere behind and keep well guarded. :)

[kremator 1065]

What a great idea ! Will give this a go right now :)

[katipo66 94]

I'm glad you like it, Katipo66. LeaderHQ will hold its position if is AI-controlled (script assigns him a waypoint "hold" on his position). Yes, you better hide him somewhere behind and keep well guarded. :)

Yeah, great gameplay options for player just in that.

Just a couple more questions, sorry bro... ive only skimmed through the PDF, if the answers are their no prob, i check it later.

- If RydHQ_Obj is moved during a game, would that have any influence on leaderHQ?

- and i think that RydHQ_Obj has no influence on leaderHQB?

- would either leader recognize and use spawned or respawned units

there is a good chance, that Artificial Commander will not send to attack armored units, if he knows about presence of enemy anti-tank weapons (such as ATGM units). Similarly rather not send air units in the area in which presence of AA weapons was found...

This sounds like great stuff and something sorely missing from Arma, nice work :ok:

[Rydygier 1317]

Yeah, great gameplay options for player just in that.

- If RydHQ_Obj is moved during a game, would that have any influence on leaderHQ?

Addon itself does not change position of "RydHQ_Obj" but mission maker can do it via script (and it may be mobile object). Addon will "notice" this change and take it into account with next cycle.

- and i think that RydHQ_Obj has no influence on leaderHQB?

Yes, leaderHQB knows nothing about "RydHQ_Obj". His interest in his own objective - object named "RydHQB_Obj".

- would either leader recognize and use spawned or respawned units

Yes, units that appear on the map during the game will be taken into consideration during next cycle.

This sounds like great stuff and something sorely missing from Arma, nice work :ok:

EDIT: It should be noted that because almost every team has infantry anti-tank weapons, tanks will be sent with care. I hope that not too carefully. I really wanted to do something like that for Arma. Ambitions nearly outgrown me, code is not perfect and certainly not optimal, but it does its job. I'm also going to use it often.

Edited December 21, 2011 by Rydygier

[Guest]

Thanks for taking the time to inform us of your release :cool:

Release frontpaged on the Armaholic homepage.

HETMAN - Artificial Commander v1.0 beta



Community Base Addons

[katipo66 94]

EDIT: It should be noted that because almost every team has infantry anti-tank weapons, tanks will be sent with care. I hope that not too carefully....

Too carefully is great im thinking, because theres dynamic sub missions etc for the player, for example if the commander will not send armour into an area until AT is cleared, maybe if that was broadcast to the player somehow.

I really wanted to do something like that for Arma. Ambitions nearly outgrown me, code is not perfect and certainly not optimal, but it does its job. I'm also going to use it often.

...Nearly, but not yet :D

[mjolnir66 48]

This is incredable. I throw down some units, add in a couple of lines of code, an objective, and I have an awesome mission with an intelligent enemy all ready. And the differences between the AIs are pretty good too. I hope it works in MP too. The it would be a quick and easy to use dynamic enemy for Coop.

[Rydygier 1317]

Thanks a lot, Foxhound!

I hope it works in MP too. The it would be a quick and easy to use dynamic enemy for Coop.

I wish I could say that it works in MP, but I can not. I know not enough to design scripts to make them work in MP. You can try, but I have no idea whether the addon will work in multiplayer. Even if one day I will know the ins and outs of this knowledge, I have virtually no possibility of testing scripts in MP. Sorry. For patient and ambitious remains possibility of adapting scripts on their own, but it's in total several thousands lines of code.

---------- Post added at 23:43 ---------- Previous post was at 23:35 ----------

Too carefully is great im thinking, because theres dynamic sub missions etc for the player, for example if the commander will not send armour into an area until AT is cleared

I think addon creates many interesting possibilities. Beginning with mission "the hunt for an enemy commander." I am counting on unlimited imagination of Arma maniacs. :)

[mikey74 187]

LOL Im so glad you did this. Its something I've played around with sense Ive been using high command. Becuase I lack alot of scripting knowledge Ive been opting out with DAC. Which is also AWESOME.lol Now Ive kinda sorta combined them in missions. So far its working pretty good. Just have to turn off the waypoints in the zone.

I have a request though. Could you give examples of say like how do we use debug? or some of the other commands. Like I havnt tried yet but I was going to put it in a trigger and on act put "RydHQ_Debug = true". This may work fixin to find out, but what of some of the other commands in the pdf?

Thanks :-)

PS: that didnt work lol ohh and by the way also using Blakes_AI_FO_v0_1a works good with this as well.

One more question. Do you think in future releases you can put something in there for support. ex: Ive got a support team with an ambulance. I knew it wouldnt work but never know till you try. I tried it and it used them as scouts ;) :-)

Seriously great job!!!! :-) with tons of potential.

Edited December 22, 2011 by Mikey74

[DaveP 66]

The parlance is 'this setVariable ["setting you want to change","value you want to change it to"]

Eg. This setVariable ["pokeybumwank","false"]

Fun set of scripts, I have some questions/queries:

-how does the commander go about the task of allocating units on a statistical level? Will they try to leverage the strength of one unit against another? (ie. a vehicle might do brilliantly against a sniper, but poorly against an aircraft)

-does the commander use the concept of keeping a reserve unit (or units) to support a main force/defend? Could it be possible to define a unit as a reserve and not have them called from their position until required?

-is there any plans to integrate ai artillery usage? Feels like a missing hole in the puzzle

-when is the objective considered complete? If the objective was moved after the objective was complete, would the commander still pursue it?

-does the commander handle logistic requirements? If a unit ran out of fuel/ammo, could it send re-up?

[stubs 10]

I can't seem to get this to work... Any help or suggestions would be greatly apperciated.

Thanks, Stubs.

[wolffy.au 9]

Rydygier - judging by the comments, this looks really effective.

@DaveP - see if one of you VCB boys can confirm it works well and we may be able to "modularise" it into MSO as an Enemy module.

[thearies 12]

that´s what im waiting for absolutely great, evolution to module would be perfect idea and support of ace2 please....;) ...does drone´s fly in "uncleaned antiair-regions" ?

[katipo66 94]

I can't seem to get this to work... Any help or suggestions would be greatly apperciated.

Thanks, Stubs.

It works with A2 units but doesnt seem to work with OA?

Anyway i used Shukos SHK_pos to randomize the RydHQ_Obj position, use this attachTo [RydHQ_Obj, [0,0,0]]; in RydHQB_Obj to have both factions move to same objective area, objects were just flags.

Where do you call global variables? from init.sqf?

For example where do i put this

RydHQ_Personality = „GENIUSâ€: (RydHQ_Recklessness = 0.5; RydHQ_Consistency = 1; RydHQ_Activity = 1; RydHQ_Reflex = 1; RydHQ_Circumspection = 1; RydHQ_Fineness = 1).

And does that only apply to RydHQ_Obj, if i want a different personality for the B commander do i use

RydHQB_Personality

[Rydygier 1317]

@Mikey74

RydHQ_Debug is simply a global variable. The script periodically checks its value. To set this (and any other variable specified in the manual), you need to place the code that defines a particular variable with properly value, where will be executed in the appropriate time. So if you want to have debug mode from the beginning, you have to put "RydHQ_Debug = true" in a place where it will be executed at the start of the mission, that is, for example in the "init" of any unit/object. Placed in the "act" trigger code will work in a time, when trigger conditions are met. Here is a small demo on Utes for script version:

HACDemo

There isn't enouhg space for proer maneuvers, but you can see, how mission with debug and personalities is set. Other variables shall be defined similarly. For addon you shall simply remove following code:

nul = [] execVM "RydHQInit.sqf"

and some screen (sorry for poor res...)

I hope, this will be helpful.

About support...

HAC by assumption operates on waypoints. Probably would be possible to make the commander to send an ambulance near the wounded or repair truck to damaged vehicle, but rather nothing more. I would prefer not to intervene directly in the activity of individual units. It should only assign them waypoints. I will think about that.

---------- Post added at 12:13 ---------- Previous post was at 11:41 ----------

-how does the commander go about the task of allocating units on a statistical level? Will they try to leverage the strength of one unit against another? (ie. a vehicle might do brilliantly against a sniper, but poorly against an aircraft)

-does the commander use the concept of keeping a reserve unit (or units) to support a main force/defend? Could it be possible to define a unit as a reserve and not have them called from their position until required?

-is there any plans to integrate ai artillery usage? Feels like a missing hole in the puzzle

-when is the objective considered complete? If the objective was moved after the objective was complete, would the commander still pursue it?

-does the commander handle logistic requirements? If a unit ran out of fuel/ammo, could it send re-up?

1. Commander will send up to three groups of infantry and up to two vehicles and no more, than one chopper/plane to destroy one enemy group. It reflects, I think, a reasonable preferred ratio. On type of enemy group depends the type of units that commander try to send in the first place. Then, among the units of a given type chooses those, tha are closer target. Then determines if there are no circumstances which would make risky to send the unit (terrain, presence on the battlefield enemy anti-tank weapons (if present, decides not to send more armored vehicles) etc, with some random factor multiplied by attributes of leaders personality). At the end verifies that the target is already attacked by a sufficient number of units. If not, reaches for another unit, if so, go to the next kind of targets (one target of given kind will be attacked per cycle, but given target can belong to several kinds).

2. Yes. Leader will keep recon and attack reserves (how numerous - depends on leader personality). Those unit will be gradually used by time. To keep some units in reserve for moment of your choose you can put its leaders names into RydHQ_Excluded or, for "B" side, into RydHQB_Excluded array (example in manual) and next to empty this array, when those units shall be used in battle.

3. I'm glad you asking. HAC should works great with this:

Fire at Will addon

4. I think that while he does not see a lot of enemies, the commander will be gradually sent to the area of its objective combat units until it sends all. If you want to stop sending, you have to remove the object from the map RydHQ_Obj (RydHQB_Obj for "B" side) or to use RdHQ_Excluded array. I will think, how to make this more user friendly.

5. See my above post about support. Currently there are no units sent into battle without ammunition.

---------- Post added at 12:16 ---------- Previous post was at 12:13 ----------

I can't seem to get this to work... Any help or suggestions would be greatly apperciated.

Thanks, Stubs.

See just added demo mission. I hope it will help.

---------- Post added at 12:24 ---------- Previous post was at 12:16 ----------

that´s what im waiting for absolutely great, evolution to module would be perfect idea and support of ace2 please....;) ...does drone´s fly in "uncleaned antiair-regions" ?

HAC,I guess, will work fine with ACE if you add under HAC control classnames of ACE's units. See manual (RHQ and RHQB category arrays) to learn, how achieve this. Drones are in air units category, so no, leader rather not send them into area with AA's. In fact HAC control of drones is not tested, I'm not sure, how drone putted flying over map will behave with HAC control...

---------- Post added at 12:32 ---------- Previous post was at 12:24 ----------

It works with A2 units but doesnt seem to work with OA?

You can add also AO units under HAC control, as I mentioned just above (same way as ACE units)

Where do you call global variables? from init.sqf?

This is one of the possibilities. You can define these variables for any effective manner. For example, in the init field of some unit (see demo mission).

For example where do i put this

RydHQ_Personality = „GENIUSâ€: (RydHQ_Recklessness = 0.5; RydHQ_Consistency = 1; RydHQ_Activity = 1; RydHQ_Reflex = 1; RydHQ_Circumspection = 1; RydHQ_Fineness = 1).

Only that (bolded in manual) you should input: RydHQ_Personality = „GENIUSâ€; The rest is just a description of the effects (with how values "genius" will set attributes).

And does that only apply to RydHQ_Obj, if i want a different personality for the B commander do i use

RydHQB_Personality

Yes, thats it. RydHQ_ variables are for "A" side only, analogously RydHQB_ variables are for "B" side.

Edited December 22, 2011 by Rydygier
Typos

[katipo66 94]

Thanks Rydygier, great support :)

[mikey74 187]

Thanks for the reply Rydygier. It answers a few questions. :-) As for support... I wasnt sure how far you wanted to go with this. Its great as is, but if ya wanted to add more ;);) Just figured I'd through in 2 cense. :)

Thanks again. :-)

[DaveP 66]

Great answers Ryd, cheers -I can imagine it's too structurally ingrained, but would there ever be a future possibility of multiple commanders with their own forces per side?

Rydygier - judging by the comments, this looks really effective.

@DaveP - see if one of you VCB boys can confirm it works well and we may be able to "modularise" it into MSO as an Enemy module.

It's not scripted for MP Right now and having only one commander per side makes it suitable only for a single 'battle' rather than a war (ie taking one town, major strategic position, etc.) but I'd tried it before posting that stuff, it's certainly got legs and would be a great FOB defence module

[Rydygier 1317]

Great answers Ryd, cheers -I can imagine it's too structurally ingrained, but would there ever be a future possibility of multiple commanders with their own forces per side?

Well. Theoretically, should be possible to reconfigure the scripts accordingly, but maximum number of leaders probably will be always strictly set. I promise nothing, but I will think...

[munger 25]

This looks excellent Rydygier - really a very promising addon with much potential (though don't get me wrong - it looks very comprehensive already!). :)

Just to clarify how I should use this addon - should I put all units in the editor without waypoints so that the commander can give them waypoints himself? What happens if I set up my own waypoints for some units? For example what would happen if I used this addon in a pre-made mission where every unit already had waypoints, objectives etc set up? Thanks.

[Rydygier 1317]

Just to clarify how I should use this addon - should I put all units in the editor without waypoints so that the commander can give them waypoints himself?

Yes.

What happens if I set up my own waypoints for some units? For example what would happen if I used this addon in a pre-made mission where every unit already had waypoints, objectives etc set up? Thanks.

Script will remove previously added waypoints for all units under HAC control when will give the first command to them. Only, you can do with this is use an RyHQ(B)_Excluded array for some units to bring them out of HAC control.

Edited December 22, 2011 by Rydygier

[andersson 285]

I wish I could say that it works in MP, but I can not. I know not enough to design scripts to make them work in MP. You can try, but I have no idea whether the addon will work in multiplayer. Even if one day I will know the ins and outs of this knowledge, I have virtually no possibility of testing scripts in MP.

If you want to test in a MP environment (this or future projects) you can always start up a dedicated server on you computer, start arma2 as normal and join your very own dedicated server. Its a good way to test, as long as your comp can keep up with it.

This looks like an excellent addon!

[Rydygier 1317]

If you want to test in a MP environment (this or future projects) you can always start up a dedicated server on you computer, start arma2 as normal and join your very own dedicated server. Its a good way to test, as long as your comp can keep up with it.

Ha ha, you see? I did not know even that about multi. :). Hmm. So, who knows, maybe in next year will study all this MP scripting. Thanks for info!