locale independent objective parser about pfquest HOT 7 CLOSED

Add ruRU locales (dbc's) to your server if you want to use a russian client.

from pfquest.

I reproduced the situation described in #11. If the players play on their client, and the server will not return text for the locale of their client (enUS text will return), then in your addon this parser will not work.

from pfquest.

I signed from below that if the languages of the client and server are the same, then everything works. But if suddenly the server does not return the client's locale data(return enUS data), then the parser does not work

from pfquest.

It's unrelated to the parser and is related to: #11
The parser itself just uses the client localization like before.
The only difference is that It's not hardcoded anymore and using globalstrings instead.

from pfquest.

why unrelated with the parser? It is the parser that does not work under certain conditions:
server locale = locale addon databases ≠ game client locale

I wrote in the first message: "Accordingly in the addon I use the base enUS(look at screenshot)". So it turns out that I reproduced the conditions written above and the parser did not work.

from pfquest.

why unrelated with the parser?

Because it's the zones.lua, the parser itself is working. You can't see anything on your map, because the zones.lua in enUS only contains enUS maps, which leads to the fact that no nodes are displayed because a valid zone can not be opened.

Reproduce:

• Replace zones.lua from enUS with the one located in ruRU
• Reload

from pfquest.

Exactly, I completely forgot about the zones... Thank you.

from pfquest.