• Content count

  • Joined

  • Last visited

Community Reputation

184 Excellent


About Rochet2

  • Rank
  • Birthday 10/26/1993

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location

Recent Profile Visitors

6,150 profile views
  1. Its enough to just change the DB names in configs (and in DB hurr durr). I use this all the time to hop through the 5 different core/patch combinations I have.
  2. Hmm, looks like it does tho: master: 3.3.5; maybe you should post the error message. You probably have not included Player.h or WorldSession.h or something lke that
  4. You probably downloaded them as zip files instead of using git to download it (clone) The installation guide tells you what you should do.
  5. They were probably moved to rbac as permissions
  6. Follow the TC requirements page guide on how to install visual studio.
  7. Try delete cache folder in wow installation folder. What patch is this on?
  8. Changed windows guides. Another reference is made here though: Btw. this reminded me about this from 2013
  9. Should change release to RelWithDebInfo in the guide?
  10. Debug builds contain debug code and run a lot slower. Release is optimized more for actual production. Compile your core with release instead of debug to make it run fast.
  11. If you change things in your source folder (D:/Trinity) then you need to run cmake which will alter the files in the build folder, like the sln file. Also as you build the core many files will likely change inside the build folder, like logs and binary files and so on. But you probably dont want to keep track of the changes cmake does to build folder or the changes compiling makes to build folder or bin folder as those are not "your changes"
  12. Not sure how well Visual Studio 2017 is supported yet. Other reasons could be that you did not install your VS with C++. Did you explicitly select that you want to install C++ when you installed VS like the TC requirements page says?
  13. Can you post all the text in this box? Im not sure if read only is an issue. Could be, but the program shouldnt actually edit the files. Make sure D:/Build is not read only as files will be written to it.
  14. If you make changes in TC source files, then I guess the repository is C:\Trinity if you are using that as the source (see cmake what is source folder) If you make changes in DBC files then you should probably have them in a separate folder that has another git repository or you could move them to the TC source folder (the TC repository) when you want to add them to the version. To back up the config files you should do the same as with DBC files. Either have them in a folder that is a git repository or move them to TC source folder. One option is also to make the server folder a git repository, but Im not so sure that is a good idea. The whole build folder being a git repository seems to me like a bad idea. Though it will capture all changes you have done in the sln file. I think though that you should be editing the cmake files and not the sln file as when cmake is run your sln changes may get lost I think (did not test).
  15. Personally I dont use git extensions. I use git bash. But Im sure you just open the repository in git extensions, click on the "commit" button, stage your changes, commit them.