antz

It has taken much longer than planned, but via MAGNET (MAnGos oNline Editing Tool), the packet formats can now be documented and exported to the forum.

This are errors, but not serious ones. Sometimes these errors are introduced when things are updated. - In the fullness of time they will get fixed !! However, if you feel about having a go at fixing them, please be our guest :D

That error message indicates that you are missing the OpenSSL dll's that are needed. Installing OpenSSL will correct the issue.

Please see my Answer in this topic:

If anyone really wants to have a go at creating a mangos core support nuClassic, then please contact either @madmax or @antz directly and we'll see what we can do to help you get started.

The Short answer is yes.... eventually Let me explain why..... 1) In the Original Wow clients Vanilla, TBC, WOTLK - these used locked opcode values for each packet sent between the server and the client. Since Cata each patch randomised these values, thus meaning we would have to reverse engineer and work out the values for every opcode value for that patch version. 2) The Data structures are based on the BFa structures not the original Vanilla structures. 3) The nuClassic client would have to be 'patched' like all versions from Cata onwards, to use an ip address for the realm server rather than the Bnet server. What this means is..... To support the nuClassic client, it would effectively be a new core version of mangos. Not impossible to support, but that's a lot of work I would also add that it will be almost impossible to play using the original Vanilla client and the nuClassic client on the same server (for the reasons mentioned in 1 & 2 above).

@thimmy- Are you able to post the build log so that we can we what the error is ?

Remove the # from the beginning of the lines for the values to take effect

The Pathing has been extensively tested over the years, can you give us a specific example of where this is failing ?

also... is this a fresh clone of the database GitHub repo ?

I do remember seeing a commit for Zero (can't remember whether it was for the DB or code) which corrected this. - It might be possible that some updates have reverted this in error. Maybe a quick github search of the repos might find it, although since this is an older issue, possibly try http://github.com/mangosarchives

Changed Status to Completed Changed Priority to New

Changed Status to Completed Changed Version to 21.14 (Master Branch)