Tryphen

Repo is a little out of date with mangos...generated patch file needs a patch to accomodate the new mangos source...replace the lines in the patch file that read: Player* pReceiver = receiver.GetPlayer(); // can be NULL + if (receiver.GetPlayerGuid() == auctionbot.GetAHBObjectGuid()) + { + if (sender.GetMailMessageType() == MAIL_AUCTION && !m_items.empty()) + deleteIncludedItems(true); + + return; + } + if (pReceiver) prepareItems(pReceiver); // generate mail template items with the following lines: Player* pReceiver = receiver.GetPlayer(); // can be NULL bool has_items = !m_items.empty(); + if (receiver.GetPlayerGuid() == auctionbot.GetAHBObjectGuid()) + { + if (sender.GetMailMessageType() == MAIL_AUCTION && has_items) + deleteIncludedItems(true); + + return; + } + // generate mail template items for online player, for offline player items will generated at open if (pReceiver) { if (prepareItems(pReceiver)) has_items = true; } Just want to throw a big THANK YOU out to the devs for a great addon!

First, please forgive the x-post as I initially posted this in Windows Server Setup yesterday but it was suggested it be posted here. I just wanted to return a little something to the community as I have got so much from it. I was curious how Blizz set up its 'Breaking News' dialog at the login screen...well I won't bother you with the details but can tell you that if you want your clients to see your 'Breaking News' then all they have to do is make the following entry in the hosts file (by default in the <WINDOWS>\\system32\\drivers\\etc directory): 1.2.3.4 launcher.worldofwarcraft.com where 1.2.3.4 is the IP address of your server. Yes, unfortunately since what you are doing is redirecting the message request to your server, you have to use an IP and not a name, therefore if your IP changes you will have to instruct your users to update the file (I just provide a download of a hosts file on my webpage along side the realmlist.wtf sample) A default hosts file looks like this: # Copyright © 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost so you just have to add the line to the end like this: # Copyright © 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 1.2.3.4 launcher.worldofwarcraft.com Lastly, you create a file on the root of you HTTP server called 'alert'. A sample of mine is as follows: <snip> SERVERALERT: May 3rd, 2010 21:05 MST Levelling up my hunter...w8n for some company. Staff At MyWoWServer </snip> NOTE that the first line must be as shown above: SERVERALERT: as the blizz parser looks for this. I searched through the forum for this information and couldn't find it. When I get some time I may add this funtionality to my DotNet app that can be downloaded to manage realmlists (similar to WoW FE) so that it can be enabled/disabled programmatically.

Thanks mate, will do.

I just wanted to return a little something to the community as I have got so much from it. I was curious how Blizz set up its 'Breaking News' dialog at the login screen...well I won't bother you with the details but can tell you that if you want your clients to see your 'Breaking News' then all they have to do is make the following entry in the hosts file (by default in the <WINDOWS>\\system32\\drivers\\etc directory): 1.2.3.4 launcher.worldofwarcraft.com where 1.2.3.4 is the IP address of your server. Yes, unfortunately since what you are doing is redirecting the message request to your server, you have to use an IP and not a name, therefore if your IP changes you will have to instruct your users to update the file (I just provide a download of a hosts file on my webpage along side the realmlist.wtf sample) A default hosts file looks like this: # Copyright © 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost so you just have to add the line to the end like this: # Copyright © 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 1.2.3.4 launcher.worldofwarcraft.com Lastly, you create a file on the root of you HTTP server called 'alert'. A sample of mine is as follows: <snip> SERVERALERT: May 3rd, 2010 21:05 MST Levelling up my hunter...w8n for some company. Staff At MyWoWServer </snip> NOTE that the first line must be as shown above: SERVERALERT: as the blizz parser looks for this. I searched through the forum for this information and couldn't find it. When I get some time I may add this funtionality to my DotNet app that can be downloaded to manage realmlists (similar to WoW FE) so that it can be enabled/disabled programmatically.

Heya mates. I'm 'freshening' my 3.1.3 server and wanted to add the PlayerBot into the mix...I currently run Mangos with AHBot (gigelf version). When I try to git the mangos master, ahbot master, and playerbot master I get a couple of merge errors: $ git pull git://github.com/Gigelf/mangos.git auctionhouse remote: Counting objects: 100, done. remote: Compressing objects: 100% (43/43), done. remote: Total 65 (delta 51), reused 28 (delta 22) Unpacking objects: 100% (65/65), done. From git://github.com/Gigelf/mangos * branch auctionhouse -> FETCH_HEAD Auto-merging src/game/Chat.cpp Auto-merging src/game/Chat.h Auto-merging src/game/Level3.cpp Auto-merging src/game/Mail.cpp Auto-merging src/game/Makefile.am Auto-merging src/game/World.cpp Auto-merging src/mangosd/mangosd.conf.dist.in CONFLICT (content): Merge conflict in src/mangosd/mangosd.conf.dist.in Auto-merging win/VC80/game.vcproj Auto-merging win/VC90/game.vcproj Automatic merge failed; fix conflicts and then commit the result. The above was from merging the master mangos, then playerbot and finally AHBot...I get similar errors if I do mangos then ahbot, then playerbot. After attempting a compile, the AuctionHouseBot cpp file squacks about minimailloadindb not found for player (something similar as I killed the compile window and am going off memory). 1) Is playerbot compatible with gigelf AHBot or should I use the *new* ahbot by narc? The conflict looks trivial as I'm sure I could file compare the files for differences (just config files) and make the appropriate edits, but I just want to make sure that this conflict isn't indicative of something I am doing wrong. 2) Is the narc version as stable as the old gigelf version? Thanks in advance for any help you can provide. Best Regards, T.

MaNGOS/0.14.0-DEV (* * Revision 8052 - When logging in the pet starts with 100 Focus as it attacks it does not generate Focus. - If relog of course pet will start again with 100 Focus - If dismiss pet and summon it gets 100 Focus again. Things that I have noticed: - My pet was stuck at 10 Focus after its first mob attack. The next mob I pulled and put my pet on Stay. I hit it once with a Viper Sting and then it hit my Frozen Trap. I then set the pet to attack and it started to regen it's Focus at the regular rate. Sadly this was not repeatable and is just described here hoping to be some hint. After a handful of more mobs where it appeared to be working, it again ended up flaking out and holding at 15 Focus (just b/c my autocast fired in a different order resulting in the total used Focus being 85 rather than 90). - Once after a dimiss/summon Focus regen'd correctly for about 10 mobs then got 'stuck' again. 10,000 foot view shows that Focus regen does work in the core, but the trigger(s) associated with it may be the problem. Best Regards, T.

Well I just upgraded our server from 3.0.9 to 3.1.3 and would like to thank the devs of Mangos, UDB, ScriptDev2, and Acid for all your hard work - the upgrade went pretty smooth. The above libeay32.dll issue once again raised it's ugly head, but this time there is no workaround. It still appears as though the dist does not include a VC8 build for the dll (only VC9) and so cannot be used with a VC8 build of Mangos. Transplanting my previous 3.0.3 (used in 3.0.9 as well) caused the realmd console to bark out an error stating that the openssl version is too old and must be updated. This left me one of 3 choices: 1) Don't host a server anymore - ya, I thought this was ridiculous as well 2) Install 2008 express - I like keeping a lean/clean build machine have have 2005 Standard installed and so did not want to install the free 2008 express just for this build 3) Build myself a VC8 version of the dll using the current tar from www.openssl.org - this is the way I chose as I can still keep my VC8 dev env and still update by rebuilding the libeay32.dll as needed. I hope this isn't against the rules of conduct, but if anyone would like me to make a copy of that available by ftp, please let me know. Best regards to all and thanks to the community for all it's hard work. T.

Deleted as post already existed.

Digging in to this further it appears as though the libeay32.dll that is in the current git get was built using VC9.0 (breaking VC8.0 builds). The current release in GIT: Version: 0.9.8.10/0.9.8j Modified: April 13, 2009, 3:12:48 PM Size: 988 KB (1,011,712 bytes) If I transplant the libeay32.dll from my old working 3.0.3 version, I no longer have the error...it's details are: Version: 0.9.8.5/0.9.8e Modified: January 25, 2009, 2:57:30 PM Size: 0.98 MB (1,032,192 bytes) I couldn't pull up a revision list at http://openssl.org to see what has changed/been fixed and I am hoping that a build of libeay32.dll will be included for us VS2005/VC8.0 users and the mangosdVC80.sln be updated to use this version. Best regards, T.

If so, did you have an issue with a reference to VC9 in the VC8 solution and if this was the case where was it? Best Regards, T.

Aight, so I cleaned/rebuilt a debug build and compilation succeeded without issue. Activating the mangosd project and running the debugger, the Output Windows Shows 'mangosd.exe': Loaded 'E:\\mangos_src\\bin\\win32_debug\\mangosd.exe', Symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\ntdll.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\kernel32.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\ws2_32.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\advapi32.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\rpcrt4.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\secur32.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\msvcrt.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\ws2help.dll', No symbols loaded. 'mangosd.exe': Loaded 'E:\\mangos_src\\bin\\win32_debug\\dbghelp.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\WinSxS\\x86_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_5490cd9f\\msvcr80d.dll', Symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\user32.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\gdi32.dll', No symbols loaded. 'mangosd.exe': Loaded 'E:\\mangos_src\\bin\\win32_debug\\ACEd.dll', Symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\mswsock.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\netapi32.dll', No symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\WinSxS\\x86_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_5490cd9f\\msvcp80d.dll', Symbols loaded. 'mangosd.exe': Loaded 'C:\\WINDOWS\\system32\\wsock32.dll', No symbols loaded. 'mangosd.exe': Loaded 'E:\\mangos_src\\bin\\win32_debug\\libmySQL.dll', No symbols loaded. 'mangosd.exe': Loaded 'E:\\mangos_src\\bin\\win32_debug\\libeay32.dll', No symbols loaded. LDR: LdrpWalkImportDescriptor() failed to probe e:\\mangos_src\\bin\\win32_debug\\LIBEAY32.dll for its manifest, ntstatus 0xc0150002 Debugger:: An unhandled non-continuable exception was thrown during process load The program '[3840] mangosd.exe: Native' has exited with code -1072365566 (0xc0150002). Digging into the LIBEAY32.dll's manifest, event viewer shows that Dependent Assembly Microsoft.VC90.DebugCRT could not be found and Last Error was The referenced assembly is not installed on your system. I quickly looked through the manifests for the various modules that were built and could not see where VC90.DebugCRT was referenced and this would be a problem as I should only be referencing VC8-built libraries/dlls (as it appears from the install instructions above that VC80 is still supported). Admittedly, my strengths are in C/C++ and I am just teaching myself the DotNet side, so I am a little weak in manifest management and so appeal to the communitify for support in this matter..as I suspect anyone trying to compile under VC8/2005 will experience the same difficulty. Best Regards, T. ***EDIT: I have confimed this is the same issue when running a release build with the exception being the reference to the non-debug version: Event Type: Error Event Source: SideBySide Event Category: None Event ID: 32 Date: 02/04/2009 Time: 1:04:05 PM User: N/A Computer: WXPP-P3000 Description: Dependent Assembly Microsoft.VC90.CRT could not be found and Last Error was The referenced assembly is not installed on your system. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

That's a big negatory. Have been running 3.0.3 and now trying to compile/run 3.0.9 on the same machine - XP Pro SP3. Nothing on my build machine/server has changed in regards to either user software (what I installed) or even Windows software (Windows updates, etc). I have tried getting the files from the repo multiple times now with same result. If there are no suggestions, I will try debugging/stepping through the code to see what it doesn't like and post back what I find. Cheers.

Good day mates. I have/had a running 3.0.3 server that I wanted to upgrade to 3.0.9. 3.0.3 did not require the Microsoft Platform SDK for Windows Server 2003 R2 and I am just wondering what in the code's requirements (header files/libs) requires this as I can still compile under VS2005 w/o the SDK without any compilation errors. However when I try to run realmd and mangosd I get "The application failed to initialize properly" error. I will install the SDK next and follow the above instructions but they only reason I can see it compiling fine but throwing an exception at runtime would be if older libs were being used that the SDK updates. Any thought before I install the SDK and try a rebuild? Cheers mates. *** EDIT Ok, I rebuilt with the SDK and I get the same error - crash for both realmd and mangosd right out of the gate. This is using the master branch from git as suggest above. Any ideas? Best Regards, T.