OSY Discussion Forum

Well I started to work on my monthly refresh of the content DB and the software only to find that things are in a state of transition right now. Apparently the MaNGoS team is changing a lot of internal DB structures and breaking all sorts of addons including ones I depend upon such as the AHBot. So until at least AHBot settles into the new groove there won't be any updates to the server core and consequently the content database (or until I decide to make some heavy mods to the AHBot patch to get it to apply and to work now without segfaulting).

The biggest problem with this is that the creator/maintainer of AHBot is MIA. I guess he grew tired of WoW and MaNGoS and found something better to do. Can't say I blame him. I've been having a worse and worse time of getting AHBot patches to apply against updated MaNGoS source trees over the last three months. I've managed to play the role of "patch jockey" and come out with something workable in the end everytime thus far though. But unless AHBot is rolled into MaNGoS core or a new maintainer steps up, this situation is only going to get worse. And I don't consider running the server without AHBot to be a viable option. That feature is absolutely required to play WoW in a single player mindset.

Ironically I run the server but very rarely play on it. Luckily other than updating the core software and content db everything else is automated. So it requires no real work from me to keep running.

I have a separate copy of WoW that I can keep at any version I want, so no biggie.

Though I too haven't been playing very much either, of any WoW.

Well I manhandled the patch and integrated mods by some other posters and as of right now I have an updated MaNGoS server running. It appears to be stable. But my testing has been minimal.

Please keep in mind that MaNGoS doesn't support any client greater than 3.3.2 yet - so 3.3.3 and 3.3.3a are not going to work. Which is fine by me because now I don't have to regen all the maps and vmaps data

Molarix has been updated for client 3.3.3a as MaNGoS released an update for it two days ago. It was a rough upgrade - but all seems well now

Hmmmm... I finally got around to updating Molarix to the current builds of everything this morning. 3.3.3a is still the required client version, but the MaNGoS devs say they are working on 3.3.5 support. A bunch of stuff saw major updates today. I'm at work so I can't actually test it with a client, but everything appears to have loaded and be running correctly.

3.3.5a is now the current supported client version.

I found out today that when I redid a lot of my ManGOS stuff last week, I neglected to set up my service dependencies correctly so when I rebooted after updates a few days later, ManGOS did not restart correctly. The issue has been resolved today and while everything is back online, a lot of the backend ManGOS processes are cleaning up data that didn't get updated over the last week such as expired auctions and what not, so it'll probably be about an hour before the server is actually available for use.

So I've been keeping up with the monthly updates (not that anybody cares) and all is well. The current client version is still 3.5.1. I think 4.0 was where Blizzard essentially drew a line in the sand when it came to private servers. They've set the community back years in terms of content and in terms of the technical measures they are employing to break compatibility in every point release in the 4.x.x series.

Anyway - I just got a nice external SATA RAID 5 array that I moved all of the ManGoS databases and resources too. Everything on the private server runs so much better now that it is just amazing. I've had some fun playing for the last few days. Still trying to break into level 60 with my BE Pally. Oh well