crashuncle

Its sad to see this cause I really like the project, I tested it myself and can say that it work pretty good. Before I made already a Chatbot with the elder Client (In 2.3.3 times) and it was quite funny. I hope that the community continue on that project.

Looks interesting and useful, its easier to disable a part of the Scripts with that solution or simply to add custom scripts beside SD2. I personally think something like a "Script" folder would be useful, it should load ALL .dll files from this folder so we could make things like "InstanceScripts.dll, GossipScripts.dll..." to have it better sorted / easier to overwrite or disable a part / need to compile only a part of the Scripts to test something.

If you want 3.0.2 NOW then use a Patch like TOM_RUS or Rastizz did, it work fine so far without any problems. (12h uptime with 100 testers max.~) I think the primary priority currently is stuff like optimizing the Netcode, get a better Multithreading working etc. a very good playable 2.4.3 is better then a lagging / crashing 3.0.2.

It doesn't officially support it yet and this topics really begin to spam now. But what I can say is that it work with the correct patches quite fine with 3.0.2 (WoW/BC/Wotlk.B.). Northrend, Barber, Achievement System... work good. The Patches are quite "Hacky" anyway so I guess they will be only applied or re-written so it need less resources or has a better stability. The Databases are better in that part, a lot of Northrend is spawned and DK Startzone etc has already working Quests. I play on Wo[Censored]er.com , they use a Mangos as base for their Testserver. (Their .info is quite nice between even name all Devs etc.) and can say that really everything I tried worked fine. So yes Mangos work fine with 3.0.2 but its not offically supported here yet till it get re-written and applied to SVN to be sure everything work fine. We speak here of Pre-Wotlk, Wotlk itself will be supported here officially when it has been released.

Should be added to the SVN, a lot of VC2005 Mangos Newbies are not able to compile else. But normally only the ".\\g3dlite__$(PlatformName)_$(ConfigurationName)\\g3dlite.lib user32.lib" line should do the job.

Hello Mangos Community, I would like to help with Mangos debugging. I know how it works, but I would like to do it without a Server break. Normally you can do it only after it crashed and the message "Application crashed..." appear, click on debug give you what you need. At another Core project it was a bit easier, it created Crash Dumps which kinda did the same. But it collected them and the Server was able to restart instead of break. So is there a possibility to get this "Crash Dump" System in Mangos? It would be a lot easier then to debug with Visual Studio and find the line / thread which crash the Server. With best regards, CrashUncle <-The name say it...

You need to add that in a LevelX.cpp file and add the rest in the Chat.cpp / Chat.h files manually. But check it carefully "// In this realisation only caller can hear this sound." so I doubt it announce it to everyone.