This is a 'it compiles so ship it' TLK utility Note: have 1 field in entry struct that I don't know what it is ( used in soundref entries? ). Ex of Usage. 1. create a TLK 2. open dialog.tlk ( which is updated with nearly every patch ), then click merge, and choose custom file 3. save and use it as the dialog.tlk This file now has entires at the end. Only need to update IDs in override files for my classes, etc. No warranties, etc. I have included all source and VC workspace. No complaining about the code . * Fixed edit & delete bug & added a release build for those who don't have MSVC installed.
This is a compilation of the old system into a single score. There were 1 that made this score of 10 then rounded to 10.
Posted by TheOther ( 07/27/02 21:05..xxx.xxx ) at 2002-07-27 21:05:00
Basically, here's the deal. With every update / patch, your
dialog.tlk is updated, and you therefore must add back the
stuff you put in ( the upater checks the file checksum, so
you have to restore your original dialog.tlk ). So if you
put custom string ref's, then you have to go back and add
them. With this, you can make your own tlk file with your
strref's. And, when a patch comes along, restore your
unmodified dialog.tlk, patch, run this program, open
dialog.tlk, merge in your custom tlk, and the day is save!
Of course, you will have to update any & all of your
strrefs. Inspiration for this? Doing custom classes, and
actually having a name show up in the char generation
screen.
Posted by Mayseth Aalikor ( ..xxx.xxx ) at 2002-07-26 19:31:00
Hecateus:If I'm not mistaken it's used to edit the *.tlk
files, the ones responsible for descriptions and what not.
Posted by LordSaur ( ..xxx.xxx ) at 2002-07-26 14:38:00
There is an other TLK creator/editor on NV vault:
NWN TLK Editor 1.1
What is the difference between these two utils?
Posted by Hecateus ( 07/26/02 12:29..xxx.xxx ) at 2002-07-26 12:29:00
*WHOOOSH* ...is the sound of this concept going right
over my head.
Explain please in simple English what this does.
Thankyou. :)
You must be Logged In to post comments in this section.