crashuncle

Looks awesome, I think this will help a lot especially for test areas with 1000+ players.

What is the problem? Looks ok to me.

Any updates about this issue?

They released again a new method where you can even crash any Mangos server with, I guess the crash reports get flooded soon...

Perfect would be a normal Loglevel 1 log and a "limited "loglevel 3 log.

New method (With WPE) which is working fine appeared in the same thread!

You need to add in your terms of service that you are logging chats if there is a possible abuse blabla..., then its quite legal.

Yes and I really don't like this other thread "How to crash a Mangos server" I really hope that this forum disappear sometime.

Should work when I see the related code here, its really a critical bug in Mangos.

Emotions aren't a problem but all "normal" flying creatures are one in Mangos, at least in the 0.12 branch it doesn't works at all also with the correct DB flag.

Doesn't work as it should also with 0.12 branch even with the correct creature flag. I would really like to see which commit fixed it cause it looks strange when creatures jump in the sky.

I use since a while a similiar SQL configuration as nanounico does and I cant complain with the performance, you only need enough RAM. The only part which I don't really get is... Are you sure that it is a good idea?

Enough RAM and some alcohol in form of Vodka is the solution for all your problems. Seriously, we cant help you much if you don't define your problem more detailed and if you may post us your Server / SQL configurations and if needed any related logs. Such a machine can hold 1500+ players easily with the correct configuration and MT maps patch.

If there really exist a possibility for a new dupe exploit then it gets hopefully soon fixed.

I use a very old MTmaps ACE revision which got created by Scamp and cant complain, over 1000 with 2-3 days of uptime and no lag. So I guess ACE is better since others got problems with OpenMT. Well it would be helpful if you write down your experiences.

May post the logs here? It could have thousands of reasons.

Mangos even works fine on a P3 Dual Server (Well it cant hold much players but 50-100 are no problem depending on the settings). The problem here is not the hardware itself, its your bad knowledge about servers and Mangos itself. Your server can run Mangos fine and adding even more CPU cores will not help you at all, use the search function here and inform yourself first. I guess that you are using 64bit Linux cause Windows is really not acceptable at all together with Mangos, so configure your system first with tutorials like this one http://www.linux.org/lessons/beginner/index.html you may have a chance then to get in 1-2 months a stable server. Oh and it is not a good idea to talk about such topics here cause public servers are in some countries not completely legal, you should remove the root advertisement else you might get banned.

Sounds interesting, could you post or PM them please?

A kind of "Stable Revision" thread is really missing here, all other forums have such a thread and I even saw similar things on the Russian Mangos forum. I'm quite curios how the latest 0.12 (2.4.3) revisions are, and I didn't heard anything about that Reflective Shield issue yet. The old 2.4.3 revisions from Nov08 are at least very stable (3-4 day uptime, 1k online) but I cant tell you anything about the new ones.

Just make a new Mangos command (You find enough examples how to make one which access tables) and let players use it? That could be also used with client sided addons.

Sounds good, what kind of mtmaps system I saw several ones already.

That is for patch downloads only so clients can download official patches from the server. You cant use custom patches for it, at least not with the basic code because it checks the MD5 hash of the file. I see no possibility to check if the client has a specific MPQ, but there might be some hacky ways. I remember that I made a addon check years ago on the WoWEmu and it worked fine, you were able to stay online only when you had addon X else you get kicked.

I made a similiar version a while ago for 2.4.3 but removed the related code parts completly and added some features like Blizzlike chat colors. So its a pure chatlclient which is quite resource friendly (5MB RAM, 1MB Bin). Its sad that PseudoWoW has such a slow development because the idea itself is not that bad and the results look so far good.

I can confirm all points which got described by Leak, the memory usage is increasing with Vmaps after a few days uptime. For me it gets to 5GB after 2-3 days~ Also instances make problems like mixed up cooldowns and the gameobject bug existed already in WoWD. I like to call it "realistic resource bug"

That is very impressive on such a CPU, but I guess it wasn't very stable yet? I guess all "testers" connect of course per LAN since anything else wouldn't be allowed *cough*. I personally still use as basic a revision from November08 with Mtmaps and some crashfixes of newer revisions and get with 1000 "testers" around 4-5 days uptime till I mostly restart manually and there is no lag at all. If you don't want lags with the current hardware and Mangos revision then simply set a player limit and keep your database clean. Some members here really demand sometimes "Fix this crash now!" instead of solving it themselves and support the project that way and may even learn something new.