Input - Revision history

Davemark: /* Implementation */

2024-02-06T17:41:14Z

Implementation

← Older revision		Revision as of 17:41, 6 February 2024
Line 8:		Line 8:

	=== Code ===		=== Code ===
	Inputs are defined in data and, when exported from the database, are listed in the Enums file under ConsiderationInput.		Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under '''ConsiderationInput'''.

	Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)		Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)

Davemark: More info

2024-02-06T17:35:57Z

More info

← Older revision		Revision as of 17:35, 6 February 2024
Line 5:		Line 5:
	An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap\|Influence Map]] system, or anything else that can provide something that is measurable.		An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap\|Influence Map]] system, or anything else that can provide something that is measurable.

	Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under ~~'''~~ConsiderationInput~~'''~~.		== Implementation ==

			=== Code ===
			Inputs are defined in data and, when exported from the database, are listed in the Enums file under ConsiderationInput.

	Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)		Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)

Davemark: More info

2024-02-06T17:35:41Z

More info

← Older revision		Revision as of 17:35, 6 February 2024
Line 5:		Line 5:
	An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap\|Influence Map]] system, or anything else that can provide something that is measurable.		An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap\|Influence Map]] system, or anything else that can provide something that is measurable.

	~~== Implementation ==~~		Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under '''ConsiderationInput'''.

	~~=== Code ===~~
	Inputs are defined in data and, when exported from the database, are listed in the Enums file under ConsiderationInput.

	Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)		Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)

Davemark: More info

2024-02-06T17:32:56Z

More info

← Older revision		Revision as of 17:32, 6 February 2024
Line 8:		Line 8:

	=== Code ===		=== Code ===
	Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under ~~'''~~ConsiderationInput~~'''~~.		Inputs are defined in data and, when exported from the database, are listed in the Enums file under ConsiderationInput.

			Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)

Davemark: More info

2024-02-06T17:32:07Z

More info

← Older revision		Revision as of 17:32, 6 February 2024
Line 5:		Line 5:
	An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap\|Influence Map]] system, or anything else that can provide something that is measurable.		An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap\|Influence Map]] system, or anything else that can provide something that is measurable.

			== Implementation ==

	~~== Implementation ==~~
	=== Code ===		=== Code ===
	Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under '''ConsiderationInput'''.		Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under '''ConsiderationInput'''.

	Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)

Davemark at 17:26, 6 February 2024

2024-02-06T17:26:10Z

← Older revision		Revision as of 17:26, 6 February 2024
Line 8:		Line 8:
	== Implementation ==		== Implementation ==
	=== Code ===		=== Code ===
			Inputs are defined in data and, when exported from the database, are listed in the [[Enums]] file under '''ConsiderationInput'''.

			Processing the inputs happens in the consideration code in the method, GetInputValue. This method contains a large case statement with one case for each possible input. The case contains the code for where to retrieve the data specific to that input. Because of this, it is one of the few code changes that has to be made both in initial setup of the IAUS system and during additions and changes. In the former case, the existing inputs will have to be linked to the appropriate objects in the game engine. In the latter case, if a new input is added to the database that is game specific, a corresponding case statement will be necessary in GetInputValue in order for that input to be recognized and its value retrieved. If an input is used that does not have an associated case statement, the default case does not throw a breaking error but the method returns a bad value. (An error statement could easily be placed in the default case.)

Davemark: Initial creation

2024-02-06T17:12:48Z

Initial creation

New page

{{IAUS Header}}
{{Part of Behavior}}
== Concept ==
[[File:Diagram - Consideration.png|400px|thumb|right|Consideration as part of the IAUS structure]]
An '''Input''' is a type of data that is passed through a [[Response Curve]] to get a value that is used to help score a [[behavior]]. In a general sense, it is anything that can be accessed or measured -- either directly or through further calculation. Inputs are usually links to something that is in the game engine, a character or object's information and stats, the [[Imap|Influence Map]] system, or anything else that can provide something that is measurable.

== Implementation ==
=== Code ===