Quote:
The reason your strings get corrupted is because you screwed up the string file format when edited it with soemthing like regular windows notepad. You need to use an editor which shows and preserves special lien characters which used in that file. Like shell edit or Notepad++.
|
Yeah, I was going to came back and note that, but was too lazy. Using Notepad++ prevents those string errors.
Quote:
But in either case- I have tried altering both: the long name in DB and a name in string file (both of them) at SAME time- and it produced no effect, other one the one in chat box.
|
Right; that's the same result I get. However, (per Xardon's prompting) I've been experimenting with the SoD version of the eqstr_us.txt file in the SoD environment, and in fact you CAN change the zone names in that file and have it reflected in both the "Entering . . ." text and the "/w" text. It appears they are using an earlier version of eqgame.exe (their version is half the size of the Titanium version). In any case, Xardon is correct insofar as at least
SoD's version of eqgame.exe allows the eqstr_us.txt file to drive the in-game zone names. It just doesn't appear Titanium does.
Incidentally, I also tried replacing the Titanium eqgame.exe with SoD's version just to see if it would work, and it will not load with the EQEmu server code. So, it appears (for whatever reason) Titanium doesn't use the zonename entries in the eqstr_us.txt file.