README

KI(AI)-Addon 2.0 by SKY

Needs Operation Flashpoint Resistance Version 1.96

Developed for better reaction of units and vehicles in difined areas.

This addon was inspired by the KIAddon by Kriegerdaemon. (Download at "www.mapfact.net").


KI-Addon Folders


Table of content

  1. Overview - what does the KI(AI)-Addon?
  2. Installation
  3. Settings with dialog-window
  4. Settings without dialog-window (hide dialog)
  5. Special functions (additional settings) and hints
  6. AI-Addon 2.0 together with DAC v1  
  7. Disclaimer
  8. Problems
  9. Changes since v. 1.8
  10. Credits


1. What the KI(AI)-Addon preforms

(Overview - details following later):

Basically the KI(AI)-Addon works like a "trigger" with condition "detected by ´´side X´´". When 'triggered' it will start further scripts.
Unlike with a trigger you are able to define and use several additional conditions to control the reactions of units.
With a trigger in the editor you define the area were the KI(AI)-Addon is meant to be active. You are free to define more than one area or you can define even the entire island! 
The enemy units are added by the trigger(s) to the array "KIA_NotFriendly", filtered in the "InitKIA.sqs" and send to other arrays ("KIA_Enemies", "KIA_Air", "KIA_Tanks", "KIA_MGs"-StaticMGs - even crews of vehicles will be detected!)
The units in these arrays can trigger the alarm and are managed by the KI(AI)-Addon.
The KI(AI)-Addon is controled by variables. The functions are:
back to content

2. Installation

1.       Open the folder "KI_Addon_SKY"
Only if you don´t use your own "Init.sqs", "Description.ext" and "Stringtable.csv":
Add this folder and this files to your mission folder:
Folder "KI_Addon2.0"

+description.ext
+init.sqs
+stringtable.csv
continue with point 2.

Otherwise do this:
-   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -    

1.01. To add my "Description.ext" to yours: Copy the content of my "description.ext" into yours or:
Your Description.ext (text)
-----------------------------------------
-----------------------------------------
-----------------------------}

Add this line at the end of your file: #include <KI_Addon_Data\KIAddonDescription.h> . The folder "KI_Addon_Data" has to be in the main folder of Operation Flashpoint!

1.02. To merge the content of my "Init.sqs" with yours: Add the content of the "Init.sqs" to the beginning of your own "Init.sqs".

1.03. To add the content of my "stringtable.csv" to your: Make sure that no string-name is used twice! (Check the order or languages!)

1.04. Add the folder "KI_Addon2.0" to your mission folder.
-   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -    

2. Set two triggers in editor:


a) For the enemies (see picture 1):

    AXIS: As you like - All enemys in it are ´´smarter´´.
    This takes effect at starting mission - if units leave the triggerlist later on they keep being "smart"
    If units get into the triggerlist later on, they don´t become "smart"!

    ACTIVATION: East/west/resistance - Side of enemy. You could use "Anybody", but then no friendly unit or empty vehicle should be         in triggerlist! For two parties of enemies - use two triggers.
   
    trigger ONCE

    COUNTDOWN: 2-2-2 - there has to be the waiting time to prevent mistakes at mission start.


    ON ACTIVATION: KIA_NotFriendly = ThisList
    If you want the KI(AI)-Addon to be activ in more than one area: Each additional trigger has to activate later. Set a countdown of +2               seconds to the main/last trigger.
    ´´ON ACTIVATION´´ of these triggers you have to write ´´KIA_NotFriendly = KIA_NotFriendly + ThisList´´
   
If the time all triggers work is longer than 6 seconds:  Change value in file "InitKIA.sqs" under "6. .../WAITING TIME SINCE ALL                   TRIGGER WORK" as needed!
       
    HINT:
    Empty vehicles will not be in trigger list (exept ACTIVATION: Anybody) and will not support
    (Alternative: 5. SPECIAL FUNCTIONS / HINTS point 1. SPECIAL CASE EMPTY VEHICLES/...).

   
     back to content

    Picture 1

    
     

     back

      Picture 2

     
back

b) FRIENDLY

AXIS: As you like - units in it are on side of player. Even more then one group is possible.
 
ACTIVATION: East/west/resistance - Side of friendly.

 trigger ONCE
  
COUNTDOWN: 2-2-2

ON ACTIVATION: KIA_PlayerSide = ThisList


HINT:
This also works without a trigger. You only have to define the array "KIA_PlayerSide" at mission start. Add the names of all friendly units or the group names. For example: KIA_PlayerSide = []+ units group xy

back to content

     Picture 3

     


3.  Create a Game-Logic-Objekt (Name: Server)!

     Picture 4

     

4. Set a radio-trigger to call the settings-dialog during testing repeatedly:

(It has to be a radio-trigger! A call out of the action-menue will not work!)

    
    Axis:
0
   
   
    FIELD - "ACTIVATION":
Radio "X"
   
   
trigger REPEATEDLY 
    
    FIELD - "ON ACTIVATION": [] exec "KI_Addon2.0\KIA_CreateDialog.sqs"

5. Make sure that you didn´t name a unit "Leader"! If units on side of player are using non standard weapons, than read this info too.
    If a unit is to be able to support - don´t set a waypoint for it with the condition "hold"! When the unit reaches the waypoint it can't provide     any support because it will "hold"!
    Now the KI(AI)-Addon is ready.

6. For best use you have to read the following information and the detailed informations in the settings-dialog at mission start!  
back to content

3. SETTINGS WITH DIALOG-WINDOW

The dialog-window appears at mission start. On the left side the variables are listed.  The next column shows the actual settings.
In column "New" settings can be canged and additional dialogs can be opened.
In the "Info" box all information about the variables is shown, it appears by clicking on the respective variable.


Saving your new settings activates them immediately!
You shouldn´t change settings during an alarm, because then not all new values will be accepted!
All your new settings will be deleted by ending or aborting the mission! - Therefore take down a note of all the new settings for your mission!



Mind this
point, if you use other weapons, mines or satchels.
If you use DAC + KI(AI)-Addon with activated vehicle support, then mind this 
point.
If units on player side might use a ship or are standing near the waterline, then mind this
point.
- All these
settings can not be made in dialog!

back to content

4. SETTINGS WITHOUT DIALOG-WINDOW (hide dialog)

1. Hide dialog:
    - Open file "InitKIA.sqs", Path: ...\KI_Addon2.0\InitKIA.sqs
    - Go to point  "1. .../TEXT SIGN - LOADING DIALOG"
    - Set the variable "_Show_Dialog" to "false"
    - Save the settings


2. Settings in the file "InitKIA.sqs":
    - Open the file "InitKIA.sqs", Path: ...\KI_Addon2.0\InitKIA.sqs
    - Go to point "2. .../NOT SUPPORTING (ENEMY) UNITS"  
      Information under 5. SPECIAL FUNCTIONS/HINTS point "2. SPECIAL CASE NOT SUPPORTING ENEMY UNITS")
      In the []-brackets you can add the names of enemy units that you don´t want to support (You have to use the names you gave them, not       the names the game uses for the units!)
   -  If units on side of player (units in array "KIA_PlayerSide") use other weapons than the standard ones check under "5. .../ARRAYS TO         EXCHANGE INFORMATION IN SCRIPT - Launcher/Silent Weapons/Mines-Pipebombs-("put")" if the weapons you use aren´t in one         of the arrays, then add them. (You can easily find out the editor-name/"Put"-name and whether the weapon is in one of the arrays:               Open file "...\KI-Addon2.0\KIA_Shot.sqs" and delete the semicolon in front of line: ";if (_waffe in KIA_LoudWeapons or...". Then start         the mission with KI(AI)-Addon and fire with the weapon or put a mine/pipebomb when KI(AI)-Addon is ready.
    - Check under "6. .../WAITING TIME SINCE ALL TRIGGER WORK" if you have to set more waiting time since the/all trigger                          (trigger: Look at 2. Installation point 2.) work.
    - Go to point "8.01.  .../ACTIVATE VEHICLE CLASSES"
      By deleting the semicolon in front of the vehicle-classes you activate them for the vehicle support
      (additionaly the value of the variable "KIA_VehicleSupport" in file "InitKIA_StandardSettings.sqs" has to be "true"!)
(If you use the KI-Addon withe the DAC by Silola you have to activate the vehicle-classes in file                                              "KI_Addon2.0\Sort_DAC_units.sqs" too!)

3.   Settings of the variables in the file "InitKIA_StandardSettings.sqs":
    - Open the file "InitKIA_StandardSettings.sqs", Path: ...\KI_Addon2.0\InitKIA_StandardSettings.sqs
    - Change the settings as needed
    - Save the new values (values are loaded automaticaly at mission start)
      It is possible to change each value of a variable with a trigger or script while playing!
      (In MP-Missions: If you change the variable "KIA_Off" define it as "publicvariable = KIA_Off"!)


4. Settings for guards:
    - Read the information under 5. SPECIAL FUNCTIONS/HINTS point "3. LOOK AROUND GUARDS" or

    - Open file "LookAroundGuards.sqs", or "LookAroundOwnGuards.sqs". Path: ...\KI_Addon2.0\LookAroundGuards.sqs                                   (LookAroundOwnGuards.sqs)
    - Read the information at the beginning

    - Add into the init-line of the guard the needed line: ([This,´angle´] exec                                                                                                                     "KI_Addon2.0\LookAroundGuards.sqs"/ or for own guards [This,´angle´] exec "KI_Addon2.0\LookAroundOwnGuards.sqs")

back to content

5. SPEZIAL FUNKTIONS / HINTS    

   Sezial funktions

    1. Empty vehicles
    2. Not supporting units
    3. Look around guards
    4. Optimal visual field
    5. Filter for finding bodies
    6. Fire and shout
    7. Aircraft calls new support
    8. Exchange units - keep new grouping
    9. Reveal
  10. Troop transport with tank and aircraft
  11. Several infantry-/tank groups support
       Hints

1. SPECIAL CASE EMPTY VEHICLES / TANK SUPPORT / AIRCRAFT SUPPORT / EMPTY STATIC-MGs

In the standard situation helos, tanks and other vehicles are manned meaning less work and good results.
But there is an alternative: the crews only board their vehicles when alarmed.
To do so use waypoints with the condition "KIA_Alert" or a waypoint synchronized with a trigger.

IMPORTANT:  
The names of the empty vehicles have to be added to the respetive array in file "InitKIA.sqs" - with the exeption of empty static-MGs!
Open file "InitKIA.sqs" go to point 4. VEHICLE CLASSES and add the vehicle names to the arrays. For example: KIA_Tank = [´name tank´]. All units that will get in vehicles on KIA_Alert, have to be declared as "Not Supporting Enemy Units"  (see point 2.)
Otherwise it might happen that they are the nearest unit to the point of "KIA_Alert" and their waypoints get locked - then they support as infantry without their vehicle!

IMPORTANT:
If you want more than one tank/vehicle to support, the crews have to be in seperate groups. Let them get in their vehicle when alert is triggered, then all crews of all tanks/vehicles have to join a leading soldier.
But wait until ALL crews are in their vehicles! Use a trigger to check that and then let them join the leading soldier.
(For example: "[_x] join leader group 1" foreach units group 2 - you have to define the group names before). Do not join the vehicle-names!
After an alarm is triggered, the crews have to get in their vehicles in less than 60 seconds. Otherwise the ai-script will declare the empty vehicle as locked for support. AI-Script then searches for other vehicles!    
So it is better not to have more than two empty tanks/vehicles to join for support. Because the script will wait 60 seconds for each single vehicle for the crew to get in the ai-script needs much time searching for support-vehicles. (Alternatively allow more than one tank group. See point  11. Several infantry- / tank groups support.
Or declare all tanks/vehicles (except the leading vehicle!) that you whant to join as "Not Supporting Enemy Units" - see point 2. - then the ai-script only scans the leader vehicle and the other ones will support, too, after joining the leader!
       
BE AWARE:
The crew is bound to the vehicle, even when they get out. If the player or a playerunit gets in such a vehicle, the crew will raise an alarm ! Lock these vehicles for the player/playerunits with "this lock true" in init-line!

back to special functions
back to content

2. SPECIAL CASE NOT SUPPORTING (ENEMY) UNITS

Units that are not to/cannot  move/support have to be added to the array "KIA_NotSupportingUnits" means "Not Supporting Enemy Units". Static-MGs will be added to the array at mission start automatically.
If you want other units not to support write their names into the brackets of - "KIA_NotSupportingUnits = []" (look in "InitKIA.sqs" under 2.), or call the "Not Supporting Enemy Units-dialog-wondow" in the settings-dialog while testing.

IMPORTANT:
If there are units in the same group with a Static-MG, these units have to be added to the array. Otherwise the scripts for support can't work correctly. If you want to define a whole group as ´´Not Supporting Enemy Units´´, you have to add ALL group members to the array!
   
HINT: For large groups you also can give the order at the end of "InitKIA.sqs" file or in a trigger  --> ´´KIA_NotSupportingUnits = KIA_NotSupportingUnits + [_x]´´ foreach units (´name of group´).
Or name the group, for example "grp1" and write in "InitKIA.sqs": KIA_NotSupportingUnits = [...,...] + units grp1 + ...

back to special functions
back to content

3. LOOK AROUND GUARDS

If you want guards to randomly change their direction of view just write in their init-line: [this,"sector/angle to look for - to 360°] exec "KI_Addon2.0\LookAroundGuards.sqs"
Example for an 90° sector/angle started from init-line of the guard: [This,90] exec "KI_Addon2.0\LookAroundGuards.sqs"

HINT: Declare the guards as "Not Supporting Enemy Units", so they will not support anyone. (But you don´t have to do that.) If you want your own guards to look around: Activate the guard with the following command in init-line: [This,´angle´] exec "KI_Addon2.0\LookAroundOwnGuards.sqs".


4. OPTIMAL VISUAL FIELD (finding bodies)

You can find out the optimal settings to find bodies for each unit with the file "KIA_View.sqs" (Path: ...\KI_Addon2.0\KIA_View.sqs). The script makes the visual field of units visible.
The actual visual field depends on the values of the variables "KIA_VisualField", "KIA_Visibility" and the skill of a unit.
The script can be started out of the init-line of a unit - [This,´value visual field ´,´value visibility´] exec "KI_Addon2.0\KIA_View.sqs".


back to special functions
back to content

5. FILTER-FIND BODIES

It is possible to lock units or unit-classes so that they can´t find bodies: Path: ...\KI_Addon2.0\KI_Addon.sqs

6. FIRE AND SHOUT

If someone raises an alarm he fires his weapon (only with not silenced weapons) and screams something.
This event can be changed  or disabled in KI(AI)-Script (Path: ...\KI_Addon2.0\KI_Addon.sqs" under "#Feuern1;#Feuern2;#Alarmruf1;#Alarmruf2).


7. HELO CALLS FOR SUPPORT

If all supporters and the spotting units are dead (or vehicles can´t move) and only the helo is alive, then he will call for new support (only if he knews thomsthing about the attacker). You can disable this in file "KIA_StandardSettings.sqs", set the variable KIA_NewSupport to "false".

back to special functions
back to content

8. EXCHANGE UNITS - KEEP NEW GROUPINGS

If "Support=true (KIA_Support) & Exchange Units=true (KIA_ExchangeUnits)" is set, then new groups can be build (infantry). After an alarm is set off the grouping will be the same as before alert (if possible and if they didn´t merge).
If you want to keep the new groups: Open file "KIA_Support.sqs" (Path: ...\KI_Addon2.0\KIA_Support.sqs).
Under "#zurueck" (at end of file) deaktivate line "? KIA_ExchangeUnits: ...".


9. REVEAL  

When an alarm is raised: All units that have a knowsabout value >= alert at (KIA_AlertAt) about the attacker(s) can reveal all other units that are in the "Distance of support".
To activate this: Open file "KI_Addon.sqs", (Path: ...\KI_Addon2.0\KI_Addon.sqs), under "#reveal" disable line ´´goto "wp"´´.
You don´t have to use the "Distance of support" as "reveal distance". For a different distance replace "KIA_DistanceOfSupport" in line "_revealdistance = KIA_DistanceOfSupport" with simply a number.


BE AWARE:
Each tank and static-mg will know something about your group. If you don´t take enough cover you could die soon.

back to special functions
back to content

10. TROOP TRANSPORT WITH TANK AND AIRCRAFT

Additional infantry support can be brought to the battlefield with supporting tank(s) or aircraft(s). It doesn´t matter if the group in cargo is the group of the vehicle driver or not! After battle they'll get into their carrying-vehicle, if possible, and will move back to their starting position.
In the file "KIA_StandardSettings.sqs" you can setwether if units in cargo of tank(s)/aircraft(s) can get out or not. Also you can force aircraft(s) only to transport para troops ("KIA_OnlyTransport") to the alarm position.
At "KIA_OnlyTransport=true"  the units will move back to the starting point of the helo/aircraft (if possible) and will getin the aircraft there. At "KIA_OnlyTransport=false" the units will be picked up by the supporting helo nearby the alarm position after the alarm ends. (If you don´t want that, then set the variable  "_pickup" in file "KIA_EjectGroupSearch.sqs" to "false".)


If you don´t want units to get in cargo until the alert (KIA_Alert) is triggered at last set up two triggers for the group and place the units nearby the transport vehicle. Set the first waypoint with condition "KIA_Alert" and the second (getin) onto the transport-vehicle.

back to special functions
back to content

11. MULTIPLE INFANTRY / TANK GROUPS SUPPORT

The number of supporting infantry groups and tank groups can be set just as you want . It's a good advise not to have more than 3 groups, though. The number means the number of groups and not the number of group members! For example you allow 3 tank groups with 2 tanks in each group. At the alarm position will be 6 tanks cumbering each other - so be aware (By default the variable "KIA_OnlyOneTank" is set to "false", otherwise only one tank out of each group will support!).
You can change settings 
in the file "KIA_StandardSettings.sqs" as well as in the settings dialog window.

back to special functions

back to content

HINTS:

In the file "KIA_StandardSettings.sqs" the default value of the variable "KIA_ShipSupport"  is set to "true".  If the  point, where the alarm is set off or the position of a spotted enemy  is in the water or or very close to it this variable is activated and a ship (or a ship group) will provide support.

All supporting units have to be added to a array on the 5. position in the main array "KIA_Supporters" (KIA_Supporters select 4).
While an alarm is active it is possible to find out how many units are still alive or dead.

   
It is possible to start the KI(AI)-Addon-Script even without someone or some body was detected . Simply start the script with: ´Name of unit´ exec "KI_Addon2.0\KI_Addon.sqs".

If the side of the player is the side of the enemy (for example: Player as spy), then no unit on player side must be in the main trigger! (as to the 'Trigger' see 2. INSTALLATION under point 2.)

Is "KIA_TankSupport=true + KIA_OnlyOneTank=false" and there are mixed groups of tanks and other vehicles (a convoy), then define the whole group (name of the vehicles) as "KIA_NotSupportingUnits". Otherwise the soft vehicles will support together with the tanks (If the tank is the nearest unit to an alarm position or the convoy is under attack).

Basically there is only one alarm stage.    
It is not possible to trigger alarm at different positons at the same time. Also spotted units at a distance of more than 500 m to the alert position or other spotted positions will be ignored. (That prevents the supporting groups from being divided)

But in the KI(AI)-Script "KIA_Alert" is set to "true" at two positions. The difference: KIA_Alert at spotting an unit and at spotting a body.
So you can start your own scripts out of the KI(AI)-Script and change values of KI(AI)-Addon variables (or add your own variables) for each situation! Path: ...\KI_Addon2.0\KI_Addon.sqs - under #ausloesen (player unit spotted) and #alertentdeckt (a bodywas spotted) There, each time after line "KIA_Alert=true", you can start your own scripts by setting the new values of the KI(AI)-Addon variables and/or adding your own variables. Depending on the situation.



TIP: If you want supporting units/vehicles to move to a specific position (and not to the unit that initiated alert), then you have to set some variables to "true" and to define a position on map:
Condition: "KIA_Alert=true" or let a unit set off the alarm,
(see hints: Start KI(AI)-Addon directly)
Koordinate/position: KIA_DiscoverPosition = [x,y,z] or KIA_DiscoverPosition = getpos ´name´

Variables:   

If you want other vehicles outside the KI(AI)-Addon (that are not managed with the KI Addon) to support, then give them order to move to the the position "KIA_DiscoverPosition" (only if this position was defined before!) or give them order to move to the object "KIA_AlertPoint". (A "HeliHEmpty" object - it will be created at the position of the unit that set off the alarm.)
The command line for the unit/vehicle could look like this:  "Name of unit" move getpos KIA_AlertPoint or "name of unit" move KIA_DiscoverPosition.


back to special functions
back to content
 

6. KI-Addon 2.0 together with DAC v1

  1. The folders "KI_Addon2.0" and DAC have to be in your mission folder
  2. All triggers for the KI(AI)-Addon and DAC have to be set,  there's only one server-object needed - it is the same as in DAC 
  3. It has to be at least one unit in the trigger list of the maintrigger of the KI(AI)-Addon (KIA_NotFriendly = ThisList). It might as well be the  "DAC-Dummy".
  4. If you want to use the KI(AI)-Addon-Dialog  (only single player missions): Description.ext and stringtabel.csv have to be in your mission folder, see also:   installation
  5. In file "DAC_Init_Config.sqs" change the DAC_KI_Addon setting:   
       
        ;\\\\\\\\\\\\\\\\\\\\\\\\\\\
        ; DAC-Settings
        ;///////////////////////////
       
        DAC_KI_AddOn       = 2                                                                                                                                                                                    
  6. Copy and paste the "KI_2" folder into the DAC folder (Path: "...\KIA2.0_UnitInfo_RearmUnits\KI-Addon-SKY_and_DAC-Silola\KI_2")                                                                                                                                  
  7. Replace the files "DAC_Init_Creator.sqs", DAC_Group_Air.sqs and "DAC_Group_Soldier.sqs" in DAC folder (Path: "...\DAC\Scripts\...") with the modified ones in folder "KI-Addon-SKY_and_DAC-Silola"  (Path:"...\KIA2.0_UnitInfo_RearmUnits\KI-Addon-SKY_and_DAC-Silola\...")                                                                                                     
  8. At vehicle support: Additionally  set parameters in the file "KI_Addon2.0\Sort_DAC_Units.sqs" - the same way as in the file "KI_Addon2.0\InitKIA.sqs" for vehicle support.                                                                                                                                             
  9. Start the KI(AI)-Addon out of Init.sqs ([] exec "KI_Addon2.0\InitKIA.sqs" - at the very beginning before DAC is ready)



  

7. Disclaimer

This software is not made for commercial use. If you want to use it commercially anyway, you have to contact the author.
For crashes or dammages caused by this addon, the author takes no responsibility.
(Yet the software caused no dammage in multiple tests.)
Use at your own risk!

This is no official addon by BIS or Codemasters. Please do not send questions or complains to them!

Kontakt Author: SKY-Mapper@gmx-topmail.de


back to content

8. Problems   


If a unit/group can not move to the unit that triggered KIA_Alert or to a dead unit, then there will be neither support nor KIA_Alert.
Be carefull how you set guards inside and outside base fences. The units use to ignore base fences - they can "see" through it and could spot a dead body. I have set a kind of filter to prevent units from looking through fences and houses, but that doesn´t work propperly in every situation.  So don´t let units outside and inside bases look face to face. If that is not possible or you don´t want that, increase the radius of "Radius Of Reaction" to solve this problem.

Situation: To units look face to face, one of them is killed (they are not in the same group). The distance between the two is not below the "Radius Of Reaction" and the other one does not react.  That might happen, if the distance is just a bit below 15m.
This is due to the filter I have set to prevent units from seeing through fences and houses. To solve this problem, increase the "Radius Of Reaction".

When KIA_Alert is triggered shortly after the end of a previous KIA_Alert and the supporting helo had began to land, then it has to land at first before being able to support again. In a very few situations the helo will not support again.

It might happen, that a tank doesn´t search for attackers, even if "Always Tank Search" is set to "true":this is the case if the crew of a dammaged leading tank have got out of there wrecked vehicle. If a convoy is under attack and the leader can get out of his vehicle and get in a supporting/searching tank, then the other vehicles will follow the searching tank.
In some situations the game-AI disturbs the script. Then tanks/vehicles will not react as wanted.
If a tank member is of a group and "Tank Support = true + Only One Tank = true" then it loses his knowsabout value, but will search anyway.

Every vehicle that was manned at mission start, is bound with every enemy and not only with the crew, when the crew is disembarked. Therefore every vehicle that can be left by its crew, has to be locked in the init-line with order "this lock true"!     
   
To load a "savegame" can cause problems if you use many other variables and scripts in your mission. The game might crash to desktop or saved information isn't read corectly.
  

back to content

9. Changes since V. 1.8 

(Version 1.9 was only made for testing and hasn't been published)

back to content


10. Credits

Special thanks to Silola for his efforts to bring DAC and KI(AI)-Addon together.
Thanks to BaddAss and Chneemann for testing and ideas.
Thank you to "www.mapfact.net" and thanks for help in mapfact forum
Thanks to all the players at the mp-test on mapfact server. Thank you to 
MCPXXL and to the other guys making it possible.
A belated thank you to Lester for his english translation help and the beta testers 
BigX, Clausewitz, Lenny and BadAss and all that helped with version 1.8. In v1.8 I forgot the credits - shame on me.

Last but not least - thank you to BIS for this ingenius game!