Ideally in the future support other source databases e.g tbc
Also import will need to be able to verify / check data.
Current plan for the database is:
Keep existing TC structure (or minimal changes)
Import data from external sources.
This will hopefully reduce duplicated work between projects, and make changes easier to update in the future.
Current strategy has been to try and 'merge' data into the existing database, but not sure how effective it actually is. To decide: continue 'merge' method, or erase all and replace.
Running import:
See contrib/vmangos_db_importpython db_import.pypython db_verify.py
Will likely require python files to be edited to update db connection and enable features (whole import is slow).
Require access to the trinity world db and the vmangos world db.
Done some more thinking on this since first starting the db import process. The 'merging' approach doesnt work as it isnt repeatable, as in, it gives slightly different results importing the same dataset.
Data importer for vmangos -> trinity database.
Ideally in the future support other source databases e.g tbc Also import will need to be able to verify / check data.
Current plan for the database is:
This will hopefully reduce duplicated work between projects, and make changes easier to update in the future.
Current strategy has been to try and 'merge' data into the existing database, but not sure how effective it actually is. To decide: continue 'merge' method, or erase all and replace.
Running import:
See
contrib/vmangos_db_import
python db_import.py
python db_verify.py
Will likely require python files to be edited to update db connection and enable features (whole import is slow).
Require access to the trinity world db and the vmangos world db.
Manual files required for import: BroadcastTexts1.csv WorldSafelocs.json
Current world database with imports applied can be found at: https://drive.proton.me/urls/FYJ7971GFW#mRGxtmuXg6FP