Table of Contents

Armada 1 Logging

Star Trek: Armada is of course a software product and as such it also has some built-in means of logging things going on. Some of them can be found by carefully looking at the files delivered by the game. Others are not quite visible. Here are some means of activating/using logging in Armada.

ATVI

One method that is definitely not obvious, is the ATVI mechanism. When placing a file named ATVI (no extension!) in the root folder of a Star Trek: Armada installation, its mere presence will activate some logging. The contents of the file are of no relevance, so an empty file will already do the trick.

If you want to deactivate the ATVI logging, simply delete the file or rename it.

There will be different kinds of files showing up in the folder Logs, some of which are not always created:

These files will remain afterwards, in contrast to the standard log file logfile.txt, that will be overwritten by each new instance of Armada.

Default Logging

Armada does by default already log to the file Logs\logfile.txt. The amount of log output can be influenced by altering the Logfile.cfg file in the root folder of the Armada installation. Everything with a semicolon (;), pound symbol (#) or slash (/) in front of it will be considered a comment and the rest of the line is ignored. By this means also a number of logging options are deactivated by default. Removing the comment symbol activates a specific logging option.

Some options are not meant for Armada, but for one of it's predecessors. Do not use/activate those.

The default options (active in the unmodified stock game) are the following:

Note: The logfile.txt will be overwritten by Armada if it already exists. So information is not kept. Each new instance of Armada will remove the old log contents and write its own instead. This is one of the main advantages of the ATVI approach above: Each file has a unique name and is therefore kept.