AI_editing_commands

It has been brought to my attention that there wasnt any credits given in the tutorial to the contributors of the information for the guide below so i'll add them outside the document.
Primary sources for the document below:
Anarchy studios: http://planetcnc.com/anarchymods
Deezire : http://www.deezire.net



	INTERMEDIATE GUIDE TO AI ENHANCEMENT By: Haris Ikram Web site: http://www.racom.homestead.com/ Contents: 1. Improving AI from Rules.ini 2. Using AI.ini 3. Contact/Issues Improving AI from Rules.ini A good modder will find that there so many ways of improving AI just from the rules.ini. I�ve included some of the things you can change, to toughen up the AI. There are many more ways. The following sections have the following AI properties you can change: Computer movement and controls AIHateDelays= The delays, in frames, before the AI chooses an enemy. Listed by difficulty level Easy, Medium, Brutal. AIAlternateProductionCreditCutoff= When the AI has less credits than this it will begin to spend money more conservatively. AIUseTurbineUpgradeProbability= Percentage chance that the AI will upgrade its power plants rather than build a new one. Although parsed and valid in Red Alert 2, this is unused and should be set to 0.00 as power plants cannot be upgraded with 'plug-ins' like they could in Tiberian Sun. This does open up the possibility of this logic being enabled, however. NodAIBuildsWalls= Can be set to 'yes' or 'no' and determines whether or not the AI will build walls when it is a Soviet army. Appears to have no effect as structures can now have the ProtectWithWall= tag which makes the AI more effective at wall deployment. In either case, the AI has never geen any good at building walls and the 'new' wall logic that was implemented in Tiberian Sun (where you could string wall sections together as determined by their GuardRange= ) simply causes more problems and the AI eventually makes it's own base practically impassable - this in turn causes the game to slow to a crawl as the AI tries to move it's units. AIBuildsWalls= Can be set to 'yes' or 'no' and determines whether or not the AI will build walls when it is an Allied army. Appears to have no effect as structures can now have the ProtectWithWall= tag which makes the AI more effective at wall deployment. In either case, the AI has never geen any good at building walls and the 'new' wall logic that was implemented in Tiberian Sun (where you could string wall sections together as determined by their GuardRange= ) simply causes more problems and the AI eventually makes it's own base practically impassable - this in turn causes the game to slow to a crawl as the AI tries to MultiplayerAICM= These are the coefficients applied to the amount of money the AI generates in multiplayer games. Listed by difficulty level, Brutal, Medium, Easy. AIVirtualPurifiers= These are the multipliers to the AI's harvested money bonus for multiplayer games only. They default to hardcoded values for the single player campaign. Listed by difficulty level, Brutal, Medium, Easy. MinimumAIDefensiveTeams= The minimum number of teams the AI will create to assign to defensive missions. Listed by difficulty level, Brutal, Medium, Easy. MaximumAIDefensiveTeams= The maximum number of teams the AI will create to assign to defensive missions. Listed by difficulty level, Brutal, Medium, Easy. TotalAITeamCap= The total number of team types the AI will aspire to have at any one time to assign to specific missions. These are in addition to general unit creation which may be used for any action. Listed by difficulty level, Brutal, Medium, Easy. New AI Type Snippets AISafeDistance= Distance, in cells, that the AI will consider gathering outside it's enemies base. This distance is measured from the center of the enemy base. It appears that the 'gather' action is a new script type specific to Red Alert 2. AIMinorSuperReadyPercent= When an Iron Curtain or Chronosphere is this charged, the AI will consider it in it's AI triggers. This is what makes the AI Iron Curtain it's tanks when they attack you, or Chronoshift it's units at you rather than send them across the map. HarvesterTooFarDistance= If a War Miner is further than this from the refinery it wants, it will move next to it instead of reserving it and refigure things out when it stops. This value should be small to approximate the wait/time concern versus driving to the next refinery. Overall, this speeds up the income of credits from harvested Ore and Gems. ChronoHarvTooFarDistance= As above but for Chrono Miners. Rather than have them teleport super far and then re-pick an Ore patch (or teleport super far and drive super far back), they will stay on their side of the map (for example when the player has more than one base or multiple refineries with long distances between them). Appears to cause problems when stretches of water separat the bases as the Chrono Miners have difficulty teleporting across stretches of water. AlliedBaseDefenseCounts= This is the explicit number of base defense structures that Brutal, Medium and Easy Allied AI players will plan on making. The structures picked are those with IsBaseDefense=yes set in their entry, although that tag should not be used to get the AI to build other structures as it is also used for AI targeting and threat evaluation purposes. It's tricky, but to predict how many the AI is likely to build, use this formula;- ((Total Base Value - 2000) / 1500 x GDIBaseDefenseCoefficient) + 3 x (Difficulty Level - 1) SovietBaseDefenseCounts= This is the explicit number of base defense structures that Brutal, Medium and Easy Soviet AI players will plan on making. The structures picked are those with IsBaseDefense=yes set in their entry, although that tag should not be used to get the AI to build other structures as it is also used for AI targeting and threat evaluation purposes. It's tricky, but to predict how many the AI is likely to build, use this formula;- ((Total Base Value - 2000) / 1500 x NodBaseDefenseCoefficient) + 3 x (Difficulty Level - 1) AIPickWallDefensePercent= Each time the AI picks to build a base defense, this is the percentage chance it will override picking a gun type with picking a wall (if there are any buildings left in it's base with ProtectWithWall=yes set which have not yet been surrounded by walls). Listed by difficulty level, Brutal, Medium, Easy. AIRestrictReplaceTime= After the AI takes damage to a building, this is the number of frames to restrict the replacement of lost buildings to only walls, power and base defenses. ThreatPerOccupant= The increase to an occupied structures' ThreatPosed= value per occupant. ApproachTargetResetMultiplier= The approach target position should be recalculated if the target is further away than the weapon range times this. ApproachTarget is an AI script action which picks a target within it's weapons Range= and if it gets further away than that range times this value the AI knows the target is moving and that it will need to re-figure where it is. This can be overridden in the units' entry with the CanApproachTarget= statement. CampaignMoneyDeltaEasy= This value is added to the Easy difficulty level credits amount for all houses which have PlayerControl=yes assigned. This is added at the time the houses are read - it is the only thing that is known at that time so it can't be the player's house only. Change this value to adjust the amount of money someone starts with on a map. CampaignMoneyDeltaHard= This value is added to the Brutal difficulty level credits amount for all houses which have PlayerControl=yes assigned. This is added at the time the houses are read - it is the only thing that is known at that time so it can't be the player's house only. Change this value to adjust the amount of money someone starts with on a map. GuardAreaTargetingDelay= Used to provide explicit control of targeting rates in frames, when engaged in guard mode. NormalTargetingDelay= Used to provide explicit control of targeting rates in frames, when not engaged in a mission or AI trigger. AINavalYardAdjacency= Distance, in cells, that the AI can place it's Naval Yard from it's Construction Yard. DisabledDisguiseDetectionPercent= The percentage chance that an individual unit will detect a Mirage Tank which is fake-blinking (after firing). This is per unit, so even a lowish number is near enough automatic when then the AI has several units nearby. In other words, the more units that are near a disguised Mirage Tank which fires, the more likely it is to be discovered. Listed by difficulty level, Brutal, Medium, Easy. AIAutoDeployFrameDelay= The number of frames that the AI will wait to deploy it's GI's that are in guard mode so that they don't bounce up and down. Listed by difficulty level, Brutal, Medium, Easy. MaximumBuildingPlacementFailures= If the AI gets hung up on thinking it can place something but being unable to clear the space (too jammed with units for example) then it abandons that action after this many failures. The AI will wait for the number of frames specified in PlacementDelay= before trying again so that you can tell how long it will try for it. PurifierBonus= Percentage added to the value of harvested Ore by Ore Purifiers (any structure with OrePurifier=yes set). The AI can be prevented from building certain structures by adding the following line: AIBuildThis=no. Some structures like the Service Depots have this code enabled. To allow the computer to build the depot change this line to: AIBuildthis=yes Using AI.ini This file controls the Artificial Intelligence employed by the game engine when it assumes the role of a computer controlled player. Red Alert 2 utilizes 'scripted' AI (that is, a system based on pre-determined actions and scripts rather than a 'heuristic' system, i.e. one which intelligently responds to player actions and attempts to forecast future player actions by recording a log of previous ones in a bid to nullify them thus giving itself a tactical advantage). In simple terms, the scripted system works like this;- The computer uses an object, or group of objects, known as TaskForces... ...whose generic behaviour and unique properties are controlled by allocating them to TeamTypes... ...to carry out an action, or series of actions, controlled by ScriptTypes... ...which may or may not be triggered by predefined game events known as AITriggerTypes. [TaskForces] This section takes the form of a list of all TaskForces to be used by the computer generically across all games. The list is numbered starting at 0, new ones should be simply added to the end of the list. If you want the computer to make use of new units, or to use more units, then this section is the one to modify. Each entry in the list takes the form of a hexadecimal numbered string which is the unique identifier for each of the TaskForces - like other lists in the INI files, the game code requires that each entry in this list is defined with it's own section in this file. For convention, it is wise to stick to this hex numbering system, although any string appears to be parsed. An example is detailed below;- [TASKFORCE] Name= a=x,UNIT b=x,UNIT c=x,UNIT ... Group= [TASKFORCE] - this is the unique identifier name used to define the section for this TaskForce and should also be contained in the above mentioned list. Name= - this is simply a string name used for identification purposes only, it is not required by the game, although it is useful to leave this in for debugging and troubleshooting your AI.INI file - as a point of interest, this statement does not even get parsed. n=x,UNIT - this is used to define which units are in this TaskForce. This is in the form of a list, and for each different unit you want in your TaskForce, you must have a seperate line in the list. Each line consists of a number (how many of the unit) followed by a comma and then the name of that unit from the [BuildingTypes],[InfantryTypes],[VehicleTypes] or [AircraftTypes]lists from RULES.INI. Note that the numbering must start at 0. For example, to define a TaskForce with 5 GI's and 2 Grizzly Tanks, you could use;- [TASKFORCE] Name=5 GI's and 2 Grizzly Tanks 0=5,E1 1=2,MTNK Group=-1 Group= - this causes the TaskForce to form a particular grouping when it has been completely created or recruited together (in other words all of it's members are present). A value of -1 (which is all Red Alert 2 ever uses) simply means 'default' which makes all of the units move and face as they would when left alone (this should be used if the TaskForce contains a transport onto which other members will be loaded with your ScriptType - see below). Values other than that may be residual from Red Alert and cause problems (see the 'change grouping' entry of the [ScriptTypes] section for more detailed information on groupings, their settings and this inherent problem). [ScriptTypes] This section takes the form of a list of all ScriptTypes which can be be used by TaskForces. The list is numbered starting at 0, new ones should be simply added to the end of the list. Each entry in the list takes the form of a hexadecimal numbered string which is the unique identifier for each of the ScriptTypes - like other lists in the INI files, the game code requires that each entry in this list is defined with it's own section in this file. For convention, it is wise to stick to this hex numbering system although again this is not strictly necessary. The section entries describe what the TaskForce is going to do and consists of a list of action codes. An example is detailed below;- [SCRIPT] Name= a=x,y b=x,y c=x,y ... [SCRIPT] - this is the unique identifier name used to define the section for this ScriptType and should also be contained in the above list. Name= - this is simply a string name used for identification purposes only, it is not required by the game, although it is useful to leave this in for debugging and troubleshooting your AI.INI file - as a point of interest, this statement does not even get parsed. n=x,y - this defines the action to be performed by the TaskForce to which this ScriptType is allocated. This takes the form of a list, and for each action you want the TaskForce to perform, you should have a new line in your script. Think of this like writing a computer program - for everything you want the computer to do, you add a new line to your program - it's the same idea here. Again, by convention, the numbering must begin at 0. These scripts can become very complex and powerful tools, and provide one of the ultimate levels of editing potential in the game. The first value, x, contains the action to perform. Some actions require a parameter, y, which provides information for the action - they mean different things for different actions. Here's an example of a script, the first line tells the computer to attack any enemy vehicles, and the second line tells the computer to attack anything when it's finished the first line (ie after it has destroyed one vehicle);- [SCRIPT] Name=Attack any vehicle then attack anything 0=0,5 1=0,1 Here's a list of the known script actions and their respective parameters (where appropriate);- 0,n = Attack target, n = target type to attack This instructs the TeamType to use the TaskForce to approach and attack the target specified by the second parameter. The following are the target types which can be used;- 0 N/A cancel attack mission 1 Anything anything (usually the first enemy object they encounter) - utilizes threat rating logic 2 Structures any enemy [BuildingTypes] 3 Ore Miners any enemy [VehicleTypes] with Harvester=yes set 4 Infantry any enemy [InfantryTypes] 5 Vehicles any enemy [VehicleTypes] 6 Factories any enemy [BuildingTypes] with a Factory= setting 7 Base Defenses any enemy [BuildingTypes] with IsBaseDefense=yes set 8 Base Threats any enemy objects approaching (or already in) it's base and which are in an attack mission 9 Power Plants any enemy [BuildingTypes] with positive Power= values set 10 Occupiable any [BuildingTypes] with CanBeOccupied=yes set (usually neutral structures) 11 Tech Buildings any [BuildingTypes] with NeedsEngineer=yes set (usually the NeutralTechBuildings=) 1,n = Attack waypoint, n = waypoint number to attack This instructs the TeamType to use the TaskForce to attack the waypoint number specified by the second parameter. If any members have Infiltrate=yes set they will enter the structure at the waypoint. Members with Engineer=yes set will capture the structure provided it does not have Capturable=no set or if it has NeedsEngineer=yes set. Members with Agent=yes set will spy on the structure if it has Spyable=yes set. Members that do not have Assaulter=no set will garrison the structure if it has CanBeOccupied=yes set. Members with C4=yes set will blow up the structure if does not have CanC4=no set. If there is no building at the specified waypoint, the TaskForce will move to the waypoint and will just remain in their last mission. Waypoints are used to define specific places (cells) on the map - see the Map Editing Guide for a detailed explanation of waypoints. At this point however, it's worth noting that Red Alert 2 usually assigns waypoint number 98 to define the place where the player starts in single player games (also known as the 'home cell'), waypoint number 99 for the center of the map, and waypoint numbers 0 - 7 to define the starting places for the 8 players. 2,n = Change grouping to, n = grouping This is residual from Red Alert and may be obsolete in Red Alert 2 - it can even cause internal errors if used. This is because, unlike Red Alert and Tiberium Dawn, cells can only be occupied by one unit thus cannot always attain the predefined formations, and also units now comprise of VXLs as well as SHPs which means they have more possible facings. I have seen this work on occasion (only on SHP units when placed before a move or attack command) but is largely unreliable and should be avoided. It instructs the TaskForce to change it's Group= to the one specified by the second parameter, which can be any of the following;- -1 Default All units assume their default movement and facing settings 0 None Nothing, units remain as they were when created 1 Tight Close grouping, fast units slow down so slower units keep up 2 Loose Loose grouping, units move at their own default Speed= 3 T-North Units form a triangle pointing North 4 T-East Units form a triangle pointing East 5 T-South Units form a triangle pointing South 6 T-West Units form a triangle pointing West 7 Line NS Units form a line from North to South 8 Line EW Units form a line from East to West 9 North Units face North 10 East Units face East 11 South Units face South 12 West Units face West 13 Land Hover units 'land' (only for those units with the 'Hover' locomotor CLSID) 3,n = Move to waypoint, n = waypoint number to move to This instructs the TeamType to use the TaskForce to move to the waypoint number specified by the second parameter. Waypoints are used to define specific places (cells) on the map - see the Map Editing Guide for a detailed explanation of waypoints. At this point however, it's worth noting that Red Alert 2 usually assigns waypoint number 98 to define the place where the player starts in single player games (also known as the 'home cell'), waypoint number 99 for the center of the map, and waypoint numbers 0 - 7 to define the starting places for the 8 players. 4,n = Move into specific celltag, n = celltag to move into This instructs the TeamType to use the TaskForce to move into the CellTag specified by the second parameter. This is used when you want the TeamType to trigger a specific Action (when the game tests for the CellTag being entered). CellTags are attached to cells and are used to trigger Events and thus fire Actions when that cell is entered by a unit (or any unit from the TaskForce). The CellTag parameter should be the waypoint parameter for that CellTag from the [CellTags]listing in the map file, hence this script action is only of use on specific map files. See the Map Editing Guide for a detailed explanation of CellTags and their use. 5,n = Guard area, n = time to guard area in tenths of a minute (multiples of 6 seconds) This instructs the TeamType to put the TaskForce into Guard Mode (same effect as selecting a group of units and pressing the Guard Mode key as defined in KEYBOARD.INI or clicking the relevant button on the Advanced Command Bar). Units will move to attack enemy units that fall within their Sight= range. 6,n = Jump to script action, n = number of script action to jump to This is used to repeat actions within the ScriptType. The second parameter is the action number of the ScriptType that you want to jump to. Remember that the first action of a ScriptType is numbered 0 so if you jump to this (by using n=6,0 for example) you get the TaskForce to repeat all the commands it has, looping forever. This is used by the waypoint system in the game for setting up patrols. You don't have to repeat all the actions as you could jump to say action 3, which would ignore the first three action commands (remember, the numbering starts at 0) and just go to the fourth. 7,0 = Attack TarCom This is a strange command used in all C&C games. The TarCom (or Target Command) is defined as the most recent object to have been targetted by the player (whether that player be human or computer controlled) and is utilized primarily for defense missions (amongst some other things). The object targetted could be anything, and for this reason I would personally avoid use of this - because there can only be one TarCom, the TarCom changes very quickly and frequently as new targets are acquired by different objects (the action of firing clears the TarCom). For example, if a Paradrop plane flew over a computer controlled base, and the computer targetted that plane with it's AA defenses, the TarCom at that point would be the plane (provided nothing else had or was being targetted - remember, the TarCom will change very quickly as the player/computer targets something else). If in this instance you instructed the computer to attack the TarCom, it would use the TeamType to follow the plane and aimlessly attempt to destroy it - in this instance, it would completely fail as it would pursue the plane until it flew off the map, rendering the TeamType useless as it could not continue it's pursuit of the plane. It may seem useful to employ this action to get the computer to continually retarget enemies, although this invariably leads to it's units being destroyed as it spends more time acquiring and pursuing new targets than it does actually firing at them, something which can be observed when you order many of the same unit types to surround and then attack an enemy tank for example. 8,n = Unload, n = type of unloading If the TaskForce contains a unit or units that have a valid Passengers= value set, and those units contain passengers, this command will make the units inside the transport(s) disembark. Note that once the passengers have disembarked, the transport itself is suspended until given a new mission and is therefore no longer considered a part of this TaskForce - this means that you cannot, for example, get units to disembark, do something, then get back into the transport in the same script. The second parameter can be used to ensure that the transport 'deploys' it's cargo correctly (in other words it is within the correct MovementZone= of the unit's inside, as the transports' MovementZone= invariably differs from what it's carrying) although this isn't strictly required (can be left set to 0);- 0 Use this if the transport has MovementZone=Normal (ie standard deployment of pasengers) 1 Use this if the transport has MovementZone=Fly (ie will only deploy passengers when landed) 2 Use this if the transport has MovementZone=Amphibious (ie will only deploy passengers when on land) 9,0 = Deploy If the TaskForce contains a unit or units that are able to deploy (for example a unit which DeploysInto= a [BuildingType] or has any of Deployer=yes, DeployFire=yes, DeployToFire=yes set) then this action causes them to deploy at the current cell they are occupying (same effect as selecting a unit and pressing the Deploy key as defined in KEYBOARD.INI or clicking the relevant button on the Advanced Command Bar). 10,0 = Follow friendlies Residual from Red Alert and appears not to work correctly in Red Alert 2. This command causes the TaskForce to follow the nearest friendly unit when it moves although it will not function as if it is 'guarding' the unit. The following is not permanent, when the TaskForce is assigned another mission it abandons the following. 11,n = Assign new mission, n = new mission type The objects in the TaskForce are all assigned the new mission defined by the second parameter. Not all of them work, some are made obsolete by other action commands, some do not work because an object in the TaskForce may not support that action. Because these are the same 'behaviours' to which objects can be assigned when initially placed on the map some apply only to structures. The following are valid settings for the second parameter, you should refer to the Mission Control section of the RULES.INI Guide for a more detailed explanation of the missions and how they work;- 0 Sleep object sits around and plays dead, will not acquire targets 1 Attack special attack mission used by AI team types (utilizes threat rating logic) 2 Move simply moving to destination 3 QMove special move to destination after other queued moves occur 4 Retreat object runs away (may even leave the map) 5 Guard object sits around and will engage an enemy that falls within it's weapon range 6 Sticky just like guard mode, except the object will engage enemies but not pursue them 7 Enter enter building or transport 8 Capture engineer entry logic used by MultiEngineer 9 Eaten when object has a Parasite= attached (eg Drone, or Dog attacking [InfantryType]) 10 Harvest the loop controlling harvesting of Ore and dumping at a Refinery 11 Area Guard guard the general area where the object starts at 12 Return return to co-ordinating object (eg spawned object returns to the spawner) 13 Stop stop moving or firing at the first available opportunity 14 Ambush standard engineer capture logic 15 Hunt scan for and attack enemies wherever they may be on the map 16 Unload while dropping off cargo (eg Landing Craft unloading passengers) 17 Sabotage unit runs to place C4 on a building or Ivan goes to place bomb on object 18 Construction structures use this when building up after initial placement 19 Selling structures use this for deconstruction after being sold 20 Repair used when repairing an object (eg Service Depot) 21 Rescue special team over-ride mission 22 Missile Nuke Silo special launch missile mission 23 Harmless object doesn't fire and is not considered in any threat scan 24 Open while opening or closing a gate to allow passage 25 Patrol patrol a series of waypoints 26 ParadropApproach object is approaching the paradrop site 27 Paradrop Overfly object is flying over the paradrop site (ie dropping the paratroopers) 28 Wait paused and awaiting next mission 29 Move (special duplicate) used when Chrono units are moving to destination 30 Attack (special duplicate) used when units are deployed to fire (eg weapons with an area fire effect) NOTE: there is a difference when using Area Guard as opposed to Guard. Units with an Area Guard mission are more aggressive and will pursue enemy units that fall within their Sight= range and continue that pursuit until they can attack the target. Then the units will return to their original position unless they catch the target within their initial guard zone (in which case they will attempt to destroy it). Units in an Area Guard mission are not recruited 'from the field' when a create team Action is executed, although units in a standard Guard mission will be gathered to create the new team if they are required. 12,n = Set Global, n = global number to be set The global number specified in the second parameter is defined as being 'set' (it is allocated a value of '1' or 'true'). This should be employed in specific map files only in which the global variable has been defined. This is part of the boolean logic employed by the global variables system in the game engine - refer to the Map Editing Guide for a more detailed explanation of global variables. 13,n = Play SHP sequence, n = sequence number If the TaskForce contains a unit or units that are SHPs (ie infantry) then the relevant SHP sequence is displayed as defined by the frame numbering system in ART.INI. The sequence to display is from the following list;- 0 Ready 1 Prone 2 Walk 3 FireUp 4 Down 5 Crawl 6 Up 7 FireProne 8 Idle1 9 Idle2 10 Die1 11 Die2 12 Die3 13 Die4 14 Die5 15 Tread 16 Swim 17 WetIdle1 18 WetIdle2 19 WetDie1 20 WetDie2 21 WetAttack 22 Tumble 23 FireFly 24 Deploy 25 Deployed 26 DeployedFire 27 DeployedIdle 28 Undeploy 29 Cheer 30 Parardrop 31 AirDeathStart 32 AirDeathFalling 33 AirDeathFinish 34 Panic 14,0 = Load onto transport If the TaskForce contains a unit or units that have a valid Passengers= value set, and units whose Size= and PhysicalSize= settings allow them to be carried by that transport, this command will make the units enter the transport. 15,n = Enter structure at waypoint, n = waypoint number Should be used only for units capable of entering structures and is the script action used to get Engineers to repair bridges. This instructs the TaskForce to enter the structure at the waypoint number specified by the second parameter. If any members have Infiltrate=yes set they will enter the structure at the waypoint. Members with Engineer=yes set will capture the structure provided it does not have Capturable=no set or if it has NeedsEngineer=yes set (they will also repair a destroyed bridge if the structure has BridgeRepairHut=yes set). Members with Agent=yes set will spy on the structure if it has Spyable=yes set. Members that do not have Assaulter=no set will garrison the structure if it has CanBeOccupied=yes set. Members with C4=yes set will blow up the structure if does not have CanC4=no set. If there is no building at the specified waypoint, the TaskForce may not activate correctly and will just remain in their last mission. Waypoints are used to define specific places (cells) on the map - see the Map Editing Guide for a detailed explanation of waypoints. At this point however, it's worth noting that Red Alert 2 usually assigns waypoint number 98 to define the place where the player starts in single player games (also known as the 'home cell'), waypoint number 99 for the center of the map, and waypoint numbers 0 - 7 to define the starting places for the 8 players. 16,n = Patrol to waypoint, n = waypoint number This is similar to Move to waypoint. This instructs the TeamType to use the TaskForce to move to the waypoint number specified by the second parameter. The difference is that the units in the TaskForce will move out of their patrol route to actively go and engage any enemy objects that are within their Sight= as they move to the waypoint. NOTE: this action eats up processor time, because the TaskForce will scan for enemy objects with each movement. If you have a lot of TaskForces (or lots of units in them) engaged in this action, you will experience slowdown in the game - this is one reason why the single player missions are comparatively slow, they use this action a lot. Waypoints are used to define specific places (cells) on the map - see the Map Editing Guide for a detailed explanation of waypoints. At this point however, it's worth noting that Red Alert 2 usually assigns waypoint number 98 to define the place where the player starts in single player games (also known as the 'home cell'), waypoint number 99 for the center of the map, and waypoint numbers 0 - 7 to define the starting places for the 8 players. 17,n = Display Particle System, n = particle system number Unpredictable, this displays one of the games' [ParticleSystems] on the TaskForce. The second parameter is the number of the particle system from the [ParticleSystems] list in RULES.INI (although for this purpose you should consider this list as being numbered starting at 0 instead). 18,n = Display animation, n = animation number This instructs the TaskForce to play one of the games' animation sequences. The second parameter is the number of the animation from an internal table (see the Map Editing Guide). 19,0 = Panic If the TaskForce contains a unit or units that have Fraidycat=yes set then they will run around aimlessly, using the Panic= animation from their sequence as defined in ART.INI. Normally used for the civilian units. Units that do not fulfill this criteria lie down and act as if prone. 20,n = Change house ownership, n = house number of new owner Used in single player missions on specific map files only, this changes ownership of the entire TeamType to the House= number specified by the second parameter. See the Map Editing Guide for details of [Houses] and their numbering. 21,0 = Scatter This instructs the TaskForce to scatter (same effect as selecting a group of units and pressing the Scatter key as defined in KEYBOARD.INI). 22,0 = Afraid This instructs the TaskForce to behave in a passive manner. Similar to Guard Area although the TaskForce will not actively engage in combat, will not acquire targets, and will not retaliate - it will scatter instead. 23,0 = ? Unused 24,n = Play speech from EVA.INI, n = number of speech to play This instructs the TaskForce to play one of the Sofia or EVA voices (depending upon the ParentCountry= of the owner of this TaskForce). The second parameter is the number of the sound to be played from the [DialogList] in the EVA.INI file (note that you should consider this list as being numbered from 0 instead of 1 to get the correct numbering convention). 25,n = Play sound from SOUND.INI, n = number of sound to play This instructs the TaskForce to play one of the generic ingame sounds from the [SoundList] in the SOUND.INI file (note that for all ingame Action and Trigger purposes this number is from an internal table - see the Map Editing Guide). 26,n = ? Unused 27,n = ? Unused 28,n = ? Unused 29,n = ? Unused 30,n = ? Unused 31,0 = Suicide This instructs the TaskForce to destroy itself. In effect it commits suicide, usually accompanied by an explosion. 32,n = ? Unused 33,n = ? Unused 34,n = Center map on task force This will center the screen on the TaskForce. The same effect as hitting the Home key as defined in KEYBOARD.INI when the screen centers on your MCV (or the unit defined by the BaseUnit= statement in RULES.INI). The second parameter determines the speed at which the 'camera' switches view to the TaskForce with 0 being instant. 35,n = Shroud Map for time interval, n = time to remain shrouded This action will shroud the entire map except for the area around the players MCV's (if they have one). The second parameter determines the number of frames for which the map should remain shrouded (1 second = approximately 15 frames) after which the explored areas are revealed again. 36,n = ? Unused, appears to be a duplication of action #25 37,0 = Leave map and delete This forces dissolved members of the TaskForce to leave the map after which they are deleted (for example aerial transports after their passengers have disembarked). 38,n = ? Unused 39,n = Set Global, n = global number to be set The global number specified in the second parameter is defined as being 'set' (it is allocated a value of '1' or 'true'). This should be employed in specific map files only in which the global variable has been defined. This is part of the boolean logic employed by the global variables system in the game engine - refer to the Map Editing Guide for a more detailed explanation of global variables. 40,n = Clear Global, n = global number to be cleared The global number specified in the second parameter is defined as being 'cleared' (it is allocated a value of '0' or 'false'). This should be employed in specific map files only in which the global variable has been defined. This is part of the boolean logic employed by the global variables system in the game engine - refer to the Map Editing Guide for a more detailed explanation of global variables. 41,n = ? Unused 42,n = Change facing, n = new direction to face This instructs the TaskForce to turn and face the new direction specified by the second parameter. The facings are as follows;- 0 North 1 North East 2 East 3 South East 4 South 5 South West 6 West 7 North West 43,0 = Dissolve transport from team This is always used after members of the TaskForce have entered a transport in the same TaskForce and serves two purposes. The effect of this is that the transport will be used to carry out any subsequent movement or deploy actions but after that it is no longer considered a part of this TaskForce and as such is available to be recruited into new TeamTypes. It is this action which enables use of the TransportsReturnOnUnload=yes statement in the corrosponding TeamType entry. The second purpose is to flag the transport as being 'loaded' with passengers and thus is considered in the AI's targetting logic as a potential threat (see the ContentScan= entry in the RULES.INI Guide). 44,0 = Unload TRUCKB > TRUCKA Used purely for a graphical effect and applicable uniquely to the [TRUCKB] unit, this has the effect of converting [TRUCKB] into [TRUCKA] to give the impression that the unit has unloaded it's cargo. NOTE: this is residual from Tiberian Sun and as such may not work correctly since [TRUCKA] refers to the Demo Truck image in Red Alert 2 which has no 'unloaded' image. Changing the image for the Demo Truck and assigning new units to [TRUCKA] and [TRUCKB] enables use of this logic. 45,0 = Load TRUCKA > TRUCKB Used purely for a graphical effect and applicable uniquely to the [TRUCKA] unit, this has the effect of converting [TRUCKA] into [TRUCKB]to give the impression that the unit has been loaded with cargo. NOTE: this is residual from Tiberian Sun and as such may not work correctly since [TRUCKA] refers to the Demo Truck image in Red Alert 2 which has no 'unloaded' image. Changing the image for the Demo Truck and assigning new units to [TRUCKA] and [TRUCKB] enables use of this logic. 46,n = Attack enemy structure, n = structure number (see note below) Members of this TaskForce attack the enemy structure specified by the second parameter. This action depends upon the type of units in the TaskForce and if certain members have Infiltrate=yes set. Members with Engineer=yes set will capture the structure provided it does not have Capturable=no set or if it has NeedsEngineer=yes set. Members with Agent=yes set will spy on the structure if it has Spyable=yes set. Members that do not have Assaulter=no set will garrison the structure if it has CanBeOccupied=yes set. Members with C4=yes set will blow up the structure if does not have CanC4=no set. 47,n = Move to enemy structure, n = structure number (see note below) Members of this TaskForce move and stay adjacent to the enemy structure specified by the second parameter. 48,0 = Scout Unpredictable, appears to cause members of this TaskForce to move to some pre-determined point on the map in an attempt to scout an area although how this point is determined is not certain. The route taken is not always the direct one. 49,0 = Repeat until 0 This is typically used after an Attack Target instruction. This forces the TaskForce to carry out it's previous action in the script continually until all of the target types specified by that previous instruction no longer exist, at which point the TaskForce moves on to the next instruction after this one. The action is continually executed until any condition on it's use can no longer be met (for example if the previous action was Attack Vehicles and all vehicles have been destroyed, the script moves on to the next action). 50,n = Flash (visual effect), n = number of flashes This causes the TaskForce to 'flash', the visual effect you get on an object when you order something to attack it. The second parameter is the number of times to flash the unit 'white'. 51,n= ? Unused 52,n = Display talk bubble, n = talk bubble number Should be used for single-unit TaskForces only, this causes a 'talk bubble' to appear above the unit. The second parameter determines which type of talk bubble to display;- 1 * general speech 2 ? question 3 ! shouting or statement Note that the length of time for which the talk bubble is displayed is controlled through the TalkBubbleTime= statement in RULES.INI - refer to the RULES.INI Guide for details of this and the steps to take to enable it's inclusion in Red Alert 2 as this remains residual from Tiberian Sun:Firestorm. 53,0 = Regroup (gather at friendly base) This causes the TaskForce to regroup, if for example any of it's members have become engaged in a base defense mission or strayed away whilst in guard mode, or even the TeamType itself has been suspended for whatever reason. The members regroup directly next to each other leaving no 'gaps' at the nearest available point with sufficient space, and is used, for example, prior to activating the Iron Curtain so that all applicable members are affected (ie they fall within it's range of effect). 54,0 = Gather (at enemy base) This causes the TaskForce to gather together (sometimes used when members of the TaskForce move at different speeds and you want the faster ones to stop while the slower ones catch up) after the previous action has been executed. If the TaskForce is in an attack mission and moving towards an enemy base, this command is usually executed when the first member of the TaskForce reaches the distance from that base defined by the AISafeDistance= statement in RULES.INI - see the RULES.INI Guide. 55,0 = Activate Iron Curtain on task force If the owner of the TaskForce to which this ScriptType is attached also has the Iron Curtain fully charged then it will be fired at this TaskForce. Note that the use of the Iron Curtain in this manner depends on the percentage chance of the AI incorporating them into it's actions as defined by the AIMinorSuperReadyPercent= statement in RULES.INI - see the RULES.INI Guide for more details. 56,n = ? Unused 57,n = Chronoshift task force, n = structure number to be Chronoshifted to (see note below) If the owner of the TaskForce to which this ScriptType is attached also has the Chronosphere fully charged then it will be used on the TaskForce to shift them to the enemy structure number specified in the second parameter before moving on to the next action. Note that the use of the Chronosphere in this manner depends on the percentage chance of the AI incorporating them into it's actions as defined by the AIMinorSuperReadyPercent= statement in RULES.INI - see the RULES.INI Guide for more details. 58,n = Move to friendly structure, n = structure number (see note below) Members of this TaskForce move and stay adjacent to the friendly structure specified by the second parameter. The structure can be one owned by the owner of the TaskForce or any of it's allies. [TeamTypes] This section defines the TeamTypes, which connect a ScriptType with a TaskForce while adding some generic behaviour parameters (ie behaviours which apply to every member of the TaskForce) whether they are how the TeamType is created, or how it behaves after it has been created. These behavioural modifiers make it difficult to entirely predict or determine the TeamTypes behaviour. The maximum number of TeamTypes which can be in existance at any one time is controlled with the TotalAITeamCap= statement in RULES.INI - refer to the RULES.INI Guide for a more detailed explanation of this and many other statements relating to the AI. These can be created in any of several ways;- within individual map files by an Action when some pre-determined condition is met by the game code (known as an Event) - see the Map Editing Guide when a generic game event occurs that that may not be specific to a particular map, scenario or House (known as an AITriggerType, again these can be employed and even defined in individual map files) based on time rather than an Event or a Trigger, the TeamType is automatically created and used, known as Autocreate - this process is inherent in the game code in skirmish games with the frequency of this process being controlled by the TeamDelays= statement in RULES.INI (see the RULES.INI Guide). In map files, you must trigger this process yourself through the relevant Action (see the Map Editing Guide). The section takes the form of a list of all TeamTypes. The list is numbered starting at 0, new ones should be simply added to the end of the list. Each entry in the list takes the form of a hexadecimal numbered string which is the unique identifier for each of the TeamTypes - like other lists in the INI files, the game code requires that each entry in this list is defined with it's own section in this file. For convention, it is wise to stick to this hex numbering system although again this is not strictly necessary. The following statements can be used;- Name= This is simply a string name used for identification purposes only, it is not required by the game, although it is useful to leave this in for debugging and troubleshooting your AI.INI file - as a point of interest, this statement does not even get parsed. VeteranLevel= Is used to determine the level of 'veterancy' that each member of the TaskForce used by this TeamType has. Use 1 for 'Little Experience' (default), 2 for 'Veteran' and 3 for 'Elite'. Higher numbers can be used if you edit RULES.INI - see the Veteran Factors section of the RULES.INI Guide for more details. Loadable= Can be set to 'yes' or 'no' and is used to determine if the associated TaskForce should reload when any of it's members run out of Ammo= . This is required in case a particular unit has to dock with a co-ordinating structure to reload, a process which is a mission in itself and thus could interrupt (and possibly cause havoc with) the actions for the TeamType as defined by the associated ScriptType as 'nesting' missions in this manner could cause internal errors - objects can only be in one mission at a time. This logic is residual from Red Alert (where it was used primarily for the Mine Layer code) and may be obsolete in Red Alert 2. Full= Should be used only in map files, this can be set to 'yes' or 'no' and determines if any units within the associated TaskForce should be initially 'full' as determined by the Storage= statement in their RULES.INI entry (this applies only to Ore Miners in Red Alert 2). If the TaskForce contains a Transport and other units, the units are automatically placed in the Transport for reinforcement purposes. Annoyance= Can be set to 'yes' or 'no' and is used to determine if destroyed members of the associated TaskForce are automatically replaced by the AI and allocated the same ScriptType, the supposed effect being that this TeamType annoys the player with it's persistence. GuardSlower= Can be set to 'yes' or 'no' and has the effect of increasing the default value of BaseDefenseDelay= as defined in RULES.INI specific to this TeamType so that members of the associated TaskForce in a base defense mission take longer to respond to any threats to themselves or any objects they are guarding. The factor by which that value is increased has not been determined. House= Should be used within map files and simply defines the House= to which ownership of this TeamType is automatically passed upon creation. For general AI.INI TeamTypes this should be set to <none>. Recruiter= Can be set to 'yes' or 'no' and determines if this TeamType can be created by using any objects required to assemble the associated TaskForce that already exist on the map (provided they are not already part of an existing TeamType). Autocreate= Can be set to 'yes' or 'no' and specifies whether or not this TeamType should be created based on time rather than any form of trigger. The AI.INI file usually defaults to 'no' - this is because a TeamType with Autocreate=yes set is, obviously, subject to being automatically created. Each House= can, independantly, have this function activated through the relevant Action within a map file. As mentioned above, the frequency of this process is controlled by the TeamDelays= statement in RULES.INI (see the RULES.INI Guide). Prebuild= Can be set to 'yes' or 'no' and determines if an inactive duplicate of the associated TaskForce should be created before it may be needed. This is used in case the TeamType has a high Priority= setting so that the AI has a backup should the original be destroyed (useful if the TaskForce contains an object which is expensive or takes a long time to produce). This is how the AI can sometimes appear to produce expensive units very quickly in some single player missions. Reinforce= Used in map files only for single player missions, this can be set to 'yes' or 'no' and determines if this TeamType forms reinforcements, in other words if set to 'yes' then the TeamType is expected to be created from off the map rather than on it. Droppod= Can be set to 'yes' or 'no' and appears to be linked to and used by the Paradrop logic in Red Alert 2. This should be set to 'yes' if the TeamType will enter the game through a Paradrop (although there are other ways of achieving this effect). UseTransportOrigin= Can be set to 'yes' or 'no' and determines whether or not this TeamType should be created at the point of origin of it's transport, if the transport itself already exists and has been recruited into this TeamType. This is used in map files to create reinforcement teams from off the map that will arrive on a transport. Whiner= Can be set to 'yes' or 'no' and is used only by 'pool' TeamTypes (see AITriggerTypes) to determine if destroyed members of the associated TaskForce are automatically replaced by the AI. This is because 'pool' TeamTypes are normally assigned to base defense missions or generic missions such as guarding, hunting or scouting. LooseRecruit= Can be set to 'yes' or 'no' and determines whether or not this TeamType should be dissolved after completion of it's assigned ScriptType if that mission was successful (in other words the members of it's associated TaskForce are then free to be recruited into another TeamType). Aggressive= The TeamType will execute orders regardless of enemy action and will not stop to engage in combat with enemy objects, although it may retaliate and return fire on the way. The supposed effect is that the associated TaskForce will doggedly aspire to complete it's assigned ScriptType. Suicide= The TeamType will execute orders regardless of enemy action and will not stop to engage in combat with enemy objects and will not retaliate or return fire. It will ignore Sight= ranges and the GuardRange= of any enemy objects and will not be recruited into any subsequently created TeamTypes on the presumption that it's associated ScriptType will invariably lead to the destruction of the associated TaskForce. Priority= This is used to determine the priority of this TeamType being chosen for creation when the AI is deciding what to do next. The lower the number, the greater the likelihood of the AI using this TeamType above others. For simplicity, Red Alert 2 uses multiples of 5 for this setting (Tiberian Sun used multiples of 4) so it is best to stick with this convention although other values between 1 and 50 can be used. Note that the setting of the SuspendPriority= statement in RULES.INI uses this value to determine whether or not this TeamType will be suspended during base defense missions (see the RULES.INI Guide for more details). Max= This serves two purposes. Firstly, it serves as a trigger to create the TeamType - when set to '1', it will automatically be created by the AI regardless of whether or not it is already triggered for creation through an AITriggerType or otherwise only if IsBaseDefense=no is set for this TeamType (see below). Secondly, it serves to indicate the maximum number of instances of this TeamType that can exist at the same time only if Autocreate=yes has been set for this TeamType (see above). TechLevel= This is obsolete in Red Alert 2 and is unused. In previous C&C games, this was used as a method of restricting AI auto production by determining the lowest TechLevel= at which this team could be employed by the AI, however the TechLevel= setting in Red Alert 2 has become all but obsolete as this can no longer be determined by players. Leave this set to it's default of 0. Group= This is used to determine the default grouping that this TeamType should strive to attain if and when it is not otherwise set or changed. A value of -1 (which is all Red Alert 2 ever uses) simply means 'default' which makes all of the units move and face as they would when left alone. Values other than that may be residual from Red Alert and cause problems (see the Change Grouping entry of the [ScriptTypes] section for more detailed information on groupings, their settings and this inherent problem). Tag= Used in map files only, this is used to determine which of the [Tags] is attached to this TeamType if there is a map-specific Event and Action attached to it (eg it gets destroyed or should be created). See the Map Editing Guide for further details on [Tags] and their use. Waypoint= Used in map files only, this is used to determine the waypoint at which the TeamType is to appear. You should ensure that the waypoint you specify here is included in the [Waypoints]section of the map file. See the Map Editing Guide for a detailed explanation of waypoints. OnTransOnly= Can be set to 'yes' or 'no' and determines whether or not this TeamType should only execute it's associated ScriptType if that ScriptType contains a 'load on transports' action. If that action is not successfully completed, the TeamType is dissolved and the members of the associated TaskForce are made available for recruitment into further TeamTypes . This is used to ensure that the TaskForce only carries out it's mission if it has a transport or can be transported (as it may depend upon it). TransportWaypoint= Used in map files only. Can be set to 'yes' or 'no' and specifies the waypoint at which the transport for this TeamType is created if it's at a seperate place to the rest of the TeamType. AvoidThreats= Can be set to 'yes' or 'no' and determines whether or not this TeamType should take evasive action, meaning it will avoid, where possible, Sight= ranges and the GuardRange= of any enemy objects. IonImmune= Can be set to 'yes' or 'no' and determines whether or not members of the associated TaskForce are immune to the effects of Weather Storms. This is probably obsolete in Red Alert 2 as it is residual from Tiberian Sun, where the occurance of an Ion Storm would instantly destroy any airborn objects - this tag would nullify that effect for this TeamType. TransportsReturnOnUnload= Can be set to 'yes' or 'no' and determines whether or not any transports within the associated TaskForce should return to their point of origin upon deployment of their contents provided they have been released from that TaskForce by use of the 'dissolve transport' action (see above). The purpose of this is primarily due to the fact that most transports are unarmed and thus unable to carry out any other mission, so by returning to their point of origin they are made immediately available for recruitment into further TeamTypes. AreTeamMembersRecruitable= Can be set to 'yes' or 'no' and determines whether or not members of the associated TaskForce are available to be recruited into further TeamTypes when they have completed the actions detailed in the associated ScriptType. This is used because you can't actually recruit units that are already in a TeamType. IsBaseDefense= Used only for 'pool' teams (see AITriggerTypes). Can be set to 'yes' or 'no' and determines whether or not this TeamType should assume a base defense mission based on the actions detailed in it's associated ScriptType. The number of TeamTypes which can be assigned to this at any one time is controlled by the MinimumAIDefensiveTeams= and MaximumAIDefensiveTeams= statements in RULES.INI (see the RULES.INI Guide). OnlyTargetHouseEnemy= Can be set to 'yes' or 'no' and determines whether or not members of the associated TaskForce will also attack 'neutral' units (eg civilians or other objects belonging to a House= with Side=Neutral set) and consider such objects in it's threat scan. Script= The unique identifier name used to determine the ScriptType to use for this TeamType and should also be contained in the [ScriptTypes]list and have it's own section defined. TaskForce= The unique identifier name used to determine the TaskForce to use for this TeamType and should also be contained in the [TaskForces]list and have it's own section defined. [AITriggerTypes] This section defines which of the TeamTypes should automatically be created either in response to specific game events or other triggers in the game. Most of these are created by the AI in an attempt to ensure that it always deals with certain things, for example 'it's a good idea to destroy an enemy Nuke Silo' or 'it would be good to capture or destroy the enemy Construction Yard'. In effect, this section is the very essence of the scripted AI and relatively little is known of it outside of Westwood Studios. This section simply forms a list of each AITriggerType and in a break with convention it is not numbered and each entry contains it's own data. Note that this may partly be due to the fact that individual AITriggerTypes listed here can each be enabled or disabled through map files (see the Map Editing Guide) so for example, the computer will not waste time and resources building a TeamType specifically to capture your Construction Yard if you can't even acquire one in the mission. Each entry takes the following format;- [ID]= A,B,C,D,E,F,G,XX.000000,YY.000000,ZZ.000000,X,0,Y,0,H,D1,D2,D3 [ID] Takes the form of a hexadecimal numbered string which is the unique identifier for this AITriggerType. DO NOT change this as the [AITriggerTypesEnable] section in most map files depends upon these values in order to enable/disable this particular AITriggerType as required. If you want to add or modify one, copy an existing one and add it to the end of the list with a new ID. A = Name This is simply a string name used for identification purposes only. In this section, you should leave this in. B = TeamType Determines which of the TeamTypes should be used for the actions associated with this trigger. If a TeamType is not required then this should be set to <none>. C = Owner Determines which House or Country is associated with using this trigger. This is to ensure, for example, that Soviet armies do not use TeamTypes containing Allied units and vice versa as this serves as an override to the Owner= statement for each object in RULES.INI. You should set this to <all> if it pertains to no particular or specific House=. D = TechLevel Determines the lowest TechLevel= setting which is required in order for this trigger to be used. Although the TechLevel= setting is partly useless in Red Alert 2, this is related to the 'set tech level' trigger in map files which can be used to ensure that certain, more powerful units are not used by the AI on early missions in campaign games. E = Direction The direction in which the TeamType should initially travel and is used (with varying degrees of success due to the differences in terrain between maps) to ensure the AI does not always attack from the same direction. This should always be '0' for [BuildingTypes]. The directions are as follows;- 0 North 1 North East 2 East 3 South East 4 South 5 South West 6 West 7 North West F = Target Type Determines which object in the game will cause the AI to use this trigger. Should be any object from the [BuildingTypes],[InfantryTypes],[VehicleTypes] or [AircraftTypes]lists from RULES.INI. G Determines what to do in response to the existance of the target type defined in parameter 'F' (above). Takes the following format;- XAXXXXXXXBXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX A holds the quantity of the target type defined by parameter 'F' that must exist for the trigger to be fired. B holds a value between 0 and 5 thus;- 5 = fire the trigger if quantity A has been destroyed 4 = 3 = fire the trigger if quantity A exists 2 = 1 = 0 = fire the trigger when any event occurs XX.000000 = Weighted probability This determines the percentage probability that this AITriggerType will be used when enabled on the easiest difficulty setting (by setting the D1 parameter to 1) so that a weighted distribution of triggers is employed rather than all of them being executed one at a time as if in a list. High values such as 5000.000000 are used to ensure absolute certainty. The 'predictability' of the Red Alert 2 AI is due partly to the fact that the same values (10, 20, 40, 50, 70, 500, 5000) are usually employed throughout the triggers. YY.000000 = Weighted probability This determines the percentage probability that this AITriggerType will be used when enabled on the medium difficulty setting (by setting the D2 parameter to 1) so that a weighted distribution of triggers is employed rather than all of them being executed one at a time as if in a list. High values such as 5000.000000 are used to ensure absolute certainty. The 'predictability' of the Red Alert 2 AI is due partly to the fact that the same values (10, 20, 40, 50, 70, 500, 5000) are usually employed throughout the triggers. ZZ.000000 = Weighted probability This determines the percentage probability that this AITriggerType will be used when enabled on the hardest difficulty setting (by setting the D3 parameter to 1) so that a weighted distribution of triggers is employed rather than all of them being executed one at a time as if in a list. High values such as 5000.000000 are used to ensure absolute certainty. The 'predictability' of the Red Alert 2 AI is due partly to the fact that the same values (10, 20, 40, 50, 70, 500, 5000) are usually employed throughout the triggers. X,0,Y,0 = Side Ownership This set of values is what gives ownership of the trigger itself to a particular Side=, since several Houses= could belong to the same Side=. This is what enables generic scripts to be used, for example any Soviet army to create Dogs to guard against Spies rather than, say, just Russia. The value of 'Y' should be set to 1 if this AITriggerType applies to an Allied army and 2 if it applies to a Soviet army. The value of 'X' is always set to 1 which appears to mean that a target type (as defined in parameter 'F') is targetted for attack, although this seems to allow the AI to build units outside of any Prerequisite= requirements. H = Support TeamType This is what gives the AI some degree of 'smartness' - if the AI simply used the AITriggerTypes without this, it would appear to be boring and predictable as all it would effectively be doing is sending a series of attacks at the players 'list fashion'. This second TeamType is used if, for whatever reason, the first TeamType comes under attack or is otherwise deemed as being likely to fail it's associated ScriptType. In that instance, this second TeamType is despatched to support the first, either by eliminating the threat to it or by attacking something else in a bid to create a distraction. This second TeamType is sometimes despatched prior to the first - for example the second TeamType could be instructed to destroy any AA defenses prior to the first being an air-ground assault. This is a much under-utilized feature which allows for the possibility of combined assaults on players. D1 = Difficulty #1 Flag which should be set to 1 or 0 and indicates if this AITriggerType can be used on the easiest (or Easy) skill level setting in the game. D2 = Difficulty #2 Flag which should be set to 1 or 0 and indicates if this AITriggerType can be used on the medium (or Normal) skill level setting in the game. D2 - Difficulty #3 Flag which should be set to 1 or 0 and represents of this AITriggerType can be used on the hardest (or Brutal) skill level setting in the game. Example 1: This is a simple example. Here I�ve added my units to the teamtype already set in the game. Original Team: [0D08447C-G] Name=10 Gi�s 0=10,E1 Group=-1 New Team: [0D08447C-G] Name=10 GIs,3 Marine,3 Shock,2 Flak Infantry 0=10,E1 1=3,MARINE 2=3,SHOCK 3=2,E11 Group=-1 Example 2: This is an example I used in my mod. Feel free to use it in yours. The AI will build more than one mcv and defend it. 1. 1. Add these to the task force section and add them to the end of the task force list: [043F289C-G] Name=1 Allied MCV 0=1,AMCV Group=-1 [043F863C-G] Name=1 Soviet MCV 0=1,SMCV Group=-1 2. Next, add this to the script section and end of the script list: [043F23CC-G] Name=General MCV Deploy 0=54,0 1=9,0 2=49,0 3. Add these two teams to the team section and to the end of the teamtypes list: [043F29AC-G] Name=Allied MCV VeteranLevel=1 Loadable=no Full=no Annoyance=no GuardSlower=no House= Recruiter=no Autocreate=yes Prebuild=no Reinforce=no Droppod=no UseTransportOrigin=no Whiner=no LooseRecruit=no Aggressive=no Suicide=yes Priority=5 Max=1 TechLevel=0 Group=-1 OnTransOnly=no AvoidThreats=yes IonImmune=no TransportsReturnOnUnload=no AreTeamMembersRecruitable=yes IsBaseDefense=no OnlyTargetHouseEnemy=no Script=043F23CC-G TaskForce=043F289C-G [043F83EC-G] Name=Soviet MCV VeteranLevel=1 Loadable=no Full=no Annoyance=no GuardSlower=no House= Recruiter=no Autocreate=yes Prebuild=no Reinforce=no Droppod=no UseTransportOrigin=no Whiner=no LooseRecruit=no Aggressive=no Suicide=yes Priority=5 Max=1 TechLevel=0 Group=-1 OnTransOnly=no AvoidThreats=yes IonImmune=no TransportsReturnOnUnload=no AreTeamMembersRecruitable=yes IsBaseDefense=no OnlyTargetHouseEnemy=no Script=043F23CC-G TaskForce=043F863C-G Finally, add these two triggers to the end of the trigger section (Note that there is not a trigger list to add the trigger names to): 043F874C-G=Allied MCV,043F29AC-G,,10,1,GACNST,0200000002000000000000000000000000000000000000000000000000000000,100.000000,500.000000,1000.000000,1,0,1,0,,1,11,1 043F40BC-G=Soviet MCV,043F83EC-G,,10,1,NACNST,0200000002000000000000000000000000000000000000000000000000000000,100.000000,500.000000,1000.000000,1,0,2,0,,1,1,1 Note that these triggers should be put on one line in the ai.ini just like the other triggers. I didn�t have space so I fit them like this here. Contact/Issues Part of this AI is an extract from the tutorials by Deezire. Also thanks to Avizoa for help. To contact me: My Email: harisikram@hotmail.com My Site: www.racom.homestead.com

Hosted by www.Geocities.ws