Jump to content

antz

Community Manager
  • Posts

    2808
  • Joined

  • Last visited

  • Days Won

    90
  • Donations

    0.00 GBP 

antz last won the day on April 13

antz had the most liked content!

4 Followers

About antz

Core Infomation

  • Core
    Zero
    One
    Two
    Three
    Four

Contact Methods

  • Discord
    Antz#2868
  • Website URL
    https://getmangos.eu/wiki

Profile Information

  • Gender
    Male

Recent Profile Visitors

9281 profile views

antz's Achievements

Advanced Member

Advanced Member (3/3)

142

Reputation

48

Community Answers

  1. @Conner Reid Can you provide the text of the error messages, perhaps a screenshot.
  2. @cbuntingde install the db updates in Character/updates/Rel22 Rel22_03_001_Adjust_Tables.sql Rel22_04_001_Add_Quest_Tracker_Table.sql
  3. antz

    Extracting Game Data

    DBC's can be used from anywhere, these are blizz directly exported files. Maps, vmaps and mmaps are marked with a version to allow to cores to identify the core they are loading. Also there may be changes in the formats also by other emulators. If fact, mangos implemented several precision improves to the extracted files several years back which as far as i'm aware have no been incorporated into their codebases. To ensure the fastest extraction build, always build in release rather than debug. I do not have a monster PC, but I was able to build the cores, extract all the files and load the databases for MangoZero, One, Two and Three in an afternoon.
  4. antz

    Extracting Game Data

    @BitWhiz I have done a lot of analysis into this and the answer is, for MangosZero and MangosOne it makes absolutely no difference. The are 2 Continents 0 and 1 (Eastern Kingdoms and Kalimdor) - These get one core each. The Emerald Dream map is the next biggest, it gets a core. (In TBC Outlands also gets this core) and still finishes before the first two. ALL the other maps get the remaining core and complete before any of the other three complete
  5. @Rochet2@Foereaper Is this something you are working on ?
  6. antz

    Installing OpenSSL

    Work is being done to mangos to make it compatible. This hasn't been applied to all the cores yet
  7. antz

    Installing MariaDB

    @BitWhiz I personally recommend MariaDB (Thrown mysql in the recycle bin). Version 10,x is fine
  8. antz

    Installing OpenSSL

    @BitWhiz NEVER USE 3.x.x !!! It does not work with mangos, even though mangos will compile and run. You will not be able to login.
  9. I'm not an expert with Unix, but check your memory and pagesize as this often causes this type of error
  10. Have you compiled the source from the latest github repository ? The version you are running is almost 2 years old.
  11. @liuyang2708 mysql libraries need to be installed rather than just the service to build mangos. But i'm going to assume you have done this. With this release of easybuild I added some bypass options. 1) On the main screen of Easybuild, click the D button 2) Click the MariaDB 32/64 installation you have (mysql is deprecated, but this will bypass it) 3) Click 'UPDATE' 4) The 'Build Options' Button should appear 5) If you get errors when attempting to build, then it's cmake can't find you mysql either.
  12. @tutengjun Can you attach a screenshot of your problem ?
  13. 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. MaNGOS (C++) Build System B1) When selecting only to build extraction tools, the build fails. B2) Modify the build system on Mangos Three & Four to match that of Mangos Zero-Two. B3) Apply updates from Mangos Zero-Two into Three/Four. Extraction Tools E1) Modify the Unified Extractors to support the changes in Mangos Three & Four. E2) 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 One, 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 latests 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. MangosSharp (C#) Core C1) Modify the extraction tools / Core to use the same .map files as main MaNGOS C2) Fix up the many current issues with this young core Database D1) Adapt the current databases to match the standard MaNGOS ones
  14. The last few years have been hard for MaNGOS. The pandemic hurt us all, but on top of that we've also had the following: Losing Necrovoice (our resident DB expert) was a huge lose - RL issues meant that he had to stand down until further notice. Losing our remaining two full time devs was a huge loss - Again RL issues meant they both had to stand down permently. I also had huge personal losses in 2022 which resulted in me having to step back from active duty for 6 months. I offered to officially step down but my two colleagues and fellow trustees of Mangos didn't want me to. So for 2023, where does this lead Mangos ? Here's what I know ! I'm just about back onboard, as is MadMax (the other trustee remains anonymous for now) We have no full time Mangos core devs We have no full time Mangos DB devs So the situation sounds grim, is mangos finished ? We are in better shape than after the massive hack / takedown attempt just under 10 years ago. Back then, we had no dev team, no admin team and had lost all the code repositories, In ten years we rebuilt and now have stronger cores than we ever did. Mangos is a community project and as such belongs to each and every one of you. Madmax and I are only the guardians who look after it and protect it, I love mangos and will do what I can to see it prevail. To that end, I ask anyone who can to contribute and help us make it better. Antz (Mangos guardian)
×
×
  • 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