Bug: Talk table exported to packages override

From Dragon Age Toolset Wiki
Revision as of 14:12, 20 December 2010 by Proleric1 (Talk | contribs) (Created page with '*'''Toolset verion:''' 1.0.1008.0 *'''Game version:''' 1.03 *'''Status:''' Open == Description == <!-- Describe the bug here including as many details as possible. What situati...')

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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. Without it, when a saved game is loaded, core strings which have been changed revert to the default.

The file doesn't work if it's moved to the module 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

The only known solution at present is to ask players to remove the file from packages override manually after playing the custom campaign.