Leaderboard

Unfortunatly you will have to build TC on your win machine. However you can build just the tools. In cmake deselect the "SERVERS" and "SCRIPTS" options and select the "TOOLS" option. That should do it. Good luck, Carbenium

Hi there, this question is specially directed to trinity devs, as I am very curious (note: only for curiosity sake, it is not my intention to put any kind of pressure on opcode implementing!). I've read the opcode implementation, but I have to say there is a thing I did not get correctly. I only saw in code, the definition of the opcode macro name, along with the class which is responsible to handle it, and it is being registered as UNHANDLED, NEVER, etc.. But what I did not find, is the opcode value itself. Am I wrong guessing that opcodes are sent in binary with some value and format, like <opcode_value><opcode_param1><opcode_param2> and the like? I always thought that the value for loot=1, cast=2, etc (only examples). How do they work? This is the part I have missing long time to learn how it work, but from my point of view, and my guessing, it is very similar to what a CPU receive. Any hint on this? EDIT: I recently saw https://github.com/TrinityCore/TrinityCore/blob/6.x/src/server/game/Server/Protocol/Opcodes.h which was exactly what I was looking for. So just a question missing, when an opcode is missing implementation? Is it because the opcode value changed, because there is no code to "construct" the packet, both? Thanks for the clarify, I just want to understand the work done here better

How to enable debug logs How i get good crashlogs under Linux? Under linux compile with the following flags: declare -x CFLAGS="-m64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O0 -g3 -ggdb3 -pipe -msse3 -fno-strength-reduce -fno-delete-null-pointer-checks -fno-strict-aliasing -frename-registers -rdynamic" declare -x CXXFLAGS="-m64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O0 -g3 -ggdb3 -pipe -msse3 -fno-strength-reduce -fno-delete-null-pointer-checks -fno-strict-aliasing -frename-registers -rdynamic" cmake ../ -DCMAKE_INSTALL_PREFIX=/change/path/to/trinity -DCMAKE_BUILD_TYPE=None If your core lags to much change -O0 by -Og or even -O1. Then copy TrinityCore/contrib/debugger/crashreport.gdb to your Trinitycore's bin directory and create a file with the following lines and make it runable: cp backtrace.log backtrace.`date +%Y%m%d-%H%M%S`.log screen -A -m -d -S tri_world gdb -x crashreport.gdb ./worldserver -c ../etc/worldserver.conf When your core crashes you will have a file called backtrace.log on your TrinityCore's directory. How i get good crashlogs under Windows? Select the dropdown on compile mode and change from RelWithDebug to Debug, Release mode crashlogs are useless.