Jump to content

antz

Community Manager
  • Posts

    2813
  • Joined

  • Last visited

  • Days Won

    94
  • Donations

    0.00 GBP 

Everything posted by antz

  1. The mangos localization project is a side project I started to help push the localization of mangos forward. All contributions and help are welcome and i'm happy to discuss the finer points of how to contribute with anything who's willing to listen
  2. iirc it is the ace type libraries which are used in the extractors.
  3. also, to put some perspective on this, will still want to keep compatibility with older systems and not introduce something like the boost bloatfest
  4. sadly mangos is a single threaded application, with the objectmgr passing out unique id's to all parts of the system. Having more than one doing that job will cause the server to come crashing down.
  5. since mariaDB is not currently supported, this is actually a low priority. It will get reviewed in time and when the build system fully supports mariaDB all the existing updates beyond the base db will need to be adjusted at well,
  6. This should be fixed in commit: https://github.com/mangoszero/server/commit/f3edc3c12579a51c3f37e4d40076833280aff6e8
  7. Changed Status to Completed Changed Assigned to antz Changed Implemented Version to 21.11
  8. Changed Status to Completed Changed Assigned to antz Changed Implemented Version to 21.11 Changed Milestone to 24 Changed Priority to New / Assign Priority
  9. Fix added in https://github.com/mangoszero/server/commit/fd0401ea0459417ba27d2052c28347df51a930ac Thank you
  10. Changed Status to Completed Changed Implemented Version to 21.11
  11. @Necrovoice - could you pr this for me ? Add "Thanks Caliginuex" to the commit title
  12. antz

    Setting up User Accounts

    open your favourite MySQL manager app, select the mangos database and run the following query: select * from command Alternatively, type .help from ingame or help from the mangos console
  13. @caligineux - Do you have GitHub userid ? so that we can credit you correctly. If you have the email address that goes with it, can you pm me with it ?
  14. antz

    Branches merged

    enum WardenCheckType { MEM_CHECK = 0xF3, // 243: byte moduleNameIndex + uint Offset + byte Len (check to ensure memory isn't modified) PAGE_CHECK_A = 0xB2, // 178: uint Seed + byte[20] SHA1 + uint Addr + byte Len (scans all pages for specified hash) PAGE_CHECK_B = 0xBF, // 191: uint Seed + byte[20] SHA1 + uint Addr + byte Len (scans only pages starts with MZ+PE headers for specified hash) MPQ_CHECK = 0x98, // 152: byte fileNameIndex (check to ensure MPQ file isn't modified) LUA_STR_CHECK = 0x8B, // 139: byte luaNameIndex (check to ensure LUA string isn't used) DRIVER_CHECK = 0x71, // 113: uint Seed + byte[20] SHA1 + byte driverNameIndex (check to ensure driver isn't loaded) TIMING_CHECK = 0x57, // 87: empty (check to ensure GetTickCount() isn't detoured) PROC_CHECK = 0x7E, // 126: uint Seed + byte[20] SHA1 + byte moluleNameIndex + byte procNameIndex + uint Offset + byte Len (check to ensure proc isn't detoured) MODULE_CHECK = 0xD9 // 217: uint Seed + byte[20] SHA1 (check to ensure module isn't injected) }; The code above is lifted from Warden.h - These are the types is checks that can be processed by Warden
  15. antz

    Branches merged

    Warden is a automated cheat checker which when enabled will check for any exploits being used on the client machine. - It's not perfect, but adds an additional level of security to the server.
  16. antz

    Branches merged

    We have had two branches: Release20 and develop21. develop21 was supposed to be a temporary dev branch, but has been in use for over a year. Well, as of today they are now merged as a single master branch !! I have updated Appveyor and Travis (our test tools) to point to the new branch.
  17. Our work towards the 2016 Roadmap didn't quite go to plan ! Instead the time was spent fixing up specific long term bugs and correcting missing / broken content. To that end, most of the main points of the 2016 roadmap are carried over to 2017
  18. Goals for 2017 For 2017 the following are what we would like to achieve: Release Version 21 for Zero, One and Two containing all the recent updates and fixes we have. Release Version 21 for Three and Four - which will involve a massive amount of work to get these cores up to date. Redo the server commands to make them a bit more standard and obvious. Break out AHBot into its own daemon process Develop a mangos update daemon, which allows the ability to apply DB content and minor updates automatically Create Editors for the other xxxdocs systems (we currently only have a dbDoc Editor) Normalise the character DB and remove data blob fields Continue to standardise the code across the cores where its appropriate to do so. Document where it differs and why. Move some hardcoded values from the core into the DB, possibly some enums as well. Implement Stormlib library for Zero, One and Two and remove mlib Apply the Unified Extractor to Three and Four (requires stormlib) Look at removing DBC usage from the Core and change the extraction process to include importing into a DB for use by the core. Including Multiple locale support. This would facilitate the removal of stormlib / mlib from the core and only be needed by the extraction tools. Finish implementing the database localisation and allow localised db content to be loaded and edited. Including a localisation editor to allow localised translations to be created/edited by users. Look at Adapting EAI to match SAI functionality. As well as some of the more obvious ones: Clear down reported bugs on the Project Tracker. Improve the World Database with updates and corrections. Improve the Wiki Documentation. Include some example Eluna scripts to assist those starting out learning to script with Eluna. Include some custom Eluna scripts to help showcase it's abilities. Finally, we would like to get into a twice yearly Release cycle of more major releases. MangosVB (Formerly Spurious) RoadMap for 2017 Add RealmDB from c++ Mangos and modifying MangosVB to be compatible with it. Work out how to get MangosVB to use the standard Mangos map format. Finishing warden functionality (so it can use/read signatures from DB) Merge all of the changes from Zero to One and Two Investigate into voice functionality for One / Two Doing spells.. implementing them like stealth and getting a proper DB script system in place Getting it compiled and running under unix (using mono)
  19. Something we initially overlooked was the Appveyor and Travis configurations - These are the automated test systems for the code !!! Although the files in the repos were modified to point to the new branch name there was something else that needed to be done. - In both Appveyor and Travis they needed to be told which branch to get their config settings from, so they also needed to be updated.
  20. I spent most of yesterday in hospital having a minor operation done, since i'm home and a little drowsy.... decided it's best if I don't touch anything important
  21. @Unkle Nuke has completed the merging of the various branches of Mangos Zero server and database repos and I'd like to express my gratitude for his work on that as it was not an easy task. You might want to re-clone your repos to ensure that you now have the latest changes !! He is now turning his attention to Mangos One and Two to perform his magic there too !!
  22. With Mangos Zero (and too a lesser degree Mangos One and Two) we have been developing on the develop21 branch, while the master branch has remained untouched. This was only supposed to be a short term thing and has ended up being continued for over 2 years. Part of the changes will be to merge the two branches into a single branch again (master) and we will only use another branch when adding special development tasks which require group input. @Unkle Nuke has volunteered to help make this happen as his knowledge of git is vastly superior to my own.
  23. It's been a long long time since we last did a full release of Mangos (any of the cores) and it's long overdue. This is a blog to explain what we're doing and why, plus should hopefully act as a guide for when we do this next time.
×
×
  • 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