Google Code-in Micro AI Tasks - Revision history

Celtic Minstrel: Candidate for deletion

2022-11-16T03:24:50Z

Candidate for deletion

← Older revision		Revision as of 03:24, 16 November 2022
Line 1:		Line 1:
			{{Delete}}
	This page contains detailed information on the [http://www.google-melange.com/gci/homepage/google/gci2012 Google Code-in 2012] Micro AI Tasks.		This page contains detailed information on the [http://www.google-melange.com/gci/homepage/google/gci2012 Google Code-in 2012] Micro AI Tasks.

Mattsc: Update some links

2016-02-23T17:18:31Z

Update some links

← Older revision		Revision as of 17:18, 23 February 2016
Line 139:		Line 139:
	The AI to be converted is that controlling goblin handler Jabb on Side 3 of the 'Patrols' scenario. The AIs for Konrad and Urudin are not worth converting to Micro AIs.		The AI to be converted is that controlling goblin handler Jabb on Side 3 of the 'Patrols' scenario. The AIs for Konrad and Urudin are not worth converting to Micro AIs.

	'''Important:''' This is a [[~~Lua_AI_Howto~~#Behavior_.28Sticky.29_Candidate_Actions\|Behavior Candidate Action]] (BCA), that is, it attaches to a unit, rather than controlling all (relevant) units of a side. This means that:		'''Important:''' This is a [[Lua_AI_Legacy_Methods_Howto#Behavior_.28Sticky.29_Candidate_Actions\|Behavior Candidate Action]] (BCA), that is, it attaches to a unit, rather than controlling all (relevant) units of a side. This means that:
	* The CA is attached to the unit in an event (not in the side definition) and there are additional keys required when setting up the candidate action (see the [modify_ai] tag in the prestart event).		* The CA is attached to the unit in an event (not in the side definition) and there are additional keys required when setting up the candidate action (see the [modify_ai] tag in the prestart event).
	* ai_type in the [micro_ai] tag needs to start with 'bca_'		* ai_type in the [micro_ai] tag needs to start with 'bca_'
Line 204:		Line 204:
	* The guardian AIs (including a fourth AI that will not be converted to a Micro AI) are all part of Side 2, which means that the [ai] tag in the side definition cannot be deleted.		* The guardian AIs (including a fourth AI that will not be converted to a Micro AI) are all part of Side 2, which means that the [ai] tag in the side definition cannot be deleted.
	* All three guardian AI functions are defined in the same engine file. Thus, the file needs to be copied, rather than moved, to the new location until all three guardian AIs have been converted.		* All three guardian AI functions are defined in the same engine file. Thus, the file needs to be copied, rather than moved, to the new location until all three guardian AIs have been converted.
	* This is a [[~~Lua_AI_Howto~~#Behavior_.28Sticky.29_Candidate_Actions\|Behavior Candidate Action]] (BCA), that is, it attaches to a unit, rather than controlling all (relevant) units of a side. See the comments about BCAs in the description of the [[Google_Code-in_Micro_AI_Tasks#Patrols_.281_AI.29\|Patrols AI]].		* This is a [[Lua_AI_Legacy_Methods_Howto#Behavior_.28Sticky.29_Candidate_Actions\|Behavior Candidate Action]] (BCA), that is, it attaches to a unit, rather than controlling all (relevant) units of a side. See the comments about BCAs in the description of the [[Google_Code-in_Micro_AI_Tasks#Patrols_.281_AI.29\|Patrols AI]].
	* The BCA CA code is included as macros. The macros are defined in file utils/lua_macros.cfg.		* The BCA CA code is included as macros. The macros are defined in file utils/lua_macros.cfg.

Mattsc: /* Animals (7 AIs) */

2012-12-03T18:36:07Z

Animals (7 AIs)

← Older revision		Revision as of 18:36, 3 December 2012
Line 250:		Line 250:
	Step 2 is completed when the parametrization of the dragon Micro AI is complete and has been documented.		Step 2 is completed when the parametrization of the dragon Micro AI is complete and has been documented.

	'''Steps 3a-3f:'''		'''<s>Steps 3a-3f</s>: Completed'''

	Pick any one of the other animal AIs and convert it to a Micro AI. This should be done as a parametrization of the AI that was already converted in Steps 1 and 2, and not by defining a new Micro AI type. Thus, 'ai_type=' should be 'animal' for all animal Micro AIs, and an additional key 'animal_type=' should be added.		Pick any one of the other animal AIs and convert it to a Micro AI. This should be done as a parametrization of the AI that was already converted in Steps 1 and 2, and not by defining a new Micro AI type. Thus, 'ai_type=' should be 'animal' for all animal Micro AIs, and an additional key 'animal_type=' should be added.

Mattsc: /* Lurkers (1 AI) */

2012-12-03T18:35:17Z

Lurkers (1 AI)

← Older revision		Revision as of 18:35, 3 December 2012
Line 160:		Line 160:
	Step 1 is completed when scenario 'Lurkers' uses the [micro_ai] tag and the basic Micro AI has been documented.		Step 1 is completed when scenario 'Lurkers' uses the [micro_ai] tag and the basic Micro AI has been documented.

	'''Step 2:'''		'''<s>Step 2</s>: Completed'''

	Part of the work for Step 2 is figuring out what parameters can be added to the lurker AI to make it more generally useful. Examples could be to make it work for arbitrary unit type and arbitrary terrain.		Part of the work for Step 2 is figuring out what parameters can be added to the lurker AI to make it more generally useful. Examples could be to make it work for arbitrary unit type and arbitrary terrain.

Mattsc: /* Patrols (1 AI) */

2012-12-03T18:34:53Z

Patrols (1 AI)

← Older revision		Revision as of 18:34, 3 December 2012
Line 146:		Line 146:
	Step 1 is completed when scenario 'Patrols' uses the [micro_ai] tag to control Jabb and the basic Micro AI has been documented.		Step 1 is completed when scenario 'Patrols' uses the [micro_ai] tag to control Jabb and the basic Micro AI has been documented.

	'''Step 2:'''		'''<s>Step 2</s>: Completed'''

	Parametrization of this AI involves (at least) making the [micro_ai] tag work for arbitrary units (not just Jabb) and for an arbitrary set of waypoints. The controlled unit should also attack any enemy unit that it ends up next to, not just Jacques.		Parametrization of this AI involves (at least) making the [micro_ai] tag work for arbitrary units (not just Jabb) and for an arbitrary set of waypoints. The controlled unit should also attack any enemy unit that it ends up next to, not just Jacques.

Ubuntor: complete strikethrough

2012-12-01T01:26:26Z

complete strikethrough

← Older revision		Revision as of 01:26, 1 December 2012
Line 135:		Line 135:
	=== Patrols (1 AI) ===		=== Patrols (1 AI) ===

	'''Step 1:'''		'''<s>Step 1</s>: Completed'''

	The AI to be converted is that controlling goblin handler Jabb on Side 3 of the 'Patrols' scenario. The AIs for Konrad and Urudin are not worth converting to Micro AIs.		The AI to be converted is that controlling goblin handler Jabb on Side 3 of the 'Patrols' scenario. The AIs for Konrad and Urudin are not worth converting to Micro AIs.

Mattsc: /* Protect Unit (1 AI) */

2012-11-30T22:42:55Z

Protect Unit (1 AI)

← Older revision		Revision as of 22:42, 30 November 2012
Line 168:		Line 168:
	=== Protect Unit (1 AI) ===		=== Protect Unit (1 AI) ===

	'''Step 1:'''		'''<s>Step 1</s>: Completed'''

	This AI is used in 2 scenarios, 'Protect the Wizard' and 'The Elves Besieged'. The first step of this task involves setting up a Micro AI for scenario 'Protect the Wizard' only. Thus, leave the original engine file in place (copy it, rather than moving it), otherwise 'The Elves Besieged' will stop working.		This AI is used in 2 scenarios, 'Protect the Wizard' and 'The Elves Besieged'. The first step of this task involves setting up a Micro AI for scenario 'Protect the Wizard' only. Thus, leave the original engine file in place (copy it, rather than moving it), otherwise 'The Elves Besieged' will stop working.
Line 176:		Line 176:
	Step 1 is completed when scenario 'Protect the Wizard' uses the [micro_ai] tag and the basic Micro AI has been documented.		Step 1 is completed when scenario 'Protect the Wizard' uses the [micro_ai] tag and the basic Micro AI has been documented.

	'''Step 2:'''		'''<s>Step 2</s>: Completed'''

	Parametrization for this AI is already done in the engine functions, so Step 2 for the 'Protect Unit' scenario mostly involves just setting up the keys and parameter handlers for the parameters. However, scenario 'The Elves Besieged' requires the removal of one of the default AI candidate actions (see the scenario file). Thus, you also need to set up an additional key/parameter that allows for optional removal of this CA.		Parametrization for this AI is already done in the engine functions, so Step 2 for the 'Protect Unit' scenario mostly involves just setting up the keys and parameter handlers for the parameters. However, scenario 'The Elves Besieged' requires the removal of one of the default AI candidate actions (see the scenario file). Thus, you also need to set up an additional key/parameter that allows for optional removal of this CA.

Mattsc: /* Lurkers (1 AI) */

2012-11-30T22:42:32Z

Lurkers (1 AI)

← Older revision		Revision as of 22:42, 30 November 2012
Line 154:		Line 154:
	=== Lurkers (1 AI) ===		=== Lurkers (1 AI) ===

	'''Step 1:'''		'''<s>Step 1</s>: Completed'''

	There are three different lurker AIs in this scenario. The one written in Lua (Side 4) is the AI to be converted to a Micro AI.		There are three different lurker AIs in this scenario. The one written in Lua (Side 4) is the AI to be converted to a Micro AI.

Mattsc: /* Guardians (3 AIs) */

2012-11-30T22:42:05Z

Guardians (3 AIs)

← Older revision		Revision as of 22:42, 30 November 2012
Line 207:		Line 207:
	* The BCA CA code is included as macros. The macros are defined in file utils/lua_macros.cfg.		* The BCA CA code is included as macros. The macros are defined in file utils/lua_macros.cfg.

	'''Step 1:'''		'''<s>Step 1</s>: Completed'''

	Choose one of the three guardian AIs and convert it to a basic Micro AI. For this step, it is sufficient to make the Micro AI work for a single guardian unit (comment out the other unit(s) of the same guardian type in the scenario file) with hard-coded values for the unit ID and other parameters.		Choose one of the three guardian AIs and convert it to a basic Micro AI. For this step, it is sufficient to make the Micro AI work for a single guardian unit (comment out the other unit(s) of the same guardian type in the scenario file) with hard-coded values for the unit ID and other parameters.
Line 213:		Line 213:
	Step 1 is completed when scenario 'Guardians' controls one guardian unit using the [micro_ai] tag and the basic Micro AI has been documented.		Step 1 is completed when scenario 'Guardians' controls one guardian unit using the [micro_ai] tag and the basic Micro AI has been documented.

	'''Step 2:'''		'''<s>Step 2</s>: Completed'''

	Change the guardian Micro AI code so that the hard-coded values of the previous step are configurable keys/parameters in the [micro_ai] tag.		Change the guardian Micro AI code so that the hard-coded values of the previous step are configurable keys/parameters in the [micro_ai] tag.
Line 219:		Line 219:
	Step 2 is completed when several units of the same guardian type are controlled by the Micro AI (using one [micro_ai] tag per unit) in the 'Guardians' scenario and this has been documented.		Step 2 is completed when several units of the same guardian type are controlled by the Micro AI (using one [micro_ai] tag per unit) in the 'Guardians' scenario and this has been documented.

	'''Steps 3a and 3b:'''		'''<s>Steps 3a and 3b</s>: Completed'''

	Pick one of the other guardian AIs and convert it to a Micro AI. This should be done as a parametrization of the AI that was already converted in Steps 1 and 2, and not by defining a new Micro AI type. Thus, 'ai_type=' should be 'guardian' for all guardian Micro AIs, and an additional key 'guardian_type=' should be added.		Pick one of the other guardian AIs and convert it to a Micro AI. This should be done as a parametrization of the AI that was already converted in Steps 1 and 2, and not by defining a new Micro AI type. Thus, 'ai_type=' should be 'guardian' for all guardian Micro AIs, and an additional key 'guardian_type=' should be added.

Mattsc: /* Animals (7 AIs) */

2012-11-30T22:41:20Z

Animals (7 AIs)

← Older revision		Revision as of 22:41, 30 November 2012
Line 238:		Line 238:
	* Side 6 in scenario 'Animals' (wolves AI) contains two aspect definitions in addition to the candidate actions. These aspects need to be made part of the Micro AI as well (and ideally they could be turned on/off with configurable parameters).		* Side 6 in scenario 'Animals' (wolves AI) contains two aspect definitions in addition to the candidate actions. These aspects need to be made part of the Micro AI as well (and ideally they could be turned on/off with configurable parameters).

	'''Step 1:'''		'''<s>Step 1</s>: Completed'''

	Convert the dragon AI to a basic Micro AI. For this step, it is sufficient to use the hard-coded values for the unit ID and other parameters.		Convert the dragon AI to a basic Micro AI. For this step, it is sufficient to use the hard-coded values for the unit ID and other parameters.
Line 244:		Line 244:
	Step 1 is completed when scenario 'Dragon' controls the dragon using the [micro_ai] tag and the basic Micro AI has been documented.		Step 1 is completed when scenario 'Dragon' controls the dragon using the [micro_ai] tag and the basic Micro AI has been documented.

	'''Step 2:'''		'''<s>Step 2</s>: Completed'''

	Change the dragon Micro AI code so that the hard-coded values of the previous step are configurable keys/parameters in the [micro_ai] tag.		Change the dragon Micro AI code so that the hard-coded values of the previous step are configurable keys/parameters in the [micro_ai] tag.