Last updated: 11/10/98 23:27
A variety of TXT files are present within the TA Unit and Map structure.
AI Text Information |
||||||||||||||||
A good deal of this information came from an AI Tutorial
article by Dave Switeck within the Anniihilation Factory site. I've also made available the text from the AI Tweaking Guide by David Sellick. The ai text files use very simple commands to tell the ai what it can and cannot build. Most such commands only affect 1 specific unit, but there are a few universal values that can be used to affect groups of similar units or units all on one side. Sadly, the universal values aren't as useful as they might seem. Units are refered to by abbreviations made by Cavedog or 3rd party unitmakers. (Within these web pages, this is what has been called the "short name" for the unit. The abbreviation's first 3 letters almost always (except in the case of a few 3rd party units) tell which side the unit is made by - either ARM or COR. And the total length of the unit abbrieviation is 8 letters. First, an example from the original totala1.hpi's ai/default.txt file:
Blah blah blah
I've still discovered a couple tricks with weights and limits to make it LOOK like the ai has some simple do not build till later. If something is weighted VERY low (I.E. Weight ARMGUARD 0.05) then that item will most likely only get built if the construction units/buildings have nothing else they are allowed to build. So when all the resources are finished, THEN my ai is allowed to build guardians which are very expensive metal-wise. Weights seem to work better when placed at the top of the ai profile. Since the ai profile is read from top to bottom, if 2 commands change the same thing then the TOP command would be the one the game uses. All this is not enough information to make a good ai, however. That is best done by trial and error. |
Campaign Briefs Text Information |
|||||
Each mission in a campaign has a mission briefing in which the scenario
and objectives are revealed. This is shown immediately before beginning a mission,
and is typically accompanied by the James-Earl-Jones-Wannabe voice-over. Campaign briefings are placed in a TXT file within the camps/briefs subdirectory, and is given the same filename as the accompanying "useonly" TDF file in the useonly sibling directory under camps. It is a simple text file with no special formatting, as in the following example from the ARM Core Contingency mission 1 briefing:
Within a mission briefing file, the following have special meaning:
|
Docs Text Information |
|
The docs subdirectory typically contains miscellaneous
documentation for units, maps, missions, etc. Although not required, this is a good
place to put your own information and comments about a map, mission, or unit that you have
created. As an example, here is a piece of the TXT file from the Core Thunderbolt:
In general, it is a good idea to include information such as who you are, what the unit is called, what it does, when you'd want to use it, where can it be built, and what does it cost to build the unit. Note: When ZIPping your final UFO file to be distributed to your friends (and enemies!), the UFO file should be shipped along with a separate copy of the TXT description file from the docs directory. This file should be copied into the C:\CAVEDOG\TOTALA\DOCS directory (or wherever their Total Annihilation was installed) as part of your installation procedure as a simple courtesy to remind users what your unit is and what it does. |