Custom TLK creation

[Legacy_The Mad Poet]

                Hopefully someone might be able to give me a hand with this.

I'm making a custom TLK for my module. Basically I'm going to redo some of the classes names. My first attempt was the easiest. Basically I copied the line numbers from dialog.tlk and replaced them in my new tlk file with the names I wanted. That... did not work. Instead I got some random string from the OC dialog.

Then I tried to set my class in the classes.2da file to refrence string 150000, 150001, and 150002 for the name, plural, and lowercase specifically. Once I make the character in game it shows the class name as being blank.

This is the first time I've done tlk editing and I'm sure I've missed a rather simple step somewhere. The 2da is in a hak in the module. The module does point to the custom tlk. I'm just unsure what is wrong.
               
               

               
            

[Legacy_Rolo Kipp]

               <getting dizzy...>

The primary thing to remember with a custom tlk is that the game needs to add 16777216 to the custom tlk line number. So line 1 in your custom tlk is referred to in the game as 16777217. Line 2 is 16777218, etc.

Edit: From the Omnibus (be sure to get the update to DocFetcher!):

Primogenitor wrote...
When you reference a tlk line in a 2da file (or via scripting I assume), if its  16777216 or more, then its knows its a custom tlk. If its less that that then its in the dialog.tlk. So your line 3000 is 3000 if you want the dialog.tlk version or 3000 + 1677216 = 1680216 if you want the custom tlk version. See nwn.bioware.com/developers for the full tlk specs.

So replace the reference string numbers with the gazillion-ized custom tlk numbers and you should be alright.

<...when he tries to count that far>
               
               

               

                     Modifié par Rolo Kipp, 20 juin 2013 - 04:04 .
                     
                  

            

[Legacy_The Mad Poet]

               Everything I searched for related to this problem... and I saw that information no where. Thanks a bundle! Worked just fine.