I just took a very brief look at this. As in your case, it worked for potactics but not gfaydark for me also. I noted that I had a gfaydark.cfg file, but not a potactics.cfg file.
On renaming my gfaydark.cfg file to old_gfaydark.cfg, it then used my altered long_name for gfaydark. It would appear that if a <zone>.cfg file exists, it is using the long name that is stored in the .cfg file.
Added:
If you update the long_name in the db then go to that zone (even if the <zone>.cfg exists). If you then do #zsave <zone> it appears to write the long_name from the database to the .cfg file, so if you zone out, wait for the zone to shutdown, next time you zone back in you will get 'You have entered <your new long_name>'.
|
Threaded Mode
