Jump to content

H0zen

Senior getMaNGOS Developer
  • Posts

    114
  • Joined

  • Last visited

  • Days Won

    11
  • Donations

    0.00 GBP 

H0zen last won the day on October 5 2022

H0zen had the most liked content!

2 Followers

About H0zen

  • Birthday 10/27/1977

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

H0zen's Achievements

Advanced Member

Advanced Member (3/3)

23

Reputation

12

Community Answers

  1. Thank you for reporting this. The bug is confirmed and a fix will be applied very soon!
  2. Please go to Player.cpp file and change lines 1920-1926 into if (m_regenTimer != 0) return; Rebuild and send us the feedback
  3. Edit mangosd.conf and change the console log level to 0. For files change it to 1. Restart mangosd after editing.
  4. Sorry for the incovenience! Based on your report, we identified a nasty bug, which has been now fixed. Please update your sources with the latest version from https://github.com/mangostwo/server and rebuild. Thank you for your feedback!
  5. Your client does nothing because you didn't handle the connection step right. When the client is successfuly authenticated by the realm daemon, it is redirected to mangosd daemon and the first step, of course , is to establish a connection via TCP socket. When the connection is established, the server will send SMSG_AUTH_CHALLENGE packet. THIS IS THE FIRST PACKET YOU HAVE TO SEND AND IS MANDATORY!!! The client will respond to this packet with a CMSG_AUTH_SESSION packet, and this is where the miracle happens. The server has to handle this packet and has to create the so called session. If it succeeds, the server will send SMSG_AUTH_RESPONSE like yours. Because the intialization of Warden module is part of making the session, the server can send (but is not enforced to) various SMSG_WARDEN* packets, and this is what you already noticed. Hope this helps!
  6. All these issues comes from a wrong advice given in the mentioned install tutorial. All versions of MaNGOS have their own ACE integrated in the source code, so you don't need to mess with downloading and installing ACE separately. The guide says "Use External ACE libraries. Allows you to use the ACE libraries coming from your system. Untoggle this option only if you know what you are doing. " But this should read "Untoggle this option UNLESS you know what you're doing". So, the solution is to clear everything, and repeat the install and build process, BUT WITHOUT EXTERNAL ACE. You'll be amazed how smooth it'll compile and install.
  7. In mangosd.conf set LogFilter_AIAndMovegens = 1
  8. The issue is not in the extractors, it's in your Cata client, which is definitely not right. I strongly suggest you to find another one, avoiding in the future that source you mention in the link.
  9. Go to mangosd.conf file and change LogLevel = 3 to LogLevel = 0 (or 1). This will diminish the verbosity of logs in console.
  10. It is not a table, it is a file in the source code. I suppose you compiled mangos.
  11. Go to line 40 in file src/game/MotionGenerators/WaypointMovementGenerator.cpp and comment it, or you can reduce the log level in mangosd.conf
  12. If you build playerbot module, the ahbot will not work. The reason is playerbot module also contains a buggy ahbot submodule, which interferes with the actual ahbot. So the ideea is simple: if you want ahbot, disable playerbots from building.
  13. Please go to Player.cpp file and change lines 1920-1926 into if (m_regenTimer != 0) return; Rebuild and send us the feedback
  14. The issue is now fixed with commit https://github.com/mangoszero/server/commit/bcab12ecbc93920efc4cf78cf6a8318fb85b95a3
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use