Forum > Tutorials
[TUTORIAL] Sending Patches To The Client Through The WoW App
<< < (4/8) > >>
Swampdog:
Anyone have a Trinity patch for this that works since they redid logging? In August of 2012 the TrinityCore community was told there would be something added to the wiki to help people understand the logging system changes but it must not have been important enough to actually get done. :(
I am attempting to manually patch into my copy of the Stable TDB335.51 (2013/02/14) that I am using.. I have everything patched in. But when I go to compile it, I get a bunch of fatal errors centered around the logging, mainly "error C2039: 'outString' : is not a member of 'Log'" and one "error C2039: 'outStaticDebug' : is not a member of 'Log'"
I looked in Log.h and Log.cpp to try to grasp what functions I might need to replace them with. In the Log class I see that they added LOG_FILTER_TYPE in the parameters but again, no real documentation anywhere on what those might be.
While a patch using the new logging system would be awesome, I'm not opposed to figuring this out on my own if I need to. After several hours searching the Trinity forums and trying to get a grasp on what I might need to do, I could really use a nudge in the right direction. Or if this "phantom" documentation exists somewhere, a link would rock!
Thanks in advance if anyone is able to help! :)
schlumpf:
Just remove those logging related lines. Logging isn't important.
Swampdog:
--- Quote from: "schlumpf" ---Just remove those logging related lines. Logging isn't important. --- End quote ---
Thanks Schlumpf! I had hoped to keep them for debugging purposes. But knowing they aren't critical and that I can remove them helps. I'll comment them out for now in case I can find out more about the logging system later.. Or maybe even just convert them to generic outInfo messages without worrying about all the different variables and such that were passed through in the messages before. But then I guess I'd have to figure out the whole LOG_FILTER_TYPES and how to modify it in the worldserver.conf for logging.. lol
Thanks again for your response! You rock! :)
Jpp:
I followed the tutorial, but I ran into an issue related to logging on to the server.
Here is the error. i(.)imgur(.)com/9XOiSCy(.)png
I seem to have tracked it down to these lines if this is any help. pastebin(.)com/6p7EnF5t
In the core folder I have the folder called 'patches' with a MPQ file inside it called '12340-enUS', my client being 12340 as well.
I got my hands on a client patched to 12346, and tried to change allowed patches to 12347 instead of 12341, and change the name of the MPQ too, but it didn't work, so I doubt it's related to the client, but again, I could be wrong.
Thanks, Jpp
stoneharry:
--- Quote from: "Jpp" ---I followed the tutorial, but I ran into an issue related to logging on to the server.
Here is the error. i(.)imgur(.)com/9XOiSCy(.)png
I seem to have tracked it down to these lines if this is any help. pastebin(.)com/6p7EnF5t
In the core folder I have the folder called 'patches' with a MPQ file inside it called '12340-enUS', my client being 12340 as well.
I got my hands on a client patched to 12346, and tried to change allowed patches to 12347 instead of 12341, and change the name of the MPQ too, but it didn't work, so I doubt it's related to the client, but again, I could be wrong.
Thanks, Jpp --- End quote ---
Pretty sure it needs to be 12340enUS.mpq. Can't remember off the top of my head. Trace the find patch function in the if statement you linked.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
|