Auntie Mangos

Anyone else seeing this? I have tried on a few test accounts with no display error.

Oh, I did not notice this. Will make further changes to clean this up.

*nods*

http://github.com/mangos/mangos s what you are looking for. The master branch is for 3.3.5a, the 0.12 branch is for 2.4.3. BTW: It is SITE FEEDBACK. Closed.

It's all in the first post on page 1. Grab the mangos version from faramir118's github repository, then compile and use the new tools included. Most of the new ones depend on a working CMake installation. $ git clone git://github.com/faramir118/mangos.git In contrib/mmap/ you will find the extractor needed. As usual, normal maps and vmaps still need to be extracted. Do that first, then mmap extraction. Browse the last two or three pages of this thread for current mmaps extraction instructions. Remember please, this is in development. You should try this only if you intend to submit feedback or code.

Nice one *stamps*

Any help is welcome, currently the sheep is mind controlled to do such things :lol:

We're not using Photoshop. We use Inkscape, since all images created are vector based

Shouldn't be many hickups. Database updates already is done, forum fixes coming in next. No downtime though. This was only a few minutes.

Probably because ACE is available on Ubuntu sudo apt-get install libace-dev

And right on getmangos.eu is a working link. This is not the place where UDB forums get fixed. mangos and UDB are not maintained by the same people.

This is all about issues with this website, not with our software. Scripts and especially custom scripts should be discussed at ScriptDev2. You got your scripts library there, then any issues are best discussed there.

It is pretty simple: those who want to play, and not know how stuff works, and make stuff work, should go and pay a subscription at Blizzard anyway. This is not the place for players, it's the place for those seeking knowledge!

We're on the safe side of things. Thank you! (And the others, too!)

May I recommend Git Ready? You will find all things git, and especially newbie friendly guides for the various git commands there.

This forum is not for mangos zero. As you may have noticed, mangos currently covers client version 2.4 and client version 3.3. mangos zero is an independent project, which is why its' github home is different. Activity does not mean this is the place to be. Move over to mangos zero, please.

Last time: client 4.0.1 is no no no.

This way, please.

You will not need any special backup tool. If you did not know, MySQL comes with batteries included. mysqldump lets you backup full databases, selected tables, and more. Try a tutorial or simply google for mysqldump. If you prefer to do this from PHP, try this article. BTW: googling mysql backup would get you all these and thousands more.

No. 4.0.x is unsupported. *sigh*

Can somebody please, please wipe my tears away before I drown?

The problem is not giving out a date for a release. The real problem is: whatever we do, and where we write it does not matter because people will not read what we write and always return to asking "Is it already out?". We have had this with every client release requiring longer time to upgrade, and I doubt it will change. Look above... it just required to read 3 posts above to find out that we have no ETA, and this already was too much effort asked by us... I bet, even if I change the site and add a huge coloured, blinking line above every page that reads "There is no client 4.0.x support available yet." you will still see no topics opening, asking for a date, or asking why not, even if we answer it multiple times. This has been the scheme of things since 2005, and why should it change suddenly? Sorry, if this sounds unfriendly, it is not my intention. Just wanted to describe how these things work out usually.

The 10 player limit is merely a historic thing. It was changed to only 5 players per dungeon in patch 1.10, and the limit still exists. It's mentioned in some patch 1.x notes.

It's not like we'd all die without it

I do have a fix in my git repository, but I have to make sure it works. Want to avoid issues with the switch of the tracking system. Sorry if it took a bit longer.