Civ4AutomateInfos: Difference between revisions
(Created page with "The '''Civ4AutomateInfos''' file describes different types of automation that the AI can take over. All tags must be opened and closed; the first is the "open", the second the "...") |
No edit summary |
||
Line 36: | Line 36: | ||
|- | |- | ||
!HotKey | !HotKey | ||
|Unknown | |||
|- | |||
!HotKeyAlt | |||
|Unknown | |Unknown | ||
|- | |- | ||
Line 91: | Line 94: | ||
|- | |- | ||
!bVisible | !bVisible | ||
|Unknown | |Unknown | ||
|} | |} |
Latest revision as of 22:24, 14 January 2013
The Civ4AutomateInfos file describes different types of automation that the AI can take over.
All tags must be opened and closed; the first is the "open", the second the "close" tag. If nothing goes inside a "list tag", then it should just be the opening tag with a "/" before the closing bracket. The following tables contain all available tags, as well as their purpose and accepted values.
This page is missing information. Do not remove this notice until it is complete.
Tags
Headers
These tags typically bracket other tags, sometimes the entire file, and are generally used to specify more than one piece of data.
Tag Name | Description |
---|---|
AutomateInfo | Main bracket for each entry |
Text
Tag Name | Description |
---|---|
Description | Text displayed in game |
Help | Explanation of automation in game |
HotKey | Unknown |
HotKeyAlt | Unknown |
Command | Unknown |
Automate | Unknown |
Integers
All of these tags have a numerical value. Though it sometimes can be negative, it usually is not.
Tag Name | Description |
---|---|
iHotKeyPriority | Unknown |
iHotKeyPriorityAlt | Unknown |
Boolean
All of these can either be 1 (on, or true) or 0 (off, or false). Be careful, as you can wind up with a double-negative, which the game will interpret as "True".
Tag Name | Description |
---|---|
bAltDown | Unknown |
bShiftDown | Unknown |
bCtrlDown | Unknown |
bAltDownAlt | Unknown |
bShiftDownAlt | Unknown |
bCtrlDownAlt | Unknown |
bVisible | Unknown |
Art
These tags are directly related to the rendering of art for the entry.
Tag Name | Description |
---|---|
Button | Button displayed in game |
Example
In the following example of code, please note that there is a specific order of all of the tags. You must list the tags in this order for the game to properly interpret your file.
<AutomateInfo> <Description>TXT_KEY_ACTION_AUTOMATE_BUILD</Description> <Help>TXT_KEY_ACTION_AUTOMATE_BUILD_HELP</Help> <HotKey>KB_A</HotKey> <bAltDown>0</bAltDown> <bShiftDown>0</bShiftDown> <bCtrlDown>0</bCtrlDown> <iHotKeyPriority>0</iHotKeyPriority> <HotKeyAlt/> <bAltDownAlt>0</bAltDownAlt> <bShiftDownAlt>0</bShiftDownAlt> <bCtrlDownAlt>0</bCtrlDownAlt> <iHotKeyPriorityAlt>0</iHotKeyPriorityAlt> <Command>COMMAND_AUTOMATE</Command> <Automate>AUTOMATE_BUILD</Automate> <bVisible>1</bVisible> <Button>Art/Interface/Buttons/Actions/Automate.dds</Button> </AutomateInfo>