The totala.ini File

totala.ini is Total Annihilation’s configuration file — and a curiosity: the game never creates it. It shipped on Disc 1 as an optional file you had to copy into your TA folder yourself. Most installs therefore never had one, and most players never knew it existed. It still works with every version, including GOG and Steam installs.

Place it in the same directory as Totala.exe (e.g. the old C:\Cavedog\Totala\). Format is plain INI with a [Preferences] section — and one quirk: values are terminated with a semicolon, and lines starting with ; are comments. Cavedog shipped it heavily commented, like a friendly README that also happens to configure your game.

A minimal example:

[Preferences]

UnitLimit = 500;

NoDirectSound = 0;

UseWindowsSound = 0;

The documented options

These three are the ones Cavedog itself shipped and documented (in the readme and on Disc 1):

UnitLimit

UnitLimit = 500;

The maximum number of units per player. Default is 200 (250 in patched retail builds, per Cavedog’s patch notes); this option raises it. 500 is the practical ceiling for unmodified TotalA.exe 3.1 — community extensions (Xon’s DLL patches and similar) raise the hard limit much further, after which this file becomes the way to set any value you like, including values below the patched maximum.

The shipping comment warns honestly: the higher the number, the more CPU and RAM the game needs, and pathfinding suffers first. That warning was written in 1998 — modern machines laugh at it, but the pathfinding part still holds on huge maps with 1000+ units. Community guidance for big multiplayer games is to agree on one value (TA: Escalation, for example, expects all players to have identical totala.ini unit limits — its teleporter units are sensitive to mismatches).

NoDirectSound

NoDirectSound = 1;

Disables sound entirely (0 = normal). The 1997 fix for crashes on systems with broken or non-DirectX sound drivers — rare on modern Windows, but still the first thing to try if the game refuses to start or crashes with audio errors on exotic setups (or Wine).

The command-line equivalent: totala.exe -s.

UseWindowsSound

UseWindowsSound = 1;

Uses the classic Windows multimedia API instead of DirectSound — the compatibility fallback when DirectSound misbehaves but you still want sound. Cavedog’s own readme is refreshingly honest about the trade-off: it works, but “audio quality will be greatly decreased, especially during heavy battles”, and you lose mission-briefing narration and movie sound.

Command-line equivalent: totala.exe -w.

Command-line equivalents

The two sound options can also be passed as switches, which is how support pages of the era recommended it (right-click the shortcut → Properties → append to Target):

• totala.exe -s = NoDirectSound
• totala.exe -w = UseWindowsSound

Where the file comes from

Distribution history, for the archaeologically inclined:

• TA Disc 1 (1997): shipped as Totala.ini with the two sound options, intended as a copy-me-if-you-have-sound-problems helper.
• The Cavedog website: offered it as a download alongside the 1.1 patch notes (which documented both sound switches).
• Third-party era: every serious mod package shipped its own — with UnitLimit = 500 as the headline feature. The 500-unit ini became so associated with “serious” installs that some mods required their version, unchanged.
• GOG/Steam today: not included; the game runs without it at defaults. You create it yourself.

Notes for modern setups

• Still fully functional on Windows 10/11 and in Wine/Proton.
• GOG’s release is already patched to 3.1; without a unit-cap extension, values above 500 are silently clamped by the executable.
• If you use a community extension that raises the cap (to 1500, 5000, …), this file is the recommended way to set your working limit — several extensions read it at startup and treat its value as authoritative.
• Keep the semicolons on value lines. Some parsers in tooling around TA (launchers, mutator managers) expect them, and the original file format used them consistently.
• All players in a multiplayer game should run identical unit limits — desyncs in long games have been attributed to mismatched caps.

The bottom line

One tiny file, three settings, and the difference between “TA as it shipped” and “TA as people actually played it for the last 25 years”. If your install doesn’t have one: create it, set your unit limit, and keep a copy with your saves.

If you discover an undocumented option or a different behaviour in some version, let us know — see the Imprint for contact.