Jump to content
TrinityCore

How to setup WoD server? TrinityCore 6.x


Shinzon
 Share

Recommended Posts

I have searched all over the forums and can't find anything that exactly matches this. 

I can connect fine to the server using my windows client, but when I try to connect using my mac client it immediately bounces back stating "You have been disconnected from the server". 

I have the correct IP address in the config.wtf (And realmlist in the DB) but still can't connect. 

I of course can't apply the connection patcher, because the EXE isn't mac compatible. 

Is there something else I need to do to connect with mac?

Here is my connection.log if it helps (NOTE that the ".logon.battle.net" I can't get rid of... there is no where config.wtf that has that).

 

3/14 13:10:21.966  Login program=WoW platform=Mc64 locale=enUS
3/14 13:10:22.097  Component WoW.Mc64.20886
3/14 13:10:22.097  Component WoW.base.20726
3/14 13:10:22.099  Battle.net is Component Bnet.Mc64.37165
3/14 13:10:22.099  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 
3/14 13:10:22.145  Failed to resolve “108.26.241.19”.logon.battle.net
3/14 13:10:22.145  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED 
3/14 13:10:22.145  Login program=WoW platform=Mc64 locale=enUS
3/14 13:10:22.145  Component WoW.Mc64.20886
3/14 13:10:22.145  Component WoW.base.20726
3/14 13:10:22.154  Battle.net is Component Bnet.Mc64.37165
3/14 13:10:23.298  Client Disconnect due to reason:8
3/14 13:12:54.053  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 
3/14 13:12:54.073  Failed to resolve “192.168.1.130”.logon.battle.net
3/14 13:12:54.151  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED 
3/14 13:12:54.151  Login program=WoW platform=Mc64 locale=enUS
3/14 13:12:54.173  Component WoW.Mc64.20886
3/14 13:12:54.173  Component WoW.base.20726
3/14 13:12:54.308  Battle.net is Component Bnet.Mc64.37165
3/14 13:12:54.309  Client Disconnect due to reason:8

 

 

 

Link to comment
Share on other sites

3 hours ago, Aokromes said:

Aokromes, yes I saw your post already in there that I'm trying to connect with an unpatched client. Which points me back to the first question I posted above... How do I patch a Mac client? EXE's don't run on macs.

Link to comment
Share on other sites

On 3/14/2016, 8:38:55, Aokromes said:

OFC you must patch your mac with mac patcher.

Ok, maybe I'm being completely dense here... but where is the Mac Patcher? I've looked all through my core build out (even with tools checked on cMake) and I can't find it anywhere. Do I have to do a complete build with Mac to get it? Is there anywhere here on Trinity's source that I can download it from?

Link to comment
Share on other sites

  • 2 months later...

Go to /Applications/World of Warcraft on your mac... copy the World of Warcraft.app directory over to your wow server... I placed it in a Patch directory.  Then cd over to the Patch directory.  Then you need to run the connection_patcher.  Do a connection_patcher --path /path/to/World of Warcraft.app/Contents/MacOS/World of Warcraft.  You need to make sure you do the full path thru the app directory.  when that is done... you should have a World of Warcraft Patched.app in the Patch directory.  copy that back to the mac... and you should be good to go.

Link to comment
Share on other sites

  • 3 months later...
On 6/1/2016 at 1:26 PM, Dipdill said:

Go to /Applications/World of Warcraft on your mac... copy the World of Warcraft.app directory over to your wow server... I placed it in a Patch directory.  Then cd over to the Patch directory.  Then you need to run the connection_patcher.  Do a connection_patcher --path /path/to/World of Warcraft.app/Contents/MacOS/World of Warcraft.  You need to make sure you do the full path thru the app directory.  when that is done... you should have a World of Warcraft Patched.app in the Patch directory.  copy that back to the mac... and you should be good to go.

Thank you so much for this! Helped a lot!

Link to comment
Share on other sites

Hey Guys,

I want to explore the 6.x server.

As for now according to the wiki I understand that 6.x follows the latest patch available

I wonder how can I open a WoD server using the 6.x?

Should I use an earlier branch?

I tried to compile 363731a but I kept gettings errors

What is the right way to get a working WoD server for linux?

 

Thanks, Nitzan

  • Upvote 1
Link to comment
Share on other sites

**EDIT**

Recompiled and it runs, thanks :)

 

Hey @Nay

I received the following error

 

Determining if the pthread_create exist failed with the following output:
Change Dir: /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec611397089/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec611397089.dir/build.make CMakeFiles/cmTryCompileExec611397089.dir/build
make[1]: Entering directory '/home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building C object CMakeFiles/cmTryCompileExec611397089.dir/CheckSymbolExists.c.o
/usr/bin/cc   -std=gnu99 -W -Wall -Wextra -Winit-self -Winvalid-pch -Wfatal-errors    -o CMakeFiles/cmTryCompileExec611397089.dir/CheckSymbolExists.c.o   -c /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c
Linking C executable cmTryCompileExec611397089
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec611397089.dir/link.txt --verbose=1
/usr/bin/cc   -std=gnu99 -W -Wall -Wextra -Winit-self -Winvalid-pch -Wfatal-errors     CMakeFiles/cmTryCompileExec611397089.dir/CheckSymbolExists.c.o  -o cmTryCompileExec611397089 -rdynamic 
CMakeFiles/cmTryCompileExec611397089.dir/CheckSymbolExists.c.o: In function `main':
CheckSymbolExists.c:(.text+0x16): undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
CMakeFiles/cmTryCompileExec611397089.dir/build.make:88: recipe for target 'cmTryCompileExec611397089' failed
make[1]: Leaving directory '/home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp'
Makefile:118: recipe for target 'cmTryCompileExec611397089/fast' failed
make[1]: *** [cmTryCompileExec611397089] Error 1
make: *** [cmTryCompileExec611397089/fast] Error 2

File /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include <pthread.h>

int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(&pthread_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}

Determining if the function pthread_create exists in the pthreads failed with the following output:
Change Dir: /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec731348423/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec731348423.dir/build.make CMakeFiles/cmTryCompileExec731348423.dir/build
make[1]: Entering directory '/home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building C object CMakeFiles/cmTryCompileExec731348423.dir/CheckFunctionExists.c.o
/usr/bin/cc   -std=gnu99 -W -Wall -Wextra -Winit-self -Winvalid-pch -Wfatal-errors -DCHECK_FUNCTION_EXISTS=pthread_create   -o CMakeFiles/cmTryCompileExec731348423.dir/CheckFunctionExists.c.o   -c /usr/share/cmake-3.0/Modules/CheckFunctionExists.c
Linking C executable cmTryCompileExec731348423
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec731348423.dir/link.txt --verbose=1
/usr/bin/cc   -std=gnu99 -W -Wall -Wextra -Winit-self -Winvalid-pch -Wfatal-errors -DCHECK_FUNCTION_EXISTS=pthread_create    CMakeFiles/cmTryCompileExec731348423.dir/CheckFunctionExists.c.o  -o cmTryCompileExec731348423 -rdynamic -lpthreads 
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
CMakeFiles/cmTryCompileExec731348423.dir/build.make:88: recipe for target 'cmTryCompileExec731348423' failed
make[1]: Leaving directory '/home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp'
Makefile:118: recipe for target 'cmTryCompileExec731348423/fast' failed
make[1]: *** [cmTryCompileExec731348423] Error 1
make: *** [cmTryCompileExec731348423/fast] Error 2


Performing C++ SOURCE FILE Test boost_filesystem_copy_links_without_NO_SCOPED_ENUM failed with the following output:
Change Dir: /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTryCompileExec591387630/fast"
/usr/bin/make -f CMakeFiles/cmTryCompileExec591387630.dir/build.make CMakeFiles/cmTryCompileExec591387630.dir/build
make[1]: Entering directory '/home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp/CMakeFiles 1
Building CXX object CMakeFiles/cmTryCompileExec591387630.dir/src.cxx.o
/usr/bin/c++    -std=c++11 -W -Wall -Wextra -Winit-self -Winvalid-pch -Wfatal-errors -Woverloaded-virtual -Dboost_filesystem_copy_links_without_NO_SCOPED_ENUM -std=c++11   -o CMakeFiles/cmTryCompileExec591387630.dir/src.cxx.o -c /home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp/src.cxx
Linking CXX executable cmTryCompileExec591387630
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTryCompileExec591387630.dir/link.txt --verbose=1
/usr/bin/c++    -std=c++11 -W -Wall -Wextra -Winit-self -Winvalid-pch -Wfatal-errors -Woverloaded-virtual -Dboost_filesystem_copy_links_without_NO_SCOPED_ENUM -std=c++11    CMakeFiles/cmTryCompileExec591387630.dir/src.cxx.o  -o cmTryCompileExec591387630 -rdynamic -lboost_system -lboost_filesystem -lboost_iostreams 
CMakeFiles/cmTryCompileExec591387630.dir/src.cxx.o: In function `boost::filesystem::copy_file(boost::filesystem::path const&, boost::filesystem::path const&)':
src.cxx:(.text._ZN5boost10filesystem9copy_fileERKNS0_4pathES3_[_ZN5boost10filesystem9copy_fileERKNS0_4pathES3_]+0x26): undefined reference to `boost::filesystem::detail::copy_file(boost::filesystem::path const&, boost::filesystem::path const&, boost::filesystem::copy_option, boost::system::error_code*)'
collect2: error: ld returned 1 exit status
CMakeFiles/cmTryCompileExec591387630.dir/build.make:91: recipe for target 'cmTryCompileExec591387630' failed
make[1]: Leaving directory '/home/nitzan/TrinityCore/build/CMakeFiles/CMakeTmp'
Makefile:118: recipe for target 'cmTryCompileExec591387630/fast' failed
make[1]: *** [cmTryCompileExec591387630] Error 1
make: *** [cmTryCompileExec591387630/fast] Error 2

Source file was:

  #include <boost/filesystem/path.hpp>
  #include <boost/filesystem/operations.hpp>
  int main() { boost::filesystem::copy_file(boost::filesystem::path(), boost::filesystem::path()); }
 

 

What could be wrong here?

Edited by HolyNitzan
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Frik24
      Hello TrinityCore members,

      I wanted to mess around with 6.2.4a build 21742,
      I've downloaded/compiled the trinitycore TrinityCore-6.2.4-21742 from github

      I've got connection_patcher.exe among other files in my release build

      I've got client with same patch TrinityCore-6.2.4-21742

      I patched the client(all successful) with patcher i've got from compiling source.

      When i run WoW_Patched.exe i get error message https://imgur.com/a/ZZQI3J9
       
      can anyone help me i'd appreciate it a lot!
    • By Rochet2
      A lot of people have asked how to debug so I made this short guide on how to set up debugging.
      This guide only tells you how to actually set up debugging in TrinityCore on Windows and Linux.
      This will not explain the basics of debugging. You can google those or play around with the debugger to learn.
      Here are a few videos that explain how to actually debug after setting debugging up on visual studio: https://youtu.be/0ebzPwixrJA and linux: https://www.youtube.com/watch?v=sCtY--xRUyI

      This guide contains multiple guides. Each list of bullet points is it's own guide.
      Make sure you can run the server normally before trying to debug.

      Windows:
      On Windows before anything you should check these
      - Before debugging or making crashlogs etc. with Visual Studio you must compile the core in "Debug" instead of "Release". You can select this in "Build>Configuration Manager" or at the top of Visual Studio window http://i.imgur.com/5oHd59j.png
      - You also need to move the new pdb files generate by compiling in debug mode on Visual Studio from the compile output folder (bin) to your server folder - these files contain information needed for debugging.
      - It is assumed that Solution Explorer is open. Open it by selecting "View>Solution Explorer" in Visual Studio http://i.imgur.com/hkW6Gk0.png
      -- You may want to click on the Home icon to reset the view on Solution Explorer http://i.imgur.com/N8UPwDh.png
      - You can place breakpoints in Visual Studio editor by right clicking a line of code and selecting "Breakpoint>Insert Breakpoint" http://i.imgur.com/L2TxBVG.png
      - At the top of the window you should see controls for stepping and continuing when you have started to debug.
      - Here is a video showing the basic Visual Studio functionality https://www.youtube.com/watch?v=Ijdk4z8-2OI
      Fastest way to debug on windows. This is the easiest way to start up debugging a script.
      - Start the authserver and worldserver normally
      - Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core
      - In Visual Studio at the top select "Debug>Attach to process...>worldserver.exe" and click "Attach" http://i.imgur.com/jDEI2Hq.png
      - You are now debugging
       
      The second slower way of debugging on windows. This is useful for debugging something that occurs in the startup of the server.
      - Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core
      - In solution explorer right click on worldserver and select "Set as StartUp Project" http://i.imgur.com/wvMzeRA.png
      - In solution explorer right click on worldserver and select "Properties" http://i.imgur.com/rTNEF9O.png
      -- In Properties you should go to "Configuration Properties>Debugging" and edit "Working Directory" to point to the server folder. For me this is the default compile folder so I use "$(OutDir)" http://i.imgur.com/aRI29fB.png
      - Start the authserver normally
      - Start the worldserver by selecting "Debug>Start Debugging". The server will start with debugging attached from the beginning http://i.imgur.com/cg1KJNw.png
      - You are now debugging
      Crashlogs on windows. Once you have a way to reproduce a crash you can get a crashlog that can help you resolve it.
      - After compiling the core in "Debug" instead of "Release" start up the worldserver and authserver
      - Reproduce the crash you have
      - In the server folder there is now a folder called Crashes that contains txt and dmp files. http://i.imgur.com/9eQIdql.png
      - You can open the txt files in text editors http://i.imgur.com/EH6R17E.png
      -- At the top of a txt file there is some information about your system and below it there is the Call Stack and below that there are Variables of each part of the call stack
      -- The Call Stack will tell you at the top what was the last function call before crashing and what function calls led to that function call.
      -- Next to the function names there is the file that the function is defined in and the line number the code was executing in that function.
      -- In the Variables section you can inspect variables that were present at each function call.
      -- Based on this information you are often able to see what crashed or get a better view of what you need to inspect more in your code.
      - The dmp file can be opened in Visual Studio
      -- Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core
      -- Drag and drop the dmp file to Visual Studio
      -- In the window that opens click to "Debug with Native Only" http://i.imgur.com/OgyU2kM.png
      -- In the window popup click "Break" http://i.imgur.com/4jDzqRn.png
      -- You are now in a state like you would have hit a break point in the code or a crash while debugging. You can inspect the call stack and the variables.
      Edit and continue on windows. When debugging this allows you to change the code and without restarting the server apply those changes so they actually work ingame.
      - Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core
      - In solution explorer right click on worldserver and select "Properties" http://i.imgur.com/rTNEF9O.png
      -- In Properties select "Configuration Properties>Linker>General" and set "Enable Incremental Linking" to "Yes". http://i.imgur.com/caQqwN5.png
      -- In Properties select "Configuration Properties>Linker>Advanced" and set "Image Has Safe Exception Handlers" to "No". http://i.imgur.com/FYzN8Ks.png
      -- In Properties select "Configuration Properties>C/C++>General" and set "Debug Information Format" to "Program Database for Edit And Continue". http://i.imgur.com/pxQ6I8N.png
      - At the top of the window select "Tools>Options". In the Options select "Debugging>General" and in there select "Enable Edit and Continue", "Enable Native Edit and Continue" and "Require source files to exactly match the original version".
      - Compile the server for the changes to take effect.
      - Set up "The second slower way of debugging" (I did not test edit and continue on other configurations)
      - Start the authserver normally
      - Start the worldserver by selecting "Debug>Start Debugging".
      - Try edit a cpp file a little and save it.
      - At top of Visual Studio window select "Debug>Apply Code Changes" and wait until the changes are applied. Warning: it can take considerable amount of time for the changes to be applied. http://i.imgur.com/77pb58E.png
      - If you have issues, be sure to check the error messages in Output. You can view it by selecting "View>Output" http://i.imgur.com/4cIznW9.png
      - This guide was written based on https://msdn.microsoft.com/en-us/library/esaeyddf.aspx and https://blogs.msdn.microsoft.com/vcblog/2015/07/22/c-edit-and-continue-in-visual-studio-2015/
      Linux:
      First we need to compile the server in debug mode.
      - Compile the server with the cmake flag -DCMAKE_BUILD_TYPE=Debug

      Debugging on linux. You can debug on linux by using GDB.
      - Here is a good video about it: https://www.youtube.com/watch?v=sCtY--xRUyI
      - Basically you
      -- Start the authserver
      -- Start the worldserver by using "gdb ./worldserver"
      -- Enter breakpoints by using break command on gdb
      -- Use the run command on gdb to start the server
      -- You are now debugging
      - You may also be interested in using VScode or some other more visual debuggers. https://www.youtube.com/watch?v=B0xTgyCwsAo
      Crashlogs on linux. Once you have a way to reproduce a crash you can get a crashlog that can help you resolve it.
      - Take crashreport.gdb from /contrib/debugger from source folder and place it to your server folder
      - Start the authserver
      - Start the worldserver by using "gdb -x crashreport.gdb ./worldserver"
      - Reproduce your crash
      - There should be a backtrace.log in your server folder that contains information about the crash like the callstack and variables in each function call in the call stack
      - This guide was written based on https://github.com/TrinityCore/TrinityCore/blob/master/contrib/debugger/README
      Running valgrind on linux. This helps you find memory errors like invalid reads and writes and memory leaks.
      - Here is a good video about it: https://www.youtube.com/watch?v=fvTsFjDuag8
      - Basically you
      -- Start the authserver
      -- Start the worldserver by using "valgrind ./worldserver"
      -- Run your code that you want to analyze and close the server
      -- The console or an output log should contain the valgrind log
    • By meeek
      Hey, I've been trying to compile from github the core from 6.2.3/6.2.4, I'm well aware its stopped developing. I cannot get it to configure properly in CMake, nor can I obviously build it.
       
      I'd be willing to pay for help and get this working and running. I want to develop my own server on my freetime as a learning project and for entertainment. I can't find any core for WoD, sadly.. Very hard, would appreciate any quick help
       
    • By Ramboknife
      So I'm trying to set up a debugging process where I can see what functions are being called when I do certain things in game, that way I can hopefully locate exactly which functions in which cpp files might possibly be involved with the bug I'm trying to fix.  Is something like this possible?  I can get VS Code to launch my worldserver or attach to the worldserver process but beyond that I'm not getting any other information out of the Call Stack or anything when I make certain actions in-game.
      Thanks
    • By labaouici
      Hello!
      I was checking my DB but I didn't find any table that could tell "this is when it will happen"
      I wonder how it work, I activated it but is there a table to put the unix time? (like to do : every wednesday, at 15:25:30 there will be the distribution)
      Thanks!
×
×
  • Create New...