-
Posts
2032 -
Joined
-
Last visited
-
Days Won
71 -
Donations
0.00 GBP
Content Type
Profiles
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Everything posted by madmax
-
Warden kicking users (Exceeded Response delay)
madmax commented on madmax's bug in Archived Reports (Zero)(Resolved issues)
Changed Status to Awaiting Feedback Changed Implemented Version to 21.14 (Master Branch) -
Warden kicking users (Exceeded Response delay)
madmax commented on madmax's bug in Archived Reports (Zero)(Resolved issues)
This should now be fixed in this commit - https://github.com/mangoszero/server/commit/9dc9059fd454721271b393b350453100aff4422e -
Mangos One Incompatible Maps extracted
madmax commented on Лазар Дилов's bug in Archived Reports (One)(Resolved issues)
Changed Status to Completed Changed Implemented Version to 21.14 (Master Branch) -
Mangos One Incompatible Maps extracted
madmax commented on Лазар Дилов's bug in Archived Reports (One)(Resolved issues)
This looks like it was isolated to M1, if anyone experiences further issues please make a new report. I shall be closing this one now. -
Mangos One Incompatible Maps extracted
madmax commented on Лазар Дилов's bug in Archived Reports (One)(Resolved issues)
Spoken with antz and made this commit for M1 - https://github.com/mangosone/server/commit/dc142047ab0160e6722b454a1ef70ef33a785c87 Antz will take care of any others that need looking at later -
Mangos One Incompatible Maps extracted
madmax commented on Лазар Дилов's bug in Archived Reports (One)(Resolved issues)
Raised to Project Critical status. Project Lead @antz has been notified. -
Mangos One Incompatible Maps extracted
madmax commented on Лазар Дилов's bug in Archived Reports (One)(Resolved issues)
Confirmed. Currently maps extracted with the current extractors do NOT work on the M1 core. -
This was implemented in commit - https://github.com/mangos/Extractor_projects/commit/cef30f04a3a13077c38309bd3c5354d38176f432#diff-ef242d2771efb833ad8f397f337f18c8 We now need to alter the .bat scripts to use --threads command. Change needs implemented in Three extractors.
-
Warden kicking users (Exceeded Response delay)
madmax commented on madmax's bug in Archived Reports (Zero)(Resolved issues)
Changed Assigned to antz, H0zen -
Some console messages from Warden are currently not appearing in any log under any log setting. The console messages should be included in a warden log? Or other as needed, depending on logging settings.
-
Warden kicking users (Exceeded Response delay)
madmax commented on madmax's bug in Archived Reports (Zero)(Resolved issues)
Changed Version to 21.14 (Master Branch) Changed Implemented Version to Unset Changed Priority to Urgent -
Changed Status to Completed Changed Implemented Version to 21.14 (Master Branch) Changed Milestone to 21
-
This has been completed. Please refer to the main issue linked in the opening post.
-
The migration to OpenSSL 1.1 is now complete!
-
This has been completed with the following commits: https://github.com/mangoszero/server/commit/3299820ab74454c76a94b85ee8e93fe16431b129 https://github.com/mangosone/server/commit/be0faa22940df359e5cedea9e9b88e949a520cb4 https://github.com/mangostwo/server/commit/6a77d349f3a5560e6e0c0bbfd15762476c978ab2 https://github.com/mangosthree/server/commit/0da2bf5e4671a09e0e07b9a911b5b3b820a08bd1
-
Changed Status to Completed Changed Version to 21.14 (Master Branch) Changed Implemented Version to 21.14 (Master Branch) Changed Milestone to 21
-
Issue will remain open for sometime to allow user feedback on if this is fixed or not.
-
Changed Status to Completed Changed Implemented Version to 21.15 Changed Milestone to 21
-
Bug issue moved to PlayerbotAI to reflect the nature of the bug.
-
This is now fixed with these commits: https://github.com/mangoszero/server/commit/94cacb25104e1b70b0f398e124c985db8209f614 https://github.com/mangosone/server/commit/453bfda549aa07b7c704ad625306daefe9815c7e https://github.com/mangostwo/server/commit/99e9928c72880a6abe331dbcbf218e7642c5a4d0 https://github.com/mangosthree/server/commit/8a43384c5077f36909a29e0cb3a862014274e896
-
Did you send antz a github handle so we can credit you? If you don't have one we can just link back to this report
-
Changed Status to Confirmed Changed Assigned to antz Changed Implemented Version to Unset Changed Milestone to 22 Changed Priority to Normal
-
other How to set up a Mangos 1.12.x server with hamachi?
madmax replied to DerpTDG's question in Archived Help and support
Hey, The prefix thing for this topic is for which Mangos Core you are using, Zero is classic, one is TBC and so on. Can you confirm in the Mangosd.conf you have the following set to either the hamachi IP or 0.0.0.0 (0.0.0.0 means bind all addresses). BindIP = "0.0.0.0" Don't touch the ones ending in "Info" those are the IPs the mangosd looks at for the various databases and have nothing to do with external connections. I would suggest disabling the windows firewall while you are testing this to make sure its not interfering. I may be able to assist you with this later over discord if im free. -
[Advisory] Upcoming Planned Migration to OpenSSL 1.1.x branch With the recent change by OpenSSL in their Release Strategy we are planning to migrate all cores over to OpenSSL 1.1.x branch by Dec 2019. The first step in this process will be raising the minimum allowed level of OpenSSL used with Mangos to 1.0.2, currently you can use any version from 1.0.x - We plan for this change to take place this year, perhaps even this summer. You can follow the development notes on the OpenSSL issue on the tracker and make comments on the upcoming changes EDIT: This was completed on 12th April 2018
-
OpenSSL's latest release strategy shows that the 1.0.2 branch will stop getting updates from Dec 2019. The Mangos team intends to switch to the 1.1.x branch of OpenSSL by Dec 2019 and no later. OpenSSL 1.1.x Tasks: Refactor necessary code to allow all Mangos cores to function with OpenSSL 1.1.x branch. Raise minimum OpenSSL level to 1.0.2
Contact Us
You can also email us at [email protected]
Privacy Policy | Terms & Conditions
This website is in no way associated with or endorsed by Blizzard Entertainment®