IAUS - Revision history

Davemark: /* Behavior and Ability Packs */

2023-01-17T14:49:03Z

Behavior and Ability Packs

← Older revision		Revision as of 14:49, 17 January 2023
Line 40:		Line 40:
	=== Behavior and Ability Packs ===		=== Behavior and Ability Packs ===

	Behaviors are contained in [[behavior pack]]s and [[ability pack]]s -- usually by their type of usage. This is ~~both~~ for the sake of convenience when dealing with many behaviors that are designed to go together. However, by doing this, the are able to be added and removed as a group as necessary. Additionally, if a new behavior is added to a Behavior Pack (because it is designed to go with the other behaviors in that pack), then all the [[Brain]]s that contain that Behavior Pack will get the new behavior.		Behaviors are contained in [[behavior pack]]s and [[ability pack]]s -- usually by their type of usage. This is largely for the sake of convenience when dealing with many behaviors that are designed to go together. However, by doing this, the are able to be added and removed as a group as necessary. Additionally, if a new behavior is added to a Behavior Pack (because it is designed to go with the other behaviors in that pack), then all the [[Brain]]s that contain that Behavior Pack will get the new behavior.

	== Installation ==		== Installation ==

Davemark: /* Concept */ Added some description

2021-10-17T01:20:39Z

Concept: Added some description

← Older revision		Revision as of 01:20, 17 October 2021
Line 9:		Line 9:

	The IAUS formalizes this into a complete data-driven architecture that acts in a largely self-contained way such that the only hookups needed are the [[#inputs\|inputs]] from objects in the game engine and [[#outputs\|outputs]] to actions to take in the game engine.		The IAUS formalizes this into a complete data-driven architecture that acts in a largely self-contained way such that the only hookups needed are the [[#inputs\|inputs]] from objects in the game engine and [[#outputs\|outputs]] to actions to take in the game engine.

			Rather than leveraging the traditional "agro system" that is common in many games (in particular, MMOs), the IAUS is constantly making decisions based on what is going on around it. It may take into account things like distance, health, the environment, temperature, time of day, how much of a particular resource is remaining, and many other situational issues.

			Rather than a behavior tree that has a hand prioritized order to process things in, the IAUS is constantly prioritizing things according to all of the inputs on every behavior. This also means that every behavior has the potential to be scored at any time. Obviously, the situation would dictate things that would or would not be available. For example, in the middle of combat an agent probably would not get even remotely close to doing a friendly wave to his ally.

	== Components ==		== Components ==

Davemark: /* Behavior and Ability Packs */

2021-10-08T02:49:11Z

Behavior and Ability Packs

← Older revision		Revision as of 02:49, 8 October 2021
Line 36:		Line 36:
	=== Behavior and Ability Packs ===		=== Behavior and Ability Packs ===

	Behaviors are contained in [[~~Behavior Pack~~]]s and [[~~Ability Pack~~]]s -- usually by their type of usage. This is both for the sake of convenience when dealing with many behaviors that are designed to go together. However, by doing this, the are able to be added and removed as a group as necessary. Additionally, if a new behavior is added to a Behavior Pack (because it is designed to go with the other behaviors in that pack), then all the [[Brain]]s that contain that Behavior Pack will get the new behavior.		Behaviors are contained in [[behavior pack]]s and [[ability pack]]s -- usually by their type of usage. This is both for the sake of convenience when dealing with many behaviors that are designed to go together. However, by doing this, the are able to be added and removed as a group as necessary. Additionally, if a new behavior is added to a Behavior Pack (because it is designed to go with the other behaviors in that pack), then all the [[Brain]]s that contain that Behavior Pack will get the new behavior.

	== Installation ==		== Installation ==

Davemark: /* Concept */

2021-10-08T02:42:51Z

Concept

← Older revision		Revision as of 02:42, 8 October 2021
Line 8:		Line 8:
	The concept behind utility is that we are putting together a score for a particular [[Behavior]] based on how appropriate it is at the time. That is, what utility does this have for the character? Once these scores are assembled, we can pick the behavior with the highest score under the assumption that it is the most beneficial and, therefore, is the most appropriate action to take.		The concept behind utility is that we are putting together a score for a particular [[Behavior]] based on how appropriate it is at the time. That is, what utility does this have for the character? Once these scores are assembled, we can pick the behavior with the highest score under the assumption that it is the most beneficial and, therefore, is the most appropriate action to take.

	The IAUS formalizes this into a complete data-driven architecture that acts in a largely self-contained way such that the only hookups needed are the inputs from objects in the game engine and outputs to actions to take in the game engine.		The IAUS formalizes this into a complete data-driven architecture that acts in a largely self-contained way such that the only hookups needed are the [[#inputs\|inputs]] from objects in the game engine and [[#outputs\|outputs]] to actions to take in the game engine.

	== Components ==		== Components ==

Davemark: /* Behavior Type */

2021-10-08T02:37:55Z

Behavior Type

← Older revision		Revision as of 02:37, 8 October 2021
Line 23:		Line 23:

	=== Behavior Type ===		=== Behavior Type ===
	Each Behavior is linked with a [[Behavior ~~Type~~\|Behavior Type]] that it will execute if the behavior is selected. Behavior ~~Types~~ are the core actions that an agent can perform whereas behaviors are more "reasons why" a particular ~~Behavior Type~~ would be executed. For example, different agent types may have different reasons for engaging in a melee attack. These would be differentiated by each ~~Behavior~~ having different ~~Considerations~~. However, they all ultimately perform the ~~Behavior Type~~, "melee attack". Another wide-ranging example would be the ~~Behavior Type~~, "move to target". Whether we are moving towards an ally, an enemy, an object on the ground, or the tavern across the street, they would all be executed in the same way -- i.e. moving to the target object (as specified in the ~~Context~~ that was scored). Another way of thinking of ~~Behavior Types~~ is as "button presses". That is, there is often an analog to what the player would do in order to execute an action.		Each Behavior is linked with a [[Behavior type\|Behavior Type]] that it will execute if the behavior is selected. Behavior types are the core actions that an agent can perform whereas behaviors are more "reasons why" a particular behavior type would be executed. For example, different agent types may have different reasons for engaging in a melee attack. These would be differentiated by each behavior having different [[consideration]]s. However, they all ultimately perform the behavior type, "melee attack". Another wide-ranging example would be the behavior type, "move to target". Whether we are moving towards an ally, an enemy, an object on the ground, or the tavern across the street, they would all be executed in the same way -- i.e. moving to the target object (as specified in the [[context]] that was scored).

			Another way of thinking of behavior types is as "button presses". That is, there is often an analog to what the player would do in order to execute an action.

	=== Consideration ===		=== Consideration ===

Davemark: /* Brain */

2021-10-08T02:33:53Z

Brain

← Older revision		Revision as of 02:33, 8 October 2021
Line 15:		Line 15:

	=== Brain ===		=== Brain ===
	A [[Brain]] is the top level component that is assigned to an agent in the game. From a data standpoint, a ~~Brain~~ is simply a collection of [[~~Behavior Pack~~]]s and [[~~Ability Pack~~]]s. However, the ~~Brain~~ class contains most of the data for the agent's thinking and does most of the work of scoring Behaviors and keeping track of the history of the Behavior usage.		A [[Brain]] is the top level component that is assigned to an agent in the game. From a data standpoint, a brain is simply a collection of [[behavior pack]]s and [[ability pack]]s. However, the [[brain#Code\|brain class]] contains most of the data for the agent's thinking and does most of the work of scoring Behaviors and keeping track of the history of the Behavior usage.

	=== Behavior ===		=== Behavior ===

Davemark: /* Installation */

2021-10-06T15:16:24Z

Installation

← Older revision		Revision as of 15:16, 6 October 2021
Line 42:		Line 42:

	==== Data Tool ====		==== Data Tool ====

			=== Database ===

	=== Connections ===		=== Connections ===

Davemark: Added footer

2021-10-05T14:01:14Z

Added footer

← Older revision		Revision as of 14:01, 5 October 2021
Line 50:		Line 50:

	== Usage ==		== Usage ==

			{{Manual Footer}}

Davemark at 00:31, 30 September 2021

2021-09-30T00:31:39Z

← Older revision		Revision as of 00:31, 30 September 2021
Line 1:		Line 1:
	{{IAUS Header}}		{{IAUS Header}}

	The Infinite Axis Utility System is the primary behavioral decision-making system in Intrinsic Algorithm's library. While it can be supported by information from other systems (such as the [[Imap]] system or [[Tagging]] system), it is the "brains" of the game agents. This can be applied to individual characters, invisible "team leaders", or even to inanimate objects.		The '''Infinite Axis Utility System (IAUS)''' is the primary behavioral decision-making system in Intrinsic Algorithm's library. While it can be supported by information from other systems (such as the [[Imap]] system or [[Tagging]] system), it is the "brains" of the game agents. This can be applied to individual characters, invisible "team leaders", or even to inanimate objects.

	The IAUS exists as a stand-alone black box that can be installed into a project codebase with minimal work. We have both C++ and C# versions based on the needs to the client. In theory, minus any specific custom language or library issues, this means that this core AI system can be installed on day 1 and work can begin on hooking it up to world information, existing behaviors and animation code, and behavior logic can be authored in the tool we have developed for that purpose.		The IAUS exists as a stand-alone black box that can be installed into a project codebase with minimal work. We have both C++ and C# versions based on the needs to the client. In theory, minus any specific custom language or library issues, this means that this core AI system can be installed on day 1 and work can begin on hooking it up to world information, existing behaviors and animation code, and behavior logic can be authored in the tool we have developed for that purpose.

Davemark: /* Components */

2021-09-29T21:37:07Z

Components

← Older revision		Revision as of 21:37, 29 September 2021
Line 11:		Line 11:

	== Components ==		== Components ==
	[[File:Diagram-Brain.png\|400px\|thumb\|right\|~~Behavior as part of the~~ IAUS structure]]		[[File:Diagram-Brain.png\|400px\|thumb\|right\|The high level IAUS structure]]
	The IAUS system is comprised of a number of high level components. (Each of these contains lower level components that are detailed on their respective pages.)		The IAUS system is comprised of a number of high level components. (Each of these contains lower level components that are detailed on their respective pages.)

Line 35:		Line 35:

	Behaviors are contained in [[Behavior Pack]]s and [[Ability Pack]]s -- usually by their type of usage. This is both for the sake of convenience when dealing with many behaviors that are designed to go together. However, by doing this, the are able to be added and removed as a group as necessary. Additionally, if a new behavior is added to a Behavior Pack (because it is designed to go with the other behaviors in that pack), then all the [[Brain]]s that contain that Behavior Pack will get the new behavior.		Behaviors are contained in [[Behavior Pack]]s and [[Ability Pack]]s -- usually by their type of usage. This is both for the sake of convenience when dealing with many behaviors that are designed to go together. However, by doing this, the are able to be added and removed as a group as necessary. Additionally, if a new behavior is added to a Behavior Pack (because it is designed to go with the other behaviors in that pack), then all the [[Brain]]s that contain that Behavior Pack will get the new behavior.


	== Installation ==		== Installation ==