antz

Cmangos is nothing to do with mangos. They are a fork of mangos from about 6 years ago. We have made extensive changes since then. The hides in the wiki are the definitive source.

The realms is common across all the cores, so you can use a version from any core. However, the furthest I was able to get to was the create character screen.

Hi @biruni666, could you let me know which Client and Mangos version you are using and also some examples of Npc's for me to check ?

MySQL 8.0 is not currently supported by MaNGOS

Please note that extractors found elsewhere on the internet are unlikely to work with mangos. Please you build the project, compatible extractors are also built. These are the ones that should be used.

Boost is not used in Mangos. Looking at your pathname, it mentions Trinity core - They are not part of Mangos and are a completely separate project.

The build system can't find OpenSSL, all the messages mentioning:- 'SSL-EAY' are OpenSSL related

I know several years ago that I user worked on getting mangos to compile and build on a raspberry pi. - At the time we implemented any changes suggested to help him. But I can't recall whether he ever got it fully running.

This is not trivial, but can be done !! There is a script in the Database Repo Tools\cleanup folder called: characters_convert_s1099_to_11391.sql characters_item_duplicates_remove.sql characters_mail_items_cleanup.sql characters_pet_data_cleanup.sql Running each of these should theoretically upgrade the database to be compatible with MangosOne. - However, I am aware that this has not been tested in a long long time. If anyone is willing to give these a go and report back on the issues found, that will help us a lot.

I have added a spaces check in the new version of easybuild currently in testing. - Hopefully it will ready soon

It's simple really, just create a GitHub user and password, then use them. GitHub are tightening their security up all the time.

Thats because the develop21 branch no longer exists, just clone the master branch. - I have updated the above docs to try and cover the changes.

can you check something for me..... Inside your ServerZero folder, do you have the following folders: |-dep |-src | |-modules | | |-Eluna | | |-SD3 | |-realmd | |-tools | |-Extractor_projects |-win

Please see my reply to this question: ----== Google Translate ==---- Bitte sehen Sie meine Antwort auf diese Frage:

We use an online tool called Magnet to update the translations, or failing that you can apply updates directly to the GitHub repos. Any help is gladly appreciated.

I am currently working on a permanent fix for this issue: As a temporary fix, you can apply the follow SQL to the realm DB's: For TBC: ALTER TABLE account MODIFY COLUMN `expansion` TINYINT(3) UNSIGNED NOT NULL DEFAULT '1' COMMENT 'Which maximum expansion content a user has access to.'; For Wotlk: ALTER TABLE account MODIFY COLUMN `expansion` TINYINT(3) UNSIGNED NOT NULL DEFAULT '2' COMMENT 'Which maximum expansion content a user has access to.'; For Cata: ALTER TABLE account MODIFY COLUMN `expansion` TINYINT(3) UNSIGNED NOT NULL DEFAULT '3' COMMENT 'Which maximum expansion content a user has access to.';

I have answered this in more detail in the post below:

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 ?