[Carbinfibre]

On 3/21/2021 at 9:50 PM, Desed said:

You need to convert DBC to sql, add eng localization and everything will work.

Would appreciate a quick explenantion on a couple steps if you could ^.^

Convert dbc to sql, import for example Spell.sql into Database and then extract sql? Because I've been looking for an option to alter the language to the tables and my sql program is set to English btw.

[Saurfang-WoW]

On 12/13/2022 at 4:20 PM, Carbinfibre said:

Would appreciate a quick explenantion on a couple steps if you could ^.^

Convert dbc to sql, import for example Spell.sql into Database and then extract sql? Because I've been looking for an option to alter the language to the tables and my sql program is set to English btw.

U either need to export it as CSV or to SQL/SQL file.
When u did export via CSV/SQL file:
import it to your database (best is a very own database section for it).

when the spelldata is at your database...
you need to download the english client, grab the spell.dbc/spell.db2 out of the last mpq patch from blizz, then export it to database in a very own table (rename the other spell table to somewhat like:
spells_toBeTranslated so it does not overwrite the russian spell localization...
when both tables are up... you need to go into the english table, set your database viewer so it shows all entries, then head to the columns with the names, ranks descriptions and such...
mark the columns and copy/paste them to the equivalent columns in the spells_toBeTranslated table...
when done just export it from your database to CSV or directly via database import option. then pack your new spell.dbc in a mpq patchfile as well as in your dbc folder on server and you should be fine =D

going to do this as well after i finished with adding all language localizations to all dbc's for all possible client languages ^.^