ATTENTION! There is a new release so this is now outdated and unsupported!
Well its finally here! The release that answers everyones questions and fixes everyones bugs! It took me about 8 hours of consistent coding and I believe that it is perfect. The only problem and thing I could not do was get the database updated. Besides that we have updated many things and added many new things as well.
Here is the list of newly added items:
*ScriptDev2 231 Actually Works!
*Auction House Bot Added
*Optional GM Island Vendors in Batch File
*Weather System is now Fixed!
*Lan Feature in Batch Now Works
*Transports Flooding Mangos
*DBC Files Already Included
…And of Course Much More!

REQUIREMENTS:
1. MySQL Database and the Guide on how to Install MySQL
2. World of Warcraft Client version 2.3.2
3. Updated DBC’s, VMAP’s, and MAPS.
DBC’s are already included as part of this release!
4. Mangos Server :
Reaper Mangos 5054 SD2 231 UDB FULL | 17.09 MB | File Beam
Reaper Mangos 5054 SD2 231 UDB FULL | 17.09 MB | Rapidshare
Reaper Mangos 5054 SD2 231 UDB FULL | 17.09 MB | Mega Upload
Instructions Coming Soon
Basically since the installation instruction is just the same as before release, and i’m currently writing on the fresh installation guide so there’s no need to write it everytime there’s a new release available for download :)
in the meantime you can read the previous fresh installation guide :)
Leave a response
2.3.2 is working mostly fine for me, Getting to the most Stable DB with the most bugs fixed is my hopes and wishes.
I havent spotted any large bugs. What’s bugged?
My favorite feature which seems glitched in latest is maybe the XP fun rate seems slow no matter what I set it to though.
Hey I would just like to thank Oatman and Reaper. My server when I got it up it was running just fine when I had wow 2.3.2 but I upgraded it (dumb move on my part) But I am not in a big hurry to get it back up and running. I feel sorry for Oatman and Reaper to get all of the comments that ask to make a new one now now now. But right now i am taking computer programming and it seems like it would be a pain in the @$$ to do what they do. So hey Oatman and Reaper, just take your time and don’t feel rushed. And I would like to thank you guys again for making something so simple yet so effective that someone like me can make it work. You guys are awesome. Thanks.
Hey, just sending out a thanks to the Reaper-mangos team. I don’t have enough time to learn to compile my own mangos server so it’s nice to have something with a batch file and pre-extracted dbc files. Responding to oatman’s post, I would like a quick fix, then take your time to compile a full release. Currently I can’t even run 2.3.2 as I’m getting a runtime errot no matter how many different computers I try it on or download new copies. So a fix that allows me to run a 2.3.3 server at all would be great. Wow, I usually just lurk here waiting for updates, but jeez, most of the people that post asking for help are pretty retarded. Learn to read previous posts or go back to previous forums to get help before you post. Please, for the good of the people who are just reading looking for answers, stop asking the same questions over and over again…
I’d personally like to see a 2.3.3 update as long as it isn’t too buggy.
It wouldn’t show who logins in in realmd.exe but some release would show in mangos server but since I doesn’t you can always do info in mangos server
-B
Ok, to my previous issue, I have noticed someting fishy. Even when I log in and play locally, my realmd.exe cmd widnow doesent’ show anything, I remember in the previous releases it would show who loged on. Now nothing happens. Might this be a problem? and how would I be able to fix it? If anyone knows how, please give me a shout, it is greatly apreciated, thank you :)
-Death Scythe
i would actually like the version that runs 2.3.3 for now if that works without any major issues. If and when a stable/official/compatible version comes out, it would be nice to have an update on that…
… idunno. Am i too greedy for wanting both =P
Either is fine. I just hope a compatible release comes out soon. Thanks Oatman!
@killer126dies
Because its tasty duh..
Why is Mangos Called Mangos?????
Anyone Know?????
@Oatman
Dude, I know I speak for many when I say Thank you for all your hard work. No need to apologize, and don’t rush. The hours of enjoyment I’ve had because of your work is worth the extra couple of days, and that’s saying the least.
You can’t expect that Blizzard won’t at some point address the free server issue by making their launcher.exe and wow.exe private server hostile.
So to all those that expect to patch and quickly get back on private servers with Blizzards product. I have some swam..er beachfront land in Florida I’d like to unlo..er sell. Give me a call!
Gotta Keep em Separated!
Just would like to say personally I would like to take a momment and thank all of the people developing the Reaper Mangos… Since I started to use it I have enjoyed the experience more and more.. Just want to pat on the back all of the people working on this project.. Your hard work make people appreciate what you do for us.. I have been working with mangos since one of the first builds.. Thanks again
-B
heres a couple of links for 2.3.0 patches…..
EnUS
http://findfiles.com/list.php?string=WoW-2.3.0-enUS-patch.exe&size=725924282&db=Mirrors
EnGB
http://www.findfiles.com/list.php?string=wow-2.3.0-engb-patch.exe&size=913540356&db=Mirrors
i got mine from one of these links, its 871.22mb, so expect a little time for download, took me about 35-40mins, or just google it, u may find a faster site :)
hello every1 how is it going
yes if you patched… rename wow.exe and run repair… it will put you at 2.0.0.. so then you need to patch back up to 2.3.2.
There is a 2.3.0 patch available on the web…like at filefront…its about 600mb though.
@ Stefano
Here is a link on rollback instructions
http://www.reaper-x.com/2007/09/29/how-to-revert-to-previous-wow-patch/
So basically every person that wants to connect to my server has to roll back their wow version? That’s not going to happen. I hope there is some quick fix to all this. =\
I just got a registration page and invited tons of people to my server and even put it on a wow server site, this doesn’t look good at all.
# Stefano
To roll back your client to version, all you have to do is take out your WoW.exe file from your World of Warcraft installation folder, and run the repair tool, it will restore your files back to the first version (2.0.0 if my memory doesen’t fail me)
# n1t3
Yeah this might sound stupid, but to say the truth I wouldent know where to change those settings (accept it from LAN ip or from WAN ip) if it would not be to much to ask, could you give me a little more detail on where to check/change that? thank you :) and I tryed the net stop/start mysql, it sadly didn’t help the cause.
Hello , I’m A m8 Off Koentje25 .
So When u Say We Could RollBack The Client …
How Exactly can we do this ??
Thx # Grtz
.Stefano
@ koentje25
The current release of Reaper-X Mangos DOES NOT support the new 2.3.3 client.
That’s why you are seeing that message. Either roll back your client or sit tight and wait for another Reaper Release which does support 2.3.3.
hello thx fir helping
i can make my acc now.
but again i has a problem.:s
when i try to log in i get this message on my screen..
http://imgday.com/uploads/73282prob2.jpg
what i need to do know?
my version of wow is 2.3.3 (7799)
plz help
kind regards
#jodh do you have windows set to open your wtf file automatically to txt format? if you do this could cause an issue with mangosd.exe to read it… you might need to replace your mangosd.conf file with another one. i had this problem once and that is what i did.. not exactly sure why it worked but it did and havn’t had a problem from it yet.
Hi, everone i have a problem, i had the server going but when i went to get on today, whe i try to run mangosd.exe the screen flashs on and then closes its self out, anyone know whats wrong? realmd.exe is working just fine(if that helps…) thanks for any replys in advance.
#Death Scythe
i’ve had this problem a few times. make sure that your realm is set to accept connections on either your public IP (www.whatismyip.com) or your home IP (cmd prompt: ipconfig) if you have changed something on your server you may need to restart it. you might also restart your mysql .. go into start menu and select run. then run cmd. at the prompt type (without the quotations) “net stop mysql” after it has stopped restart it by typing “net start mysql” it’s worked for me before not sure if it helps or not..
Hello, you guys are doing an exelent job, I do have a question though.
I got the server running great, I can log in even with my dns in the realmlist.wtf file
But the problem is, my friend can’t properly log in, The account is acepted, then he get’s redirected to the ‘choosing your realm’ window, he selects the only server on there wich is mine, and then it says ‘loging into game server’ and it never does, it just brings up the realm list again. And this repeating proccess never stops. Btw I’m behind a router, but forwarded all the port’s I could find in the configuration files, I don’t think that might be the problem,but who knows, I’m not the most intelligent :P.
BTW thanks for your help in advance
-Death Scythe
#koentje25 helps if you have your messanger on to recieve messages… your problem is easily solved.
go into your mangosd.conf and look for this line
# Data directory setting.
# Important: DataDir needs to be quoted, as it is a string which may
# contain space characters.
DataDir = “C:\WOW\data”
in yours your DataDir isn’t set correctly to the folder that you have your maps/vmaps etc. in… you need to change it so that the DataDir = “C:\WOW\data” is the directory that you have your vmaps/maps in.
Some one please help me.
AlexT | Jan 24, 2008 at 17:46 / 5:46 PM | Links to this comments | Reply
hello
i try to make it. everything works fine until ill start mangosd
it start and then it give an error..
this is the link to a screenshot.
http://imgday.com/uploads/88813mangos_prob.jpg
plzz help me..
i don’t know what to do.
i reinstall everything for 3times and i still get the error.
if you can help me
pm me
BBFuryy_@hotmail.com
kind regards koen
@Freze: Simple answer. People who play on private servers should keep a separate Warcraft non-patching folder for their private gaming copy of Wow which they do not patch every time Blizzard patches. Pointing the realmlist.wtf away from blizzard will prevent the patching that will usually break private server compatibility.
If they want to just have one folder perhaps because they cannot spare 8 gig of disk to maintani two copies, then they are going to need to decide to patch and break their private server play or not patch and be unable to log into Blizzard.
Ehh i REALLY needs the new version fast nobody can play on my server the new 2.3.3 is just camed out..!
Freze
#weiss935 just go to any merchant… or create one using quice. you can add items to a vendor using quice or ingame using .addvendoritem ####
i think quice is easier tho.
van someone tell me how to set out own merchants?
Thank you all for help! But i have a question: I would like to make my server PUBLIC. I opened the ports and set my external IP as the server’s address.
I use wamp and a simple registration page for mangos.
But at the previous server (2.3.0) when other friends made an account on my server and tried to log in it stopped at LOGGING IN TO GAME SERVER.
PLEASE HELP!!
Hi all. Before I started my own server I played one that had everyone start the game running at 2x speed. Does anyone know where to change it so I can have my friends start that way without having to modify their speed every log-in?
Some one please help me. Ok here it goes. You know that command .maxskill it sets your skill to max. And you know how at lvl 70 those fields only go up to 300. It gives out 5 for every lvl. Things like Defense and your weapon skills.
Where can I change so it give out instead of 5 more like 10 for every lvl?
Thanks for you help!
Thank You
@those who need to revert game to 2.0.0 so u can reinstall the patches, i delete the wow.exe then run the repair tool, it will reset all your files to 2.0.0, then just reapply the patches to the version needed. hope it helps :)
P.S. it will also change your realmlist.wtf file back to original, so dont forget to change to your IP used :)
@FFS: You have an issue with your MySQL install. If you have existing character data you need to retain be sure to save that to an SQL or CSV export somewhere safe. Put it on a flash drive stick memory or something. Completely uninstall MySQL. Reboot. Reinstall MySQL. Be sure to take defaults all the way through but be sure to check the allow access to ROOT from other machines setting. Reboot (yes again). Load SQLYog or whatever and make sure your database works.
Run a clean install of 5054 get it working with your machine. COPY those working CONF files to a folder on your flash drive named Localmachineonly.
Trial and error with another machine on your LAN and once you get it working copy those CONF files to your flash drive in a folder named LANplayworking or whatever.
Write down what changed ni the realmd realmlist if anything. I dont recall having to change anything for LAN play there.
NOW install Hamachi and make sure your friend can see your LAN like make a shared folder and have him try to browse for it.
Now the only thing that really changes is (A) Hamachi might have security blocking your ports so turn off Hamachi security settings on your machine and your friends machine. (B) your local IP changed too. If you had to change 127.0.0.1 to your local IP for LAN play before then you will need to change it from 127.0.0.1 to your NEW Hamachi IP again. Whatever chaneged between your two sets of CONF files changes in the SAME way for Hamachi.
That’s it. I’ve done it and it was unimpressive so I went with the big leap to having one machine oepn to the internet instead which works much better because I hate having to setup Hamachi just to let people in. It just feels like “Your Kung Fu is weak”.
hey i just wantet to say to reaper-x that i found the WSG coordinates if he dont got em i just ditten found em on the DB for this version:D
.goxyz 1519.53 1481.87 352.024 for alli start loc
.goxyz 933.331 1433.72 345.526 for hord start loc:D hope you guys can use it:D
Yeah for those that are always asking for the mangos executable to match the current WoW version like 2.3.3, perhaps you are missing the point. Once I have a perfectly working system which is “good enough” for me, I don’t ever want to patch again. The Wow version matches the Wow database and the Mangos Wow version matches the Mangos database. Life is good. Everytime we increment the Mangos version to match its mostly more work for me upgrading the database and all the risk that goes along with it that I’ll trash my DB somehow =).
I vote – take your time – I’m exciting when a fix comes out and EH not so much when a Tuesday patch comes out from Bliz.
THIS IS HOW YOU STOP THE AUTO-UPDATE FROM 2.3.2 to 2.3.3!
#1 Make sure your in version 2.3.2.
If not, revert http://www.reaper-x.com/2007/09/29/how-to-revert-to-previous-wow-patch/
#2 Your realmlist.wtf file should look like this:
—————————
set realmlist 127.0.0.1
set patchlist 127.0.0.1
—————————
If the patchlist is not specified, then the launcher will automatically assume its going to ‘us.version.worldofwarcraft.com’ and automatically update the next patch. This method will disable updating even while using the launcher.
Hope this helps
Quick question. Is there a setting that would allow the player to do more damage? We don’t have many people, but would still like to take down the big bosses and such.
i dont know if this question was answered or not so sorry if i am re-asking but… when i run reaper-x-mangos.bat and choose option 5 (Mangos Config Editor – MaNGOS.conf/Realmd.conf/ScriptDev2.conf)
i get a message that says “‘This’ is not recognized as an internal or external command, operable program or batch file.” i have no idea how to fix this or if i am doing something wrong pls help me if you can. my windows live id is farnoreth@hotmail.com thx
5054 Is not compatible with WoW 2.3.3 Read the above comment by Matt
Eek. My wow client autopatched with the launcher by accident and is not on version 2.3.3. I rebuilt the maps\dbc\vmaps folders and put them in the data folder…but now I get a client version error with 5054. Any fix for this?
SWEEEET I GOT IT WORKING.. ALL I DID WAS CHANGE THE PORT.. I could connect then and then i changed the port to default, power cycled my router and modem and restarted the server and realm and it works… THey dont block the realm port you just need to power cycle your gear… Let me know if this fixes anyone elses issue.. IM SOOO HAPPT
when is the next mangos upate being released to everyone?
So after my post yesterday and seeing others are having the same problem, I researched the problem out a bit and found a solution. Roll back WoW to the previous patch!(For those using: Reaper Mangos 5054 – Easy WoW Private Server for WoW 2.3.2 -Critical Update-) To do this follow the instructions at this link:
http://www.reaper-x.com/2007/09/29/how-to-revert-to-previous-wow-patch/
In order to keep WoW from auto updating to the new patch just keep the two seperate .exe files :)
@ Everyone asking for Reaper to Hurry Up
Some of you may be joking but you guys do realize that Reaper and Oatman and whomever else are under no obligation to release anything else at all right? This stuff takes time and testing and still at that there are hundreds of questions in the comments (see above).
They will release it when they can and they’ve tried to work out as many bugs as they can. They are also limited to when the Mangos team releases a compatible SVN for them to compile.
I’d suggest if you can’t wait then goto http://www.mangosproject.org and read up yourself on compiling the the system then you won’t have to wait.
BUT… FYI… the following is being tested over @ Mangosproject at the moment so you won’t have to wait too much longer I’m sure.
MaNGOS Rev.5069 SD2 Rev.236 UDB Rev.335
Patch:
* Event Announcer
* AHB 5.6 (Fix 6)
* Guild Bank
* Patch common.h for 2.3.3
Client 2.3.2 & 2.3.3
Stable and running for 12 hours with 15-20 users.