Versiones comparadas

Clave

  • Se ha añadido esta línea.
  • Se ha eliminado esta línea.
  • El formato se ha cambiado.

...

Advertencia
titleImportant

Note: There are multiple .sql files to choose from in the .7z archive. If this is your first time installing TrinityCore, you will want to import ONLY the file with "TDB_full" at the beginning. 
The other files are for updating existing world and characters databases from a previous compilation. This makes it easy to update your databases from one compilation to the next as explained in the section above.  

If you downloaded TDB 53 or higher NEVER apply the sql files on in the sql\old directory, as those files are only needed for people updating core between TDB releases dates.
Also don't apply sql files on sql/updates/auth or sql/updates/characters on your fresh installation, those files are only needed to update between versions. NEVER .


NEVER EVER (LIKE, EVER) ENABLE CONTINUE ON ERROR ON YOUR SQL CLIENT. Also, you don't need to run sql files inside update_only on 1st installations. 

Installing The Trinity Databases

...

Panel

auth - holds account data - usernames, passwords, GM access, realm information, etc.

characters - holds character data - created characters, inventory, bank items, auction house, tickets, etc.

world - holds game-experience content such as NPCs, quests, objects, etc.

(if you are running 6.x - hotfixes as well)

The following steps are done using the database management program you installed in Step #5 of Software Required (ex. HeidiSQL or SQLYog):

  • In HeidiSQL, click on the database you want to use in order to "select" it, then click Tools > Load SQL File... > (select the file) > Run file(s) directly.
  • In SQLYog, click on the database you want to use in order to "select" it, then click Database > Import > Execute SQL Script.
  • On mysql cli you must use mysql --default-character-set=utf8 to avoid import failures,
    • WE STRONGLY RECOMMEND TO USE THIS METHOD over the SQLYog or HeidiSQL, it
    's the faster method by far
    • is by far the fastest method to import TDB and it's needed updates.

 

  1. Create the three databases by importing ...\sql\create\create_mysql.sql. You now have three databases - auth, characters, and world. You may need to refresh your program in order to see the new databases.
  2. Click on the "auth" database and import the auth database structure by importing ...\sql\base\auth_database.sql.
  3. Click on the "characters" database and import the characters database structure by importing ...\sql\base\character_database.sql.
  4. Click on the "world" database and import the world database structure by extracting and importing the "TDB_full_*.sql" file you downloaded from the Database download section.
  5. Click on the "world" database and import any *.sql file available in your ...\sql\updates\world folder.
  6. NOTICE WE NEVER IMPORT sql\updates\auth or sql\updates\character files on fresh installation.
  7. NEVER ENABLE CONTINUE ON ERROR ON YOUR SQL CLIENT

...

As mentioned earlier, it is recommended to stay on the same revision as the TDB_full database (Beginner).

If you choose to brave the wilds beyond the current monthly revision, use the (Advanced) instructions below.

...

Bloque de código
languagesql
SELECT * FROM `version`;

This instruction assumes that you have already completed the (Beginner) Keeping the Source Up-to-Date, which means you now have a newly downloaded revision archive from the TrinityCore Downloads.

This instruction also assumes that you have completed the initial Downloading the Database which had you import the TDB_FULL.sql, and it is now approximately one month later - a new revision has been released.

Note: If you have made any custom changes to your database, you may wish to backup (export) all three of them (world, characters, and auth) before performing the next few steps.

  • Beginner:Beginners
    • Extract the TDB_FULL.sql file from the archive and import it into your world database.
    • If they exist, also import the characters_ and auth_ .sql files into their respective databases.
    • Once this is finished and you have already compiled your source, you may run the worldserver binary to load your server. The revision update is complete.

Note: It is at this point that most user errors occur. If your worldserver.exe closes abruptly, make sure that your core's version matches your database version. Check that the `version` table in your world database matches the commit hash listed beside the archive you downloaded at TrinityCore Downloads.

  • Advanced :Users

If you update your source beyond a monthly revision, you will likely have additional updates in the ...\sql\updates folder. The folders within show which database they need to be imported to. For example, the "world" folder has all of the files that need to be imported to your world DB.

...

It is imperative to know the date of your previous revision when updating in order to import all of the updates from that revision to your current one.

Then, simply follow these steps:

  • Browse into your ...\sql\updates\world folder and import all *_world_*.sql files into your world DB that have a date later than your previous revision.
  • Do the same above step for the characters and auth folders, if they exist. If these folders don't exist, there have not been any characters or auth database updates.

Sugerencia
Note: If you are comfortable with executing batch files, you are welcome to use the batch file below to make the importing process easier. Also note that doing this will also gather up .sql files you may have already imported. In most cases this is safe, but you should use this batch file at your own risk. Take a look on the Combine SQL Updates thread in the TrinityCore forum for a more detailed batch script and informations.

If you don't change the batch script, it must be saved and executed in your ...\sql\updates folder.

...