Tutorial:Component Context Objects (CCOs) - Revision history

Dux: /* Part 2: CCOs in Context Viewer */

2023-07-12T16:29:01Z

Part 2: CCOs in Context Viewer

← Older revision		Revision as of 12:29, 12 July 2023
Line 34:		Line 34:

	== Part 2: CCOs in Context Viewer ==		== Part 2: CCOs in Context Viewer ==
	[[Tutorial:Context Viewer (Warhammer 3)\|Context Viewer]] is a ~~wonderous~~ tool bequeathed to us by CA that is essential for working with CCOs. If you aren't already familiar with it, stop here and take a moment to read the [[Tutorial:Context Viewer (Warhammer 3)\|linked guide]] on this Wiki, which goes over how to turn it on and get it running.		[[Tutorial:Context Viewer (Warhammer 3)\|Context Viewer]] is a wondrous tool bequeathed to us by CA that is essential for working with CCOs. If you aren't already familiar with it, stop here and take a moment to read the [[Tutorial:Context Viewer (Warhammer 3)\|linked guide]] on this Wiki, which goes over how to turn it on and get it running.

	Got Context Viewer up and running in your game? Great. Let's dive into some CCOs. Context Viewer's most useful feature is that it shows you exactly which CCOs are attached to which UI elements (themselves represented as CCOs here, a specific subtype of CCO called CcoComponent), and it will then show you which options you can run from these CCOs. '''All CCO options do one of two things: Either they extract information from the game and return it, or they send some instruction to the game, altering its state.''' These are referred to as '''Queries''' and '''Commands''' in Context Viewer, respectively.		Got Context Viewer up and running in your game? Great. Let's dive into some CCOs. Context Viewer's most useful feature is that it shows you exactly which CCOs are attached to which UI elements (themselves represented as CCOs here, a specific subtype of CCO called CcoComponent), and it will then show you which options you can run from these CCOs. '''All CCO options do one of two things: Either they extract information from the game and return it, or they send some instruction to the game, altering its state.''' These are referred to as '''Queries''' and '''Commands''' in Context Viewer, respectively.

Dux: /* Using CCO Commands for Campaign Scripting */

2023-07-11T13:55:21Z

Using CCO Commands for Campaign Scripting

← Older revision		Revision as of 09:55, 11 July 2023
Line 205:		Line 205:
	[[File:Cco practical 2.png\|thumb\|Forsaken has been forsaken!]]		[[File:Cco practical 2.png\|thumb\|Forsaken has been forsaken!]]

	One such instance is the scripted disbanding of a unit from an army. If you have the ObjectID of the unit you wish to disband, you can use the cco function to get its CcoCampaignUnit directly and simply call the "Disband" command from there. More often, you'll be starting from the lord leading the army, which is has a CcoCampaignCharacter we can access. For this example, I will disband the first unit of an army. The only information I need to start out with is the CQI of the lord, which is something we can easily get through the model hierarchy.		One such instance is the scripted disbanding of a unit from an army. If you have the ObjectID of the unit you wish to disband, you can use the cco function to get its CcoCampaignUnit directly and simply call the "Disband" command from there. More often, you'll be starting from the lord leading the army, which has a CcoCampaignCharacter we can access. For this example, I will disband the first unit of an army. The only information I need to start out with is the CQI of the lord, which is something we can easily get through the model hierarchy.

	Because CcoCampaignCharacter is one of the direct access-enabled CCOs, we can get it using the cco function. Conveniently, the ObjectID for a CcoCampaignCharacter matches that character's CQI, so once we have that, we can just plug it in:		Because CcoCampaignCharacter is one of the direct access-enabled CCOs, we can get it using the cco function. Conveniently, the ObjectID for a CcoCampaignCharacter matches that character's CQI, so once we have that, we can just plug it in:

Dux: /* Retrieving Campaign Information */

2023-07-11T13:53:34Z

Retrieving Campaign Information

← Older revision		Revision as of 09:53, 11 July 2023
Line 191:		Line 191:
	Campaign CCOs can be used as an alternative to the [https://chadvandy.github.io/tw_modding_resources/WH3/campaign/model_hierarchy.html model hierarchy] for retrieving dynamic information about an active campaign, and in some cases, it's the easier option. One example of this that is currently used as part of [https://steamcommunity.com/sharedfiles/filedetails/?id=2856936614 Community Bugfix Mod] is getting information about "faction initiatives," which is the system that drives the "Gifts of Chaos" feature added with the Champions of Chaos DLC. This system extended the "character initiatives" system, which is what is used to track things like Ogre Big Names. Character initiatives, being older, have documented interfaces in the model hierarchy, but faction initiatives do not. Luckily, we can use CCOs instead:		Campaign CCOs can be used as an alternative to the [https://chadvandy.github.io/tw_modding_resources/WH3/campaign/model_hierarchy.html model hierarchy] for retrieving dynamic information about an active campaign, and in some cases, it's the easier option. One example of this that is currently used as part of [https://steamcommunity.com/sharedfiles/filedetails/?id=2856936614 Community Bugfix Mod] is getting information about "faction initiatives," which is the system that drives the "Gifts of Chaos" feature added with the Champions of Chaos DLC. This system extended the "character initiatives" system, which is what is used to track things like Ogre Big Names. Character initiatives, being older, have documented interfaces in the model hierarchy, but faction initiatives do not. Luckily, we can use CCOs instead:

	~~local faction_cco = cco("CcoCampaignFaction","wh_main_chs_chaos")~~ -- CcoCampaignFaction has direct access support, and the ObjectID matches the faction key		-- CcoCampaignFaction has direct access support, and the ObjectID matches the faction key
			local faction_cco = cco("CcoCampaignFaction","wh_main_chs_chaos")

	local active_undivided_gifts = faction_cco:Call("InitiativeSetList.FirstContext(InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided').ActiveInitiatives.Size")		local active_undivided_gifts = faction_cco:Call("InitiativeSetList.FirstContext(InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided').ActiveInitiatives.Size")

	The above code starts by directly accessing the faction CCO for Archaon's faction (OG Chaos), which is simple enough. It then calls a ~~'''~~context expression~~'''~~ from this CCO interface, which is essentially a series of queries, the result of which is the number of active Undivided initiatives (Gifts of Chaos) that Archaon is currently rolling with. Don't worry if the context expression part of this seems confusing; I will go into [[Tutorial:Component Context Objects (CCOs)#Context_Expressions\|greater detail]] on these in the last section of this guide.		The above code starts by directly accessing the faction CCO for Archaon's faction (OG Chaos), which is simple enough. It then calls a [[Tutorial:Component Context Objects (CCOs)#Context_Expressions\|context expression]] from this CCO interface, which is essentially a series of queries, the result of which is the number of active Undivided initiatives (Gifts of Chaos) that Archaon is currently rolling with. Don't worry if the context expression part of this seems confusing; I will go into [[Tutorial:Component Context Objects (CCOs)#Context_Expressions\|greater detail]] on these in the last section of this guide.

	=== Using CCO Commands for Campaign Scripting ===		=== Using CCO Commands for Campaign Scripting ===

Dux: /* Context Expressions */

2023-07-11T01:42:49Z

Context Expressions

← Older revision		Revision as of 21:42, 10 July 2023
Line 279:		Line 279:

	# We're starting with the CcoCampaignFaction interface for Archaon's faction, which we have assigned to the "faction_cco" variable.		# We're starting with the CcoCampaignFaction interface for Archaon's faction, which we have assigned to the "faction_cco" variable.
	# From here, we call "InitiativeSetList", which returns a CcoContextList containing all of the CcoCampaignInitiativeSet objects for this faction (refer to the subsection on CCO Lists, just above, for more information on these). The period after "InitiativeSetList" indicates that the next query (or command) will be for the CCO that this returns, which in this case is our list.		# From here, we call <code>InitiativeSetList</code>, which returns a CcoContextList containing all of the CcoCampaignInitiativeSet objects for this faction (refer to the subsection on CCO Lists, just above, for more information on these). The period after "InitiativeSetList" indicates that the next query (or command) will be for the CCO that this returns, which in this case is our list.
	# Now at our list, we run the "FirstContext" query, which is a query common to all CCOs of type CcoContextList that takes a secondary context expression as an argument to test each item in the list. It returns the first CCO ("first context") that causes the secondary context expression (<code>InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided'</code> in this instance) to return true. Let's break this down further:		# Now at our list, we run the <code>FirstContext</code> query, which is a query common to all CCOs of type CcoContextList that takes a secondary context expression as an argument to test each item in the list. It returns the first CCO ("first context") that causes the secondary context expression (<code>InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided'</code> in this instance) to return true. Let's break this down further:
	## The secondary context expression is run on each object in the list. In this case, all of these are CcoCampaignInitiativeSet objects.		## The secondary context expression is run on each object in the list. In this case, all of these are CcoCampaignInitiativeSet objects.
	## CcoCampaignInitiativeSet objects have a query ~~for~~ InitiativeSetContext, which returns another CCO, a CcoInitiativeSet'''Record''' (as you recall, CCOs ending in "Record" indicate that they contain database information).		## CcoCampaignInitiativeSet objects have a query <code>InitiativeSetContext</code>, which returns another CCO, a CcoInitiativeSet'''Record''' (as you recall, CCOs ending in "Record" indicate that they contain database information).
	## We call the query "Key" from the CcoInitiativeSetRecord object, which returns the string key from the DB for this particular initiative set. We compare this key to the one we are looking for, "wh3_dlc20_faction_initiative_set_chs_undivided", and if it matches, the test is passed: <code>FirstContext</code> will return this CcoCampaignInitiativeSet object.		## We call the query <code>Key</code> from the CcoInitiativeSetRecord object, which returns the string key from the DB for this particular initiative set. We compare this key to the one we are looking for, "wh3_dlc20_faction_initiative_set_chs_undivided", and if it matches, the test is passed: <code>FirstContext</code> will return this CcoCampaignInitiativeSet object.
	# Now that we've found the right CcoCampaignInitiativeSet, we can run its ActiveInitiatives query.		# Now that we've found the right CcoCampaignInitiativeSet, we can run its <code>ActiveInitiatives</code> query.
	# This query returns ''another'' CcoContextList, this time one that contains CcoCampaignInitiative objects (these represent the individual Gifts of Chaos from the Undivided set)		# This query returns ''another'' CcoContextList, this time one that contains CcoCampaignInitiative objects (these represent the individual Gifts of Chaos from the Undivided set)
	# Since we only care about the number of active initiatives in this example, we simply run the "Size" query on this list, which finally returns what we were after, the number of active Undivided initiatives.		# Since we only care about the number of active initiatives in this example, we simply run the <code>Size</code> query on this list, which finally returns what we were after, the number of active Undivided initiatives.

	This was a bit of a complex example, but I hope it demonstrates just how robust context expression can be (if you want). If you want to practice with context expressions, I have good news: Context Viewer provides a space for just that. The text entry field at the bottom, which was referred to as the "test field" earlier in this document, is built to interpret context expressions and will immediately show you the result (or an error if you get something wrong). Keep in mind that the starting point for these context expressions is whatever page you are currently on in Context Viewer. To test the above example using Context Viewer, for example, you would want to start on the CcoCampaignFaction page for Warhost of the Apocalypse.		This was a bit of a complex example, but I hope it demonstrates just how robust context expression can be (if you want). If you want to practice with context expressions, I have good news: Context Viewer provides a space for just that. The text entry field at the bottom, which was referred to as the "test field" earlier in this document, is built to interpret context expressions and will immediately show you the result (or an error if you get something wrong). Keep in mind that the starting point for these context expressions is whatever page you are currently on in Context Viewer. To test the above example using Context Viewer, for example, you would want to start on the CcoCampaignFaction page for Warhost of the Apocalypse.

Dux: /* CCO Lists */

2023-07-11T01:37:49Z

CCO Lists

← Older revision		Revision as of 21:37, 10 July 2023
Line 251:		Line 251:

	In working with CCOs, you will find that these lists come up quite a bit, so learning how to navigate them is a good idea. Here are the basics:		In working with CCOs, you will find that these lists come up quite a bit, so learning how to navigate them is a good idea. Here are the basics:
	* To select a particular element in the list, simply follow the name of the list with a number in brackets (just as you would do for a table with numeric keys in Lua, with the important caveat that indexing here is zero-based, not one-based). If you want to select the third unit in my unit list, for example, you would write <code>UnitList[2]</code>		* To select a particular element in the list, simply follow the name of the list with a number in brackets (just as you would do for a table with numeric keys in Lua, with the important caveat that indexing here is zero-based, not one-based). If you want to select the third unit in a unit list, for example, you would write <code>UnitList[2]</code>
	* To get a count of the number of elements contained in the list, use the "Size" query: <code>UnitList.Size</code> will return a count of the number of items present in this CcoContextList.		* To get a count of the number of elements contained in the list, use the "Size" query: <code>UnitList.Size</code> will return a count of the number of items present in this CcoContextList.

Line 268:		Line 268:
	end		end

	At the end of our example, our variable <code>total_entities</code> will contain the total number of individual entities in this force.		At the end of our example, our variable <code>total_entities</code> will contain the total number of individual entities in this force.

	=== Context Expressions ===		=== Context Expressions ===

Dux: /* Context Expressions */

2023-07-11T01:32:15Z

Context Expressions

← Older revision		Revision as of 21:32, 10 July 2023
Line 283:		Line 283:
	## The secondary context expression is run on each object in the list. In this case, all of these are CcoCampaignInitiativeSet objects.		## The secondary context expression is run on each object in the list. In this case, all of these are CcoCampaignInitiativeSet objects.
	## CcoCampaignInitiativeSet objects have a query for InitiativeSetContext, which returns another CCO, a CcoInitiativeSet'''Record''' (as you recall, CCOs ending in "Record" indicate that they contain database information).		## CcoCampaignInitiativeSet objects have a query for InitiativeSetContext, which returns another CCO, a CcoInitiativeSet'''Record''' (as you recall, CCOs ending in "Record" indicate that they contain database information).
	## ~~Finally, we~~ call the query "Key" from the CcoInitiativeSetRecord object, which returns the string key from the DB for this particular initiative set. We compare this key to the one we are looking for, "wh3_dlc20_faction_initiative_set_chs_undivided", and if it matches, the test is passed: <code>FirstContext</code> will return this CcoCampaignInitiativeSet object.		## We call the query "Key" from the CcoInitiativeSetRecord object, which returns the string key from the DB for this particular initiative set. We compare this key to the one we are looking for, "wh3_dlc20_faction_initiative_set_chs_undivided", and if it matches, the test is passed: <code>FirstContext</code> will return this CcoCampaignInitiativeSet object.
	# Now that we've found the right CcoCampaignInitiativeSet, we can run its ActiveInitiatives query.		# Now that we've found the right CcoCampaignInitiativeSet, we can run its ActiveInitiatives query.
	# This query returns ''another'' CcoContextList, this time one that contains CcoCampaignInitiative objects (these represent the individual Gifts of Chaos from the Undivided set)		# This query returns ''another'' CcoContextList, this time one that contains CcoCampaignInitiative objects (these represent the individual Gifts of Chaos from the Undivided set)

Dux: /* Direct Access Limitations */

2023-07-11T01:27:35Z

Direct Access Limitations

← Older revision		Revision as of 21:27, 10 July 2023
Line 165:		Line 165:
	*CcoBattleSelection		*CcoBattleSelection
	*CcoBattleUnit		*CcoBattleUnit
	If you attempt to use the cco function with a CCO that is not contained on the list above, it will fail. The ''only way'' to access these other CCOs is through the context system, i.e., via UI components.		If you attempt to use the cco function with a CCO that is not contained on the list above, it will fail. The ''only way'' to access these other CCOs is through the context system, i.e., via UI components or other CCOs which link to the one you want.

	It is also notable that the ObjectID requirement for the cco function is not 100% accurate. You may have noticed that there are asterisks next to CcoCampaignSettlement above. This is because '''the listed ObjectID for CcoCampaignSettlement does not work with the cco function'''. CcoCampaignSettlement interfaces ''can'' be accessed directly, but you need to replace the ObjectID found in Context Viewer with the settlement's CQI on the campaign map. Why is this? I have no idea; it was probably a mistake. Are there others like it? Not that I've found in my personal testing, but I have not gone through them all, so maybe. In any case, just be aware that the cco function was manually programmed to expect a particular data format for a particular set of CCO types, and there is always a chance that it won't match up precisely. You will never need to worry about this when accessing CCOs through the context system.		It is also notable that the ObjectID requirement for the cco function is not 100% accurate. You may have noticed that there are asterisks next to CcoCampaignSettlement above. This is because '''the listed ObjectID for CcoCampaignSettlement does not work with the cco function'''. CcoCampaignSettlement interfaces ''can'' be accessed directly, but you need to replace the ObjectID found in Context Viewer with the settlement's CQI on the campaign map. Why is this? I have no idea; it was probably a mistake. Are there others like it? Not that I've found in my personal testing, but I have not gone through them all, so maybe. In any case, just be aware that the cco function was manually programmed to expect a particular data format for a particular set of CCO types, and there is always a chance that it won't match up precisely. You will never need to worry about this when accessing CCOs through the context system.

Dux: /* Using CCO Commands for Campaign Scripting */

2023-07-11T01:25:14Z

Using CCO Commands for Campaign Scripting

← Older revision		Revision as of 21:25, 10 July 2023
Line 213:		Line 213:
	# We need to get from our Character CCO to its attached CcoCampaignMilitaryForce, which is the CCO for the army. Context Viewer shows us that this can be accomplished using the "MilitaryForceContext" query. (Side note: CcoCampaignMilitaryForce is ''not'' on the list of direct access CCOs, so we could ''not'' have started from here using the cco function).		# We need to get from our Character CCO to its attached CcoCampaignMilitaryForce, which is the CCO for the army. Context Viewer shows us that this can be accomplished using the "MilitaryForceContext" query. (Side note: CcoCampaignMilitaryForce is ''not'' on the list of direct access CCOs, so we could ''not'' have started from here using the cco function).
	# From the Military Force CCO, we need to get a list of units in the army. Context Viewer shows us that this can be accomplished using the "UnitList" query.		# From the Military Force CCO, we need to get a list of units in the army. Context Viewer shows us that this can be accomplished using the "UnitList" query.
	# From the UnitList, we want to select the second (first non-lord) unit, which is represented by [1] because context expressions use [https://en.wikipedia.org/wiki/Zero-based_numbering zero-based indexing] (CCO lists will be discussed in more detail in the final section of this guide).		# From the UnitList, we want to select the second (first non-lord) unit, which is represented by [1] because context expressions use [https://en.wikipedia.org/wiki/Zero-based_numbering zero-based indexing] (CCO lists will be discussed in [[Tutorial:Component Context Objects (CCOs)#CCO_Lists\|more detail]] in the final section of this guide).
	# Finally, having arrived at the Unit CCO (CcoCampaignUnit), we send the "Disband" CCO command, which immediately disbands the unit.		# Finally, having arrived at the Unit CCO (CcoCampaignUnit), we send the "Disband" CCO command, which immediately disbands the unit.
	As a context expression, this is represented as such:		As a context expression, this is represented as such:

Dux: /* Retrieving Campaign Information */

2023-07-11T01:24:11Z

Retrieving Campaign Information

← Older revision		Revision as of 21:24, 10 July 2023
Line 195:		Line 195:
	local active_undivided_gifts = faction_cco:Call("InitiativeSetList.FirstContext(InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided').ActiveInitiatives.Size")		local active_undivided_gifts = faction_cco:Call("InitiativeSetList.FirstContext(InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided').ActiveInitiatives.Size")

	The above code starts by directly accessing the faction CCO for Archaon's faction (OG Chaos), which is simple enough. It then calls a '''context expression''' from this CCO interface, which is essentially a series of queries, the result of which is the number of active Undivided initiatives (Gifts of Chaos) that Archaon is currently rolling with. Don't worry if the context expression part of this seems confusing; I will go into greater detail on these in the last section of this guide.		The above code starts by directly accessing the faction CCO for Archaon's faction (OG Chaos), which is simple enough. It then calls a '''context expression''' from this CCO interface, which is essentially a series of queries, the result of which is the number of active Undivided initiatives (Gifts of Chaos) that Archaon is currently rolling with. Don't worry if the context expression part of this seems confusing; I will go into [[Tutorial:Component Context Objects (CCOs)#Context_Expressions\|greater detail]] on these in the last section of this guide.

	=== Using CCO Commands for Campaign Scripting ===		=== Using CCO Commands for Campaign Scripting ===

Dux: /* Context Expressions */

2023-07-11T01:23:17Z

Context Expressions

← Older revision		Revision as of 21:23, 10 July 2023
Line 274:		Line 274:
	At its simplest, the Call method of a CCO script interface is used to call a single query or command for that CCO. As we've already seen at various places throughout this guide, however, it ''can'' do more than that. What you are really providing as an argument for <code>my_cco:Call</code> (or as the third argument for <code>common.get_context_value</code>) is a '''context expression''', and while this can be a single query or command, it can also chain multiple queries together, some of which can take additional arguments themselves, weaving through the context system from CCO to CCO in order to get to the end point you desire. Once again, we can use Context Viewer as our guide here: Any series of query buttons you click through in Context Viewer can be converted into a context expression, a series of instructions for your script to execute which mirrors that series of clicks.		At its simplest, the Call method of a CCO script interface is used to call a single query or command for that CCO. As we've already seen at various places throughout this guide, however, it ''can'' do more than that. What you are really providing as an argument for <code>my_cco:Call</code> (or as the third argument for <code>common.get_context_value</code>) is a '''context expression''', and while this can be a single query or command, it can also chain multiple queries together, some of which can take additional arguments themselves, weaving through the context system from CCO to CCO in order to get to the end point you desire. Once again, we can use Context Viewer as our guide here: Any series of query buttons you click through in Context Viewer can be converted into a context expression, a series of instructions for your script to execute which mirrors that series of clicks.

	How does it work? It looks complicated at first, but there's a logic to it. You start with a normal CCO query, one which returns another CCO, and then you can select a query or command from ''that'' CCO, delineating these two commands with a period (mimicking "syntax sugar" patterns from Lua). As long as you keep adding queries which return other CCOs, you can continue to do this as many times as you need. Let's return to an [[Tutorial:Component Context Objects (CCOs)#~~Using_CCO_Commands_for_Campaign_Scripting~~\|earlier example]] for getting the number of active Undivided Gifts of Chaos for Archaon's faction, only this time, let's break down the context expression:		How does it work? It looks complicated at first, but there's a logic to it. You start with a normal CCO query, one which returns another CCO, and then you can select a query or command from ''that'' CCO, delineating these two commands with a period (mimicking "syntax sugar" patterns from Lua). As long as you keep adding queries which return other CCOs, you can continue to do this as many times as you need. Let's return to an [[Tutorial:Component Context Objects (CCOs)#Retrieving_Campaign_Information\|earlier example]] for getting the number of active Undivided Gifts of Chaos for Archaon's faction, only this time, let's break down the context expression:

	faction_cco:Call("InitiativeSetList.FirstContext(InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided').ActiveInitiatives.Size")		faction_cco:Call("InitiativeSetList.FirstContext(InitiativeSetContext.Key == 'wh3_dlc20_faction_initiative_set_chs_undivided').ActiveInitiatives.Size")
Line 288:		Line 288:
	# Since we only care about the number of active initiatives in this example, we simply run the "Size" query on this list, which finally returns what we were after, the number of active Undivided initiatives.		# Since we only care about the number of active initiatives in this example, we simply run the "Size" query on this list, which finally returns what we were after, the number of active Undivided initiatives.

	This was a bit of a complex example, but I hope it demonstrates just how robust context expression can be (if you want). If you want to practice with context expressions, I have good news: Context Viewer provides a space for just that. The text entry field at the bottom, which was referred to as the "test field" earlier in this document, is built to interpret context expressions and will immediately show you the result (or an error if you get something wrong). Keep in mind that the starting point for these context expressions is whatever page you are currently on in Context Viewer. To test the above example using Context Viewer, for example, you would want to start on the CcoCampaignFaction page for Warhost of the Apocalypse.		This was a bit of a complex example, but I hope it demonstrates just how robust context expression can be (if you want). If you want to practice with context expressions, I have good news: Context Viewer provides a space for just that. The text entry field at the bottom, which was referred to as the "test field" earlier in this document, is built to interpret context expressions and will immediately show you the result (or an error if you get something wrong). Keep in mind that the starting point for these context expressions is whatever page you are currently on in Context Viewer. To test the above example using Context Viewer, for example, you would want to start on the CcoCampaignFaction page for Warhost of the Apocalypse.

	== Closing Thoughts ==		== Closing Thoughts ==

	CCOs seem quite strange and esoteric at first glance, but I've found that the more I work with them, the more logical and elegant they seem. You certainly won't need to use them all the time, but they are a good tool to add to your scripting toolbox. This guide is by no means an exhaustive account of everything you can do with them, but my hope is that it will provide a solid foundation on the topic for anyone who has been interested. If you have any questions, feel free to reach out to me in Da Modding Den. - Dux		CCOs seem quite strange and esoteric at first glance, but I've found that the more I work with them, the more logical and elegant they seem. You certainly won't need to use them all the time, but they are a good tool to add to your scripting toolbox. This guide is by no means an exhaustive account of everything you can do with them, but my hope is that it will provide a solid foundation on the topic for anyone who has been interested. If you have any questions, feel free to reach out to me in Da Modding Den. - Dux