Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Naios last won the day on January 26 2017

Naios had the most liked content!

Profile Information

  • Gender
  • Location
  • Interests
    Coding (C++, Java & JS), beautiful code and ice tea ,-)

Recent Profile Visitors

3987 profile views

Naios's Achievements


Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Good question. In the time back as I implemented the DB updater I thought about custom updates being compatible to the current database structure. Currently there is no possibility to prevent such conflicts that you described as part of your question.
  2. Currently TrinityCore is using C++14, the compiler flag for the version is evaluated by CMake with the following CMake CXX target features: https://github.com/TrinityCore/TrinityCore/blob/master/cmake/macros/ConfigureBaseTargets.cmake#L20-L34
  3. @Spec so did the patch solve the issue for you? I need to know whether I should push it to the main repo or not...
  4. Spec could you try whether applying this patch fixes your issue? https://gist.github.com/Naios/b1a44d9448fee3fb6031f21a7df94829
  5. Probably this is related to 697b4dbef20b5c , I will take a look into this .
  6. In order to support C++14 properly the required compiler versions of both branches since b9b667f92 are: Visual Studio 2017 GCC 6.3 (current stable version of Debian 9) Clang 3.9 (current stable version of Debian 9 - might work with earlier versions)
  7. CMake has a command which allows you to invoke the underlying make programm (nmake, make, ninja...) through cmake --build YOUR_CMAKE_DIRECTOY --config Release --target YOUR_TARGET
  8. If you want to use the automatic script recompiler you must use the INSTALL target. otherwise it won't reinstall changed libraries. You don't have to do additional stuff when you use the INSTALL target.
  9. -> https://trinitycore.atlassian.net/wiki/display/tc/IRC Probably you'll receive better help in the IRC. What's in your TrinityCore directory?
  10. AppData isn't a good location for the source and build dir (also because your path contains spaces) -> Move it into the first depth of C:// -> C://TrinityCore and C://TrinityCoreBuild
  11. What Nay meant is that you should have left the path empty because it uses the correct path for your machine then.
  12. You are probably using an unsupported fork of TC, the current database contains > 1000+ applied world updates (and most of it are already included in the world db). Yours contains 15 as the screenshot shows. Also I can't imagine how the current codebases could lead to the issues you are describing. Are you using seperate databases for world/auth/hotfix and char?
  13. You can also try to just create the databases manually, the updater will import the base and update sqls then
  14. You don't need to downgrade any MSVC version... Make sure you created the boost environment var which needs to point to your boost root dir. Also make sure you use the CMake x64 generator and the matching x64 dev openssl libraries. Seems like you mixed x32 and x64.
  15. MariaDB 10.1 works very well with TC, but it's not official supported though. Maybe it's an alternative to MySQL 5.7 for you...
  • Create New...