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.
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).
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.
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.
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.
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.