Jump to content
TrinityCore

Leaderboard

Popular Content

Showing content with the highest reputation on 03/31/16 in Posts

  1. Changing the gamebuild and restarting server didn't work, still incompatible. Tried that with 127.0.0.1 and 192.168.1.10 still getting incompatible realm. EDIT: /sigh so apparently my dyslexia and inability to check each number kicked in..... i put in '21335' instead of '21355'. Connecting now....
    1 point
  2. If you look at cmake you will see an option "with dynamic linking" make sure it is unchecked to build it as the old core where its 2 core bins and your configs and tool bins by placing the check in place it splits the systems into separate dlls which is nice to have when you are constantly changing things and debugging Delete everything in your build directory and rerun cmake if you have the check in the dynamic linking try removing the check mark and rebuilding the tools that way and see if its any better i really think this is your issue your having with patching on systems you didnt build the bins on
    1 point
  3. are you building core in dynamic or static? If you are building in dynamic i believe you need to place a copy of common.dll in the same folder as the patcher and wow.exes for it to work Im not sure though i havent explored the linking to see for sure if they split the common.dll on patcher besides the dynamic linking and the overall bnet restructure thats the only change i can think that would impact you like this If you are building dynamic try changing over to static in the dropdown and rebuild tools and try that patcher on the other machines If it patches that is your problem you failed to include one of the required dlls from build directory
    1 point
  4. Do you have openssl on that machine? or Microsoft redistributables? If not this may be your issue
    1 point
  5. FFS when will you people learn that copying the patched exe from another machine alone IS NOT ENOUGH? You need another file in wow installation folder - tc_bundle.txt
    1 point
  6. I don't really recommend it but you can get the AI* from an Unit* and then dynamic_cast the UI to your custom AI type, calling whatever methods you have there (including setters).
    1 point
×
×
  • Create New...