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) When selecting only to build extraction tools, the build fails.
B2) The additional files for the extraction tools are placed into the wrong folder (root rather than tools). Thanks Will Tuker
B3) Modify the build system on Mangos Three & Four to match that of Mangos Zero-Two.
B4) Apply updates from Mangos Zero-Two into Three/Four.
B5) The additional files for the extraction tools are placed into the wrong folder (they are also in tools).

Extraction Tools

E1) Modify the unified extractiors to use Stormlib rather than mlib (Mangos Zero, One and Two). Stormlib is already used on Mangos Three & Four.
E2) Modify the Unified Extractors to support the changes in Mangos Three & Four. (Related to B3).
E3) Modify Mangos Three / Four to use the unified extractors. (Related to B3).
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 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.
 

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.
 

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
 

For 2019 the following are what we would like to achieve:

• Release Version 22 for Zero, One, Two and Three containing all the recent updates and fixes we have.
• 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
• Normalise the character DB and remove data blob fields
• 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.
• Look at Adapting EAI to match SAI functionality. 

As well as some of the more obvious ones:

• Continue to standardise the code across the cores where its appropriate to do so. Document where it differs and why.
• 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. Once done, this will be linked via a git submodule
• 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.

Goals for 2014

• Continued alignment of the cores. Different teams did things slightly differently and as a result we have similar functions in different cores using different names. This need tidying up

• Documenting the core, other groups shy away from this work as they feel it is beneath them. We are an educational group, documenting the core we help others learn.

• Continue to look at new ways to improve mangos, both from a technical aspect as well as a functional one.

• Developing better code, remove hardcoded values. Sadly some of our older developers never believed things would never change and hardcoded a lot of values in various areas of the core. This makes extending quite complex in places.

• Some of the database has been designed badly (playerbytes anyone), we intend to review and enhance the database where we can to improve performance and readability.

• More improvement to the server files to make them consistent across the cores.

• Continue our commitment to the Eluna project and add LUA support across the cores.

• Lastly, helping to teach more people for the core and scripting libraries work.

We also recently asked our devs a question:

"If you wanted two things to put on the 'roadmap' for mangos for the coming year, what would they be ?"

• Look at streamlining the installation and upgrade process, in particular database upgrades
• Look at the concept of scripting things like spells, NPCs etc; there's no reason why a basic quest scripts should be a dozen lines long when the same thing could be done in a line or two in something like Lua or JavaScript.
• Have a clear view of what's working good, what needs work, what is broken ... also in terms of content (which instances work) that would be useful.
• Reorganise the project file system to all mangos branches and backport the Cryptography and Implemention as used in other projects. That way development can continue on Warden.
• We need some core cleanup perhaps, As in getting the core documented etc.

• DK rune system rewrite

• New virtual functions in scripts

• Full mingw support

• Creature_difficulty system rewrite.

• Dungeon finder

What follows is a quick summary of 2014, plus how we did against the Roadmap set out for the year.

MaNGOS had a difficult year with whole chunks of bugs being reported for the first time. While some of these bugs were new, a majority were bugs that have been there for years. Part of the reason they have only just started to be reported and Two-fold.

1) The Unified Tracker on the website has helped bring this issues to light easier, plus the ability to raise a log from a forum post.

2) With the massively improved Build System in Mangos Zero, people are able to build and use mangos with the minimum of hassle.

Having some of the Eluna team onboard also helped to get the Eluna implementation completed a lot smoother than we would have done otherwise.

How did we do on our Goals for 2014

• Continued alignment of the cores. Different teams did things slightly differently and as a result we have similar functions in different cores using different names. This need tidying up

The Rel20 branches have all received extensive syncronisation / cleanup and this work in ongoing. For example, a git diff between MangosZero and MangosOne before the sync came in at over 80mb, run a diff now and it's about 12mb. There is still work continueing, but it's work in the right direction.

• Documenting the core, other groups shy away from this work as they feel it is beneath them. We are an educational group, documenting the core we help others learn.

Again, this is ongoing. As our devs are working on different parts of the system and making changes, they are adding documentation. Also the DBDocs project has helped to document the database significantly better than any other Emu project, this too is ongoing. To this end, tools have been written to allow users to help update the information.

• Continue to look at new ways to improve mangos, both from a technical aspect as well as a functional one.

Rel20 introduced git submodules - where common code is shared among all projects. Eluna, Realmd, the Deps all benefitted from this change and applied Across Zero, One and Two and to a lesser degree Three.

The new SD3 project, which will replace the different SD2 modules in all the cores in Rel21 is a continuation of this work. SD3 is a single scripting library which is compatible with all the cores, rather than five slightly different libraries. This has been made possible thanks to the groundwork laid down by the Eluna team in their efforts to allow a single Eluna Library to work with all the cores.

• Developing better code, remove hardcoded values. historically developers never believed things would never change and hardcoded a lot of values in various areas of the core. This makes extending quite complex in places.

Sadly this is still outstanding, due to the amount of work syncing the cores up. This should happen soon

• Some of the database has been designed badly (playerbytes anyone), we intend to review and enhance the database where we can to improve performance and readability.

Some work has been done on how this can be achieved, nothing has been completed - but there are several changes that are currently WIP.

• More improvement to the server files to make them consistent across the cores.

Rel20 of Zero, One and Two offer a very consistant project structure and build process - This will continue

• Continue our commitment to the Eluna project and add LUA support across the cores.

As of Rel20, Eluna is now present in Zero, One and Two. Work is in progress to get it implemented in Three and Four

• Lastly, helping to teach more people for the core and scripting libraries work.

This year has seen an influx of new devs and sorely needed scriptors / db devs. The improvement of the information held in the Wiki, plus fixing any highlighted shortfalls has pushed this effort on a long way.

Things the devs wanted to improve:

The devs were asked:

"If you wanted two things to put on the 'roadmap' for mangos for the coming year, what would they be ?"

• Look at streamlining the installation and upgrade process, in particular database upgrades

Work has already been done on this, but it's not complete yet.

The numbering system has been simplifier significantly.

With the reorg of the project files, all DB updates are now in a single repo

To help with debugging, there is now an update history stored in the db_revision table.

• Look at the concept of scripting things like spells, NPCs etc; there's no reason why a basic quest scripts should be a dozen lines long when the same thing could be done in a line or two in something like Lua or JavaScript.

There is work ongoing with a redesign of the spell system.

• Have a clear view of what's working good, what needs work, what is broken ... also in terms of content (which instances work) that would be useful.

The Tracker has been a huge boost, plus using stats fed back from the cove servers have helped

• Reorganise the project file system to all mangos branches and backport the Cryptography and Implemention as used in other projects. That way development can continue on Warden.

A majority of the project files have been reorganised and synced up and the differing Realm projects merged to become a single project.

• We need some core cleanup perhaps, As in getting the core documented etc.

Work is ongoing on this, but a lot of progress has been made

• This has been done or is ongoing

DK rune system rewrite

New virtual functions in scripts

Full mingw support

Creature_difficulty system rewrite.

• Still outstanding

Dungeon finder

• Some work has already been done for this in Two.

As such we didn't have a formal roadmap in 2015 as it was a year of proper transition and rebuilding for MaNGOS.

Much of the project foundations have been rebuilt and redesigned to allow us to be able to move forward easier in the future.

I would like to make a special acknowledgement of the efforts of the following people who contributed massively over the last year:

• FoeReaper - Who worked tirelessly with me to get things cleaned up, especially on the cmake and build system side of things.
• Olion - Who helped reshape SD2 into SD2+, which became the foundation of SD3
• Chuck5ta - Who's constant eagerness to fix any DB data issues I uncovered, has been a great help

There have also been hundreds of other people who have also contributed in various amounts throughout the year and I would like to take the time to thank everyone who contributed  !! - MaNGOS is our project, it belongs to all of us

Some of the key changes made to the codebase to make it a little bit more coherent were:-

• Replacing the ageing SD2 libraries in each core with a single cross-core SD3 submodule
• Replacing the separate extraction tools on Zero, One and Two with a Unified Extractor submodule.
• Moving the RealmD code to a submodule

My push to get MaNGOS properly documented has started to pay off. Several sub-projects were created to help achieve this:

• dbDocs system for the Wiki has helped us create one of the most complete database documentation of any project.
• dbcDocs for documenting the DBC files is still a work in progress but has come on a long way this year
• packetDocs for documentation the packets and their structure is well into development
• codeDocs this is still in a prototype phase atm, but the idea behind it is to allow full API documentation of the codebase

These four projects use a semi-automatic system for creating the information. In principle the key information is pulled from the source material whether that be the database, dbc files or the mangos source code - This information is then mapped onto a documentation layer which allows anyone to add information and notes freely.

In the contrib folder of the mangos 'repos' is a tool called dbDocs Editor, this allows for documentation to be created and/or edited relating to the database.

For 2016 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.

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 2016

• 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

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

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)