Where is GlobalStrings?
 

It is used to be in the FrameXML/GlobalStrings, but not in LEG.
Does anyone know where it goes?

it got moved to a data file within the game client, no longer publicly accessible via framexml

its still viewable via townlong-yak, who have extracted it and hosted it as it existed previously in a dummy file:
https://www.townlong-yak.com/framexm...balStrings.lua

Silly question, maybe. Can you still use GlobalStrings the same way as previous?

Yes, you can - it's just loaded in via C now. Otherwise, plenty of things (including the default UI) would be broken.

You could look them up here. Don't know how they got them though, but the strings are probably in some db file right now.

EDIT: Sorry for the useless reply

Does moving stuff to a db file speed things up some how vs using lua?

Either way, they get loaded into memory so no real advantage at run time. The db file probably means they only get loaded once.

The reasoning for this was discussed on IRC; the primary advantage for Blizzard is that db2 files use the CASC streaming data system, so they can update GlobalStrings as needed without having to push a client update.

Without having thought it through.. when will that be useful?

GlobalStrings.lua was an exported list of localized strings. This was before they started injecting values directly into Lua globals. It makes sense to skip importing an exported list and just inject the strings directly. In the long run, manipulating the Lua backend to do so probably results in marginally quicker load times compared to relying on setting the values through the Lua engine. This also allows centralized storage of all localization and easy correction of localization errors.

Wish they would do this for tooltips. Tooltips can be out of date for months on live before a patch comes along.

They can update nearly everything without patching client in Legion, including tooltips.

Whether they actually will do that remains to be seen though. They don't like to get things out of sync between localizations, and hotfixes to tooltips would require all of their localization teams to be doing high-priority localizations in the middle of other things.