Nay

Developers
  • Content count

    2,746
  • Joined

  • Last visited

Community Reputation

629 Excellent

About Nay

  • Rank
    Jack of All Trades, Master of None
  • Birthday March 3

Contact Methods

  • Website URL
    https://github.com/DDuarte

Profile Information

  • Gender
    Male
  • Location
    Portugal

Recent Profile Visitors

15,529 profile views
  1. Search around the forums. https://trinitycore.atlassian.net/wiki/display/tc/smart_scripts
  2. 7.2.0 is supported on master since 16 April
  3. Currently, the way it works is with the pool_* tables in the world database. There are pool groups and a max number of notes (herbs, mines, etc) that can be active at once. @r00ty has been working hard on improving this system, by having dynamic spawns that take into account number of players in the zone, like retail, and much more. The pull request is at https://github.com/TrinityCore/TrinityCore/pull/19056 and needs testers.
  4. Don't do that, get the actual master branch (HEAD)
  5. --- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---
  6. Shauren added support for 7.2.0 now
  7. If you build the server to C:/TrinityCoreBuild, you cannot launch the binaries from C:/TrinityCoreBuild/bin/Release/worldserver.exe You can either copy the contents of the Release directory somewhere else OR, as explained, use the CMAKE_INSTALL_PREFIX to put the files in the correct place automatically (once you compile the INSTALL project in Visual Studio or run "make install" on Linux).
  8. PCH speeds up compilation, by a lot.
  9. I recommend reporting any issues in the tracker. They do not get visibility here.
  10. As explained in the wiki, you need to select the C++ compiler in Custom install options of Visual Studio
  11. Create a pull request in the Github repository.
  12. I don't want anything If you have errors during compile, you can post the errors. The ones in CMakeError.log should be ignored.
  13. Those errors do not matter, they are tests done by CMake internals. All that matters is in the Visual Studio compile log.