Can NPCs speak in other languages?

[realityincarnate]

I'm glad you included the full output like that. I don't know if I would have ever figured out what was going on without seeing the "Current Language is..." text.

So here's what I've found so far: if you change the language by right clicking on the main chat box and selecting a language, everything works fine. But if you use the /language command (which I forgot existed), it doesn't seem to actually change the language (even though it does update it in the select language box).

I'll try to figure out what's going on with /language; hopefully it'll be something simple and I'll be able to get a fix out tonight or tomorrow.

[Shendare]

So I've been tripped up by an obscure problem with the /language command! Good catch!

I did some testing and it does appear that the /language command is not being received or processed on the server.

The client is acting as though it's working (it lists the changed value with /lang sans argument and even shows the correct language highlighted in the right-click menu), but the server never sees the change.

The server keeps acting as though you're speaking the old language, until you zone, at which time the server gets updated properly, and the NPC recognizes the new language.

[realityincarnate]

I spent a little bit of time looking at the /language issue and, to be perfectly honest, I'm pretty confused.

The language number and skill is contained in the packet of each message sent, so that's where all the code currently grabs the language id from. For whatever reason, when you use /language it doesn't change the data that the client sends, but using the right click method does.

My first thought was that there was a "default" language value stored someplace on the server, and that /language was supposed to change that rather than updating the value sent in each packet. But the client doesn't seem to send anything different to the server when you use the command, so I don't know where it would get the information. The fact that it changes after zoning just makes it more confusing.

Anyway, with the weekend ending, I probably won't get to look at this again for a little bit, but I'd be interested to know if anyone has any idea what it's doing.

[Shendare]

Ahh, if language changes are handled client-side, then it must be a client issue. Perhaps I'll just have to say good-bye to old /lang and start using the right-click menu. Thanks for looking into it!

[trevius]

If language doesn't update until you zone, then it is probably because it is being added to the Player Profile, but not being handled properly by the server code before zoning. Using the /language command probably sends a packet that we aren't handling properly yet. Sounds like it should be changing a setting on the server end, but it isn't. This is just a guess, but the profile thing is most likely accurate.

[realityincarnate]

The profile was my thought as well, but I couldn't track down how the data should be getting to the server in my (admittedly far from thorough) first attempts. The only packets I see being sent are ClientUpdate and FloatListThing. It doesn't seem to change any of the unknown values in ClientUpdate, and the floatlist is just a mess... I really hope it doesn't come to sifting through that.

Of course, I'm just using a zone modified to list and dump all incoming packets as my way of checking, so I could be missing something.

And actually, I'm not seeing the /language start working after zoning (using Titanium), now that I paid attention to it. Mine still sticks with whatever value was set by the right-click menu.

[Shendare]

Oops, I must have goofed when I typed 'zoning' before. It updates after camping and logging back in, but not after zoning. Sorry!

As a reminder, another thing that may complicate tracking down the problem or detecting the packets is that the /lang command's language list doesn't number the languages by their langid, it renumbers the languages to keep them consecutive starting with 1 for the first language available to you, 2 for the second, 3 for the third, etc. It was meant to simplify things before the right-click menu was available.