Mangos – Open Source WoW Server
The following guide will explain how to grab and build your Own server for World of Warcraft, it does not go into how to Set this up, if enough people require this – I can make another Guide..
Getting the Mangos Source Code
1. You need to download tortoisesvn from this site: http://tortoisesvn.tigris.org/
2. Install the program and it may ask you to reboot – do so.
3. Create a directory where you wish to hold the source code, I named my Sources
4. Create another Directory inside here called Mangos.
5. Right Click Mangos Dir and now click SVN Checkout
6. Put in there: https://mangos.svn.sourceforge.net/svnroot/mangos/trunk
7. This will now Check out the latest Code from the Sources – it will tell you at the end what Version it is up to.
Getting the ScriptDev2 Sources
1. Open up \Mangos\src\bindings
2. There should be a directory already there called “Universal” & Makefile.am
3. Create a Directory Called ScriptDev2
4. Right Click ScriptDev2 and Choose SVN Checkout
5. Put in the Address: https://scriptdev2.svn.sourceforge.net/svnroot/scriptdev2/
6. It will now grab the latest Files for ScriptDev2.
Getting and Applying the Auction house Bot patch
1. Download the Patch files first: http://filebeam.com/aef8c6409bd6cb3be3a200cd7ec3f97e
2. Extract these somewhere.
3. Right Click Mangos Dir and tortoisesvn –> Apply Patch
4. point it to the first file AuctionHouseBot_v5.6.1.patch
5. Two Screens pop up – right click inthe files one – Apply all.
6. When all done (they all go grey) – close the window.
7. Repeat with optional_ahcommands_v5.6.1.patch
What have we achieved so far?
You should now have a directory Called Mangos which contains all the latest sources from both Mangos and ScriptDev2 also patched up with the AuctionHouse Bot 5.6.1. At this stage – its juts pure source code – we need something to Compile it with….
Visual Studio 2005 + SP1
I am using Visual Studio 2005 updated with SP1 via windows updates – if you are using a newer version, it may differ.
1. Open up mangos Dir then WIN.
2. mangosdVC71.sln is for Older (than 2005) version of Visual Studio.
3. mangosdVC80.sln is for Visual Studio 2005.
4. mangosdVC90.sln is the Latest Visual Studio.
5. We shall double click mangosdVC80.sln and up pops Visual Studio.
6. One time Only – Click on BUILD / Configuration Manager.
7. Active Solution Configuration – Change to Release.
8. Click Close.
9. BUILD / Build Solution (or press F7)
10. This part takes some time – you need it to finish with
========== Build: 10 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
11. When you close, it asks to Save (as you have changed it) – say yes.
ScriptDev2
1. Go Inside \Mangos\src\bindings\ScriptDev2
2. Same as above ref SLN file – we shall open scriptVC80.sln
3. One time Only – Click on BUILD / Configuration Manager.
4. Active Solution Configuration – Change to Release
5. Click Close
6. BUILD / Build Solution (or press F7)
7. This part takes some time – you need it to finish with
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
8. When you close, it asks to Save (as you have changed it) – say yes.
The Finished Files
1. \Mangos\bin\release hold all the files that go into the Root of your Server.
2. \Mangos\src\mangosd\mangosd.conf.in is the Mangos.Conf file – check this now and then for Changes.
3. \Mangos\src\realmd\realmd.conf.in is the realm.conf file.
4. \Mangos\sql\updates is the SQL updates fro Mangos.
5. \Mangos\src\bindings\ScriptDev2\sql\Updates is the SQL Updates for ScriptDev2.
Updating from this point forth.
1. Right Click Mangos Dir – select UPDATE
2. Shows you what files are updated, take note if Mangos.conf has changed and Version Number.
3. I have my Mangos Dir named to the version so I can remember what version it is from and to, thus easier to select any SQL updates.
4. Repeat for \Mangos\src\bindings\ScriptDev2
5. Open up the SLN files as above.
6. Select BUILD / Clean Solution (very important)
7. Now Select Build Solution (or F7) and wait.
8. Do mangos First, then ScriptDev2 – very important they are in this order.
Database files
1. You can also grab the Database files via SVN the same method.
2. Create a Directoy called Univied
3. Right click – SVN Checkout
4. https://unifieddb.svn.sourceforge.net/svnroot/unifieddb
Problem that can go wrong
The Auction House Bot can cause the build to fail – if this is the case, then you have to get a fresh set minus the Auction House Bot or check to see if there are any updated files – changes they make to to the source quite often breaks this addon.
They mistype the source and this filas the build – simply a case of Waiting until they have fixed it.
Same problems with ScriptDev2 – make sure it says ========== Build: 10 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
If it says x failed – then it wont have the complete files to run a server.
Once you have the Process Set up – its a simple enough task to update, Build first to make sure it works and then apply SQL Patches – copy files across and you good to go. make sure both are set to release, once saved, no reason for them to revert to Debug unless you get the files from Scratch again.
