Reaper Mangos 5054 – Easy WoW Private Server for WoW 2.3.2 -Critical Update-

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!

Mighty Guild

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 :)

Comment?

Note: Comment may not appear right away.

432 comments on “Reaper Mangos 5054 – Easy WoW Private Server for WoW 2.3.2 -Critical Update-

  1. 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.

  2. 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.

  3. 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…

  4. 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

  5. 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

  6. 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!

  7. I have used it on the Test Server and it works great with 2.3.3. Here, I’ll leave it up to you guys! Release a version that will run 2.3.3 or wait for a compatible version.

    Post what you want!

  8. @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.

  9. 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!

  10. 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

  11. 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.

  12. 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.

  13. # 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.

  14. 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

  15. @ 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.

  16. This version only supports 2.3.2!

    Guys I would like to deeply appologize for no release these past few days. I think I am going to release a compatible version soon.

  17. #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.

  18. 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.