The 6.x branch of TrinityCore has been created almost 11 months ago and according to the TrinityCore forum download counter, the 3.3.5 is still the most used branch by the TrinityCore community.
In fact, all of the download counters (week, month and year) are showing that the 3.3.5 database has (the more or less) twice of the downloads of the 6.x one.
Historically the MaNGOS project has kept the three main components into separated project. The core, the scripts and the database content have been developed by separated projects, having separated teams, repositories and IRC channels.
CMaNGOS has inherited this scheme, but now things seem to be changing…
It’s the 3rd of September 2015 when the “purest heir” of MaNGOS publishes the 0.18 release through a commit of stfx in the cmangos/mangos-wotlk repository.
This is the second release that comes from the CMaNGOS project, even if we are far from the days when the MaNGOS project published more than one release per year, this is an important step anyway.
The changelog reports 726 commits since the previous release and several game and server features:Continue reading
AzerothCore, CMaNGOS, and TrinityCore have a great feature that retail hasn’t, a true PvP statistical system.
PvPstats is a tool written by ShinDarth, released under the GNU-GPL3 license, that allows to store and display data about Battleground scores.
It consists of two parts: a core modification and a web application.
Core-part of PvPstats
TrinityCore goes forward with its plan of focusing the development on the 6.x branch by deleting the 4.3.4 branch.
Now there are two official branches, the stable 3.3.5 and the newest 6.x.
The 4.3.4 branch was not stable nor new, but the deletion of it caused malcontent and led to the creation of a separated repository at GitLab which aims to continue the development of the 4.3.4 game version. Behind it there are some TrinityCore DB developers:
The DB releases for 4.3.4 will be published in another repository located at GitHub:
If you are using TrinityCore, you can forget about importing the *.sql files one by one when you install/update your core.
Thanks to a Pull Request of 6,734 additions and 179 deletions written by Naios, TrinityCore has now an automatic database updater included in the core.
This will save a lot of time to TrinityCore users and simplify a lot the installation process. However, it is still disabled by default and has to be enabled by editing the worldserver.conf file, in the “UPDATE SETTINGS” category.
In order to set up the world database in a fresh TrinityCore installation, you will have just to download and import the latest release of the TDB database and enable the automatic updater. Then you can run your worldserver daemon and it will do the rest: it will update the world database, importing all the sql/updates/world/*.sql files. If you are using the 6.x branch, the same is for the hotfixes database. When needed, it will also update automatically the characters and auth database.
Happy time-saving and thanks Naios for this great change!