Bug: Talk table exported to packages override

From Dragon Age Toolset Wiki
Jump to: navigation, search
  • Toolset verion: 1.0.1008.0
  • Game version: 1.03
  • Status: Open

Description

When the Talk Table is exported, three different files are created. For a module called MyModule,

* core_en-us.tlk in packages > core > override > toolsetexport
* MyModule_c_en-us.tlk in MyModule > core > override > toolsetexport 
* MyModule_en-us.tlk in MyModule > module > override > toolsetexport

This is undesirable, because the file in packages override will impact other campaigns.

Since the file doesn't have a unique name, there can be conflict if a player tries to install more than one module.

However, the file is essential if core strings have been changed. Without it, when a saved game is loaded, those strings revert to the default.

The file doesn't work if it's moved to the add-in folder.

For example, if the module has changed string 370904 to "Dog Collar", this works until a saved game is loaded, after which it reads "Marabi Collar" in game.

Workarounds

UPDATE : this bug can be avoided completely if no changes are made to core strings. This is achieved by changing the string references in the appropriate 2DA files to new strings which belong to the module.

Admittedly, this is a somewhat tedious process when making a global change (e.g. "Marabi" to "Dog"). However, it greatly simplifies the installation instructions for the player, and improves compatibility between modules. The talk table in packages override always has the same name, so no two modules which use it can co-exist simultaneously.

In our example, we can use the String Editor to discover all instances of the word "Marabi" in the core strings. The string description usually identifies the 2DA which contains the string reference. Make new strings (copy and edit the core string text) and change the 2DA files.

With this approach, the talk table in packages override can safely be deleted (or omitted from the player package).

A known exception is the gender description. These core strings have to be changed, because they are not in a 2DA file. However, the bug never occurs in this case, because gender description is only used in character generation, so save-load doesn't affect it.