Jump to content
TrinityCore

Nay

Developers
  • Posts

    2766
  • Joined

  • Last visited

  • Days Won

    179

Everything posted by Nay

  1. Shauren added support for 7.2.0 now
  2. 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).
  3. PCH speeds up compilation, by a lot.
  4. I recommend reporting any issues in the tracker. They do not get visibility here.
  5. As explained in the wiki, you need to select the C++ compiler in Custom install options of Visual Studio
  6. Create a pull request in the Github repository.
  7. I don't want anything If you have errors during compile, you can post the errors. The ones in CMakeError.log should be ignored.
  8. Those errors do not matter, they are tests done by CMake internals. All that matters is in the Visual Studio compile log.
  9. @Drakos What errors are you talking about? Paste the output of the compilation.
  10. By using a sniffer (it captures network packets between the client and server) while connected to an official server.
  11. --- 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 ---
  12. One issue we had tabs is that more people than expected simply missed them and could not find the guide for the other OSs. Anyway, I can see that expandable text working for small portions, not entire pages. If we had a single page for all the OSs, would the texts in the expandables be short excerpts or the whole thing?
  13. https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-an-open-source-maintainer/
  14. That seems to be the opinion of someone that is removing his/her stuff from Github.
  15. WPP does not have a "data model" for packets atm. That's more or less what needs to be done... except that the same packet can have different representations across client versions.
  16. The "new" text output won't have to be the same and it will break stuff (but that's on the people that assumed that non-formatted text is safe to be consumed).
  17. I didn't mean to say that it didn't provide value, au contraire, tools like this are absolutely needed. However, imo, relying on the fragile text output format of WPP is insane; it will change and it does not matter the client version. The time spent implementing the text parsers could be used to change WPP so that it can output in a better format. @Polaretto is working on changing this so let's help him
  18. Oh noes, parsing arbitrary text That is going to break at any minor change to current WPP output format...
  19. That seems fine. The problem is probably in one of the DLLs that you copied to the worldserver directory.
  20. Somewhere, somehow, you are mixing 32 bit vs 64 bit DLLs. Can you post your CMake output?
  21. Removed? Everything is on https://github.com/TrinityCore/TrinityCore/commits/master 3.3.5, 4.3.4, 6.x and now 7.x
×
×
  • Create New...