String editor - Revision history

Proleric1: /* Editing a string with a specific ID */

2011-01-05T07:06:49Z

‎Editing a string with a specific ID

Proleric1: /* Editing a checked-out string */

2011-01-05T06:57:53Z

‎Editing a checked-out string

Proleric1: /* Editing a checked-out string */

2011-01-05T06:55:57Z

‎Editing a checked-out string

Proleric1: /* Basics */

2010-12-20T13:15:23Z

‎Basics

FollowTheGourd: More warning about needing to check resources back in to update the TLK

2010-11-12T05:22:58Z

More warning about needing to check resources back in to update the TLK

Proleric1: /* Editing a checked-out string */

2010-11-03T23:41:19Z

‎Editing a checked-out string

Proleric1: /* Basics */

2010-11-03T23:40:06Z

‎Basics

Proleric1: /* Basics */

2010-11-03T22:57:51Z

‎Basics

Proleric1: /* Basics */

2010-11-03T22:54:18Z

‎Basics

Proleric1: /* Editing a string with a specific id */

2010-11-03T22:49:59Z

‎Editing a string with a specific id

@@ Line 66: / Line 66: @@
 The string will no longer be regarded as checked out, and can be edited.
 When customising a core string, change the Owner Module to the current module, and the Table to the current module's talk table. Otherwise, the custom string will override all campaigns.
@@ Line 71: / Line 73: @@
 It's wise to back up the data base and make a careful note of the original module properties before attempting this!
-Sadly, as previously noted, while the toolset allows this technique on core gameplay strings, including the GUI, it will not permit the current module to have a local version of a core resource description.
+As previously noted, while the toolset allows this technique on core gameplay strings, including the GUI, it will not permit the current module to have a local version of a core resource description.
 [[Category:Designer resources]]

@@ Line 55: / Line 55: @@
 For strings associated with campaign resources, this is easily resolved, by checking in the resource.
-Doing this for core resources is [[Bug:_Talk_table_exported_to_packages_override bugged]] and should be avoided. Such changes affect all campaigns, which is not helpful to players or other builders. For some reason, the toolset does not allow string changes to be local to the module if they belong to a core resource. A safer technique is to duplicate the core resource into the module (with a new resource name) then edit it. There can be repercussions - some systems (e.g. treasure, recipes) refer to core resource names explicitly, so 2DA files have to be changed. Other aspects (e.g. recipe ingredients) are tag-based, so they will work with the new item as long as you don't change the tag.
+Doing this for core resources is [[Bug:_Talk_table_exported_to_packages_override | bugged]] and should be avoided. Such changes affect all campaigns, which is not helpful to players or other builders. For some reason, the toolset does not allow string changes to be local to the module if they belong to a core resource. A safer technique is to duplicate the core resource into the module (with a new resource name) then edit it. There can be repercussions - some systems (e.g. treasure, recipes) refer to core resource names explicitly, so 2DA files have to be changed. Other aspects (e.g. recipe ingredients) are tag-based, so they will work with the new item as long as you don't change the tag.
-Certain core strings are associated with system components (e.g. GUI) which cannot be duplicated or checked in. The normal procedure in such cases is to create a new string, then change the corresponding 2DA to use the new string id (for an example, see [[Backgrounds_tutorial#Creating_the_background_strings | Background Tutorial]]). Don't be tempted to edit the core string, because the same [[Bug:_Talk_table_exported_to_packages_override bug]] applies.
+Certain core strings are associated with system components (e.g. GUI) which cannot be duplicated or checked in. The normal procedure in such cases is to create a new string, then change the corresponding 2DA to use the new string id (for an example, see [[Backgrounds_tutorial#Creating_the_background_strings | Background Tutorial]]). Don't be tempted to edit the core string, because the same [[Bug:_Talk_table_exported_to_packages_override | bug]] applies.
 There are rare instances in which even this cannot be done, because the string id is hard-coded in the game (for example, the gender description used in Character Generation). See next section for a solution.

@@ Line 55: / Line 55: @@
 For strings associated with campaign resources, this is easily resolved, by checking in the resource.
-Doing this for core resources is dangerous and should be avoided. Such changes affect all campaigns, which is not helpful to players or other builders. For some reason, the toolset does not allow string changes to be local to the module if they belong to a core resource. A safer technique is to duplicate the core resource into the module (with a new resource name) then edit it. There can be repercussions - some systems (e.g. treasure, recipes) refer to core resource names explicitly. Other aspects (e.g. recipe ingredients) are tag-based, so they will work with the new item as long as you don't change the tag.
+Doing this for core resources is [[Bug:_Talk_table_exported_to_packages_override bugged]] and should be avoided. Such changes affect all campaigns, which is not helpful to players or other builders. For some reason, the toolset does not allow string changes to be local to the module if they belong to a core resource. A safer technique is to duplicate the core resource into the module (with a new resource name) then edit it. There can be repercussions - some systems (e.g. treasure, recipes) refer to core resource names explicitly, so 2DA files have to be changed. Other aspects (e.g. recipe ingredients) are tag-based, so they will work with the new item as long as you don't change the tag.
-Certain core strings are associated with system components (e.g. GUI) which cannot be duplicated or checked in. The normal procedure in such cases is to create a new string, then change the corresponding 2DA to use the new string id (for an example, see [[Backgrounds_tutorial#Creating_the_background_strings | Background Tutorial]]).
+Certain core strings are associated with system components (e.g. GUI) which cannot be duplicated or checked in. The normal procedure in such cases is to create a new string, then change the corresponding 2DA to use the new string id (for an example, see [[Backgrounds_tutorial#Creating_the_background_strings | Background Tutorial]]). Don't be tempted to edit the core string, because the same [[Bug:_Talk_table_exported_to_packages_override bug]] applies.
 There are rare instances in which even this cannot be done, because the string id is hard-coded in the game (for example, the gender description used in Character Generation). See next section for a solution.

@@ Line 33: / Line 33: @@
 When finished, use Tools > Export > Export String Table then Tools > Export > Export Talk Table so that the results are available in game.
-Owing to a [[Bug:_export_creates_unnecessary_core_override | bug]], remove the spurious talk table from \packages\core\overide when this is done.
+There is a [[Bug:_Talk_table_exported_to_packages_override | bug]] in Export Talk Table.
 == Generated string IDs ==

@@ Line 9: / Line 9: @@
 Of course, strings associated with resources can often be edited in the object inspector, but viewing strings en masse is sometimes convenient, especially when engaged in global activities like trying to remove Ferelden lore from core descriptions.
-IMPORTANT - all objects must be checked in if you want to see the latest text.
+IMPORTANT - all objects must be checked in if you want to see the latest text. See [[String_editor#Generated string IDs | Generated string IDs]] for more details.
 [[Image:String editor main screen.png]]
@@ Line 35: / Line 35: @@
 Owing to a [[Bug:_export_creates_unnecessary_core_override | bug]], remove the spurious talk table from \packages\core\overide when this is done.
-== Creating a string with a specific id ==
+== Generated string IDs ==
 When a string is created, its id is determined automatically by incrementing the String ID Last Used field in the [[Module#Properties | module properties]].
@@ Line 57: / Line 61: @@
 There are rare instances in which even this cannot be done, because the string id is hard-coded in the game (for example, the gender description used in Character Generation). See next section for a solution.
-== Editing a string with a specific id ==
+== Editing a string with a specific ID ==
 To edit a string whose id is outside of the normal range for the module, change the String ID Begin module property temporarily to a value which is less than the string id in question (but not zero).

@@ Line 25: / Line 25: @@
 For a string to pass the filters all conditions have to evaluate true - they are "AND" conditions.
-There seems to be a bug - "Contains" and "Is Exactly" seem to work the same way, in that they only return a match if you enter the entire string you're searching for.
+There seems to be a bug - both "Contains" and "Is Exactly" sometimes only return a match if you enter the entire string you're searching for. The workaround seems to be to do a successful "Is Exactly" search, after which "Contains" works as expected.
 Once you've found the string you're interested in editing, double-click to open it:

← Older revision		Revision as of 22:57, 3 November 2010
Line 6:		Line 6:

	The string editor is a basic means of accessing this collection of strings.		The string editor is a basic means of accessing this collection of strings.
		+
		+	Of course, strings associated with resources can often be edited in the object inspector, but viewing strings en masse is sometimes convenient, especially when engaged in global activities like trying to remove Ferelden lore from core descriptions.

	IMPORTANT - all objects must be checked in if you want to see the latest text.		IMPORTANT - all objects must be checked in if you want to see the latest text.

← Older revision		Revision as of 22:54, 3 November 2010
Line 22:		Line 22:

	For a string to pass the filters all conditions have to evaluate true - they are "AND" conditions.		For a string to pass the filters all conditions have to evaluate true - they are "AND" conditions.
		+
		+	There seems to be a bug - "Contains" and "Is Exactly" seem to work the same way, in that they only return a match if you enter the entire string you're searching for.

	Once you've found the string you're interested in editing, double-click to open it:		Once you've found the string you're interested in editing, double-click to open it: