Jump to content

antz

Community Manager
  • Posts

    2808
  • Joined

  • Last visited

  • Days Won

    90
  • Donations

    0.00 GBP 

Everything posted by antz

  1. hi @SoundAxis, We don't use the github issue trackers as having over 30 github repos, it becomes impossible to keep track of issues across the cores. - Especially since several modules are shared between cores as well. We have a separate Project Tracker which encompasses all the features we need: Mangos Project Tracker In addition, we also have our development roadmap: Development Roadmap 2021
  2. Going forward, I personally advise switching to MariaDB. Some of the changes made by Oracle on MySQL have made what should be an easy install process into a nightmare.
  3. I'm assuming you are using MySql 8.0 - This was untested at the time of that patch release.
  4. @DaveJ61 - the updates you need have been zipped up. They can be found in: World/Updates/Rel21/Rel20_to_BaseRel21_Updates/Rel20_to_BaseRel21_Updates.7z - Don't run all of them, just 21_02_003 onwards
  5. Generally TBC is fairly complete, if you take a look at the project tracker on the site you will be able to see the outstanding issues for MangosOne
  6. Hi, I'm not a native German speaker so i will try and help as much as I can. Firstly I would recommend MariaDB rather than mySQL - A much easy install and fully compatible Also ensure you have installed OpenSSL on you pc I believe that error message is the result of a missing openSSL installations Antz ----== Google Translate ==---- Hallo, Ich bin kein deutscher Muttersprachler, also werde ich versuchen, so viel wie möglich zu helfen. Erstens würde ich MariaDB anstelle von mySQL empfehlen - eine sehr einfache Installation und voll kompatibel Stellen Sie außerdem sicher, dass Sie OpenSSL auf Ihrem PC installiert haben Ich glaube, dass die Fehlermeldung das Ergebnis einer fehlenden openSSL-Installation ist Antz
  7. Hi Lizardman, As Olion mentioned above, we don't support repacks. Using lights hope as an example..... Lights Hope is based on the Nostralius core.... which itself is based on a 6 year old version of mangos. Since we don't have access to the source or what changes have been made in the 7+ years since... We can't tell you much about it, only what we know currently from mangos
  8. We are aware there is an issue with the Linux extraction, we're working on it
  9. In previous years we had a roadmap of changes we wanted to implement. However, we are a small team and it seemed silly to specify a set of things to do on a time scale. If you think you can help us do any of these, please contact @antz or @madmax and we can discuss things in more detail. Build System B1) Modify the build system on Mangos Three & Four to match that of Mangos Zero-Two. B2) Apply updates from Mangos Zero-Two into Three/Four. B3) The additional files for the extraction tools are placed into the wrong folder (they are also in tools). Thanks jordigil. Extraction Tools E1) Modify the unified extractors to use Stormlib rather than mlib (Mangos Zero, One and Two). Stormlib is already used on Mangos Three & Four. - Thanks Warkdev E2) Modify the Unified Extractors to support the changes in Mangos Three & Four. (Related to B1). E3) Modify Mangos Three / Four to use the unified extractors. (Related to B1). E4) Add functionality to load DBC data into a database (along with the core code to read from Database rather than DBC files) and change the extraction process to include importing into a DB for use by the core. Including Multiple locale support. Database changes D1) Apply changes to standardise the Databases across the cores. D2) Merge all the different xxx_loot_template tables into a single table with a Loot Type Field (along with the core changes to support this). D3) Extract the character table data field (all the character stat data) into a table containing the required named fields. Including Item_Instance. D4) Modify the EventAI Database (and Core) to support the TC style handling (SAI). D5) Complete the Command Help localisation for Mangos Two, Three and Four. D6) Complete the Achievement localisation for Mangos Two, Three and Four. D7) Move some hardcoded values from the core into the DB, possibly some enums as well. D8) Change defaults in DB table in order to fit latest MYSQL standards. D9) Add support for Broadcast_text table and move all text tables to use that. Core C1) Standardise the naming of functions across the cores. C2) Implement standard account handling across the cores (Mangos Zero is the odd one out with reduced functionality). C3) Implement Playerbot functionality to Mangos One and above. C4) Add Cinematic Manager to the cores - Based on the work of TC/Cmangos. C5) Redo the server commands to make them a bit more standard and obvious. C6) Break out AHBot into its own daemon process. C7) Develop a mangos update daemon, which allows the ability to apply DB content and minor updates automatically. C8) Apply useful updates from other cores into Mangos cores. Other R1) Reorganise the core into a 'mangos core' set of files functions which are shared by all the cores and a module for each core which contains the code just for that core.
  10. According to your logs, the files should be in: C:/Mangos_Files/serverTwo_install
  11. Would you mind running easybuild again and when it's finished, click on the 'copy log to clipboard' and attach it to this post. - ending it up with no files indicates a failed build
  12. Sorry in my delay in getting back to you, but I wanted to be sure. I built the server from a fresh clone of the repo and built the server and the extractors, I then used the extractors to extract the data. My created file matched yours, so the extractors are correct. I then compiled the server and set it up and ran it, it loaded without issues. - This implies that the mangos you are using is not the latest version
  13. I have looked into the file you sent me.... It has a version flag of s1.5 - which matches the current version of MangosOne. Can you confirm that you built the mangosOne server from https://github.com/mangosone/server ?
  14. good, thats ruled out the extractors at least Could you upload your 0004331.map file, so I can examine it?
  15. very strange... Can I ask you to run map-extractor again and screen capture the 'banner' at the start: It should say ' for MaNGOSOne' in the top banner and 'Detected client build: 8606' as in the screenshot above
  16. The wow.exe file MUST be present in the top level wow folder when extracting. The extractors use this file to work out which client data to extract and from which client files to get them from.
  17. Sadly we don't have the source code for the clients - only Blizzard do. Therefore we are restricted by the Wow clients abilities.
  18. @Tobi Rodriguez Sorry I am a bit late to the party here.... Can you explain where you are at and what you issues are ?
  19. Although since i've been furloughed for most of 2020, i've been a lot more active on Discord
  20. I'm not aware of any more information being available... but if it's found then please let me know, i would love to add it to the articles
  21. No Questions are stupid... We were all beginners once !!
×
×
  • 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