Jump to content
  • We are looking for staff for the Wiki area!
    If interested please
    click here and select "Documentation Team"

  • Downloading the MaNGOS sourcecode

    Important Things to remember

    There are Five MaNGOS cores, each designed to support a specific version of WOW.


    Core Supporting Client Version GitHub URL
    MangosZero Vanilla 1.12.1(5875), 1.12.2(6005) & 1.12.3(6141). http://github.com/mangosZero
    MangosOne The Burning Crusade 2.4.3(8606). http://github.com/mangosOne
    MangosTwo Wrath of the Lich King 3.3.5a(12340). http://github.com/mangosTwo
    MangosThree Cataclysm 4.3.4 (Build 15595). http://github.com/mangosthree
    MangosFour Mists of Pandaria 5.4.8 (Build 18414). http://github.com/mangosFour
                The default branch of all the repos is always the latest released version, and only hotfixes are applied to it.
                The development branch contains the ongoing development work.

                If you omit the --recursive parameter, NOTHING WILL BUILD CORRECTLY - You have been warned !!!

    In the examples below, we are using MangosZero !

    Open your favourite git command line util ie. 'git bash' or 'git shell'
    Then type the commands below:

    Cloning the default branch of the repos

    Cloning the Server Source into the folder serverZero
    git clone https://github.com/mangoszero/server.git serverZero --recursive --depth=10


    Cloning the Database into the folder dbZero
    git clone https://github.com/mangoszero/database.git dbZero --recursive --depth=10
    These will create a server and database folder, which then contain the contents of each repo.

    As the Mangos Repos now use git submodules, cloning using the "recursive" flag will pull in all required submodules automatically.
    i.e. Eluna, ScriptDev3 etc.

    If you forget to include --recursive, you can still get the missing files

    git submodule init
    git submodule update



     NOTE:   Removing the --depth=10 flag will cause the entire history to be downloaded, normally only needed be developers or when bug hunting.

    Edited by antz

    User Feedback

    Recommended Comments

    To turn a previously downloaded repo without history into a dev mode one that does, I used this command


    git fetch --unshallow



    To do the reverse, I am trying this, but it is not working so far..


    git fetch --depth 10

    Clear local (now hidden) data:

    git reflog expire --expire=all --all
    git tag -l | xargs git tag -d
    git gc --prune=all


    Edited by Pysis
    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use