- Fork this site.
- Create a new post in the _submissions directory, based on example.md, and fill out the relevant fields.
- Push your changes up and open a pull request.
- If valid your module will be forked on AzerothCore organization, entering in our catalogue, and you will be set as repository admin.
Because we fork the repo to display it in our catalogue, we only accept modules released as open-source in GitHub.
- Name: name of your module.
- Author: username of the original author (in case it's forked into an organization).
- Repository: link to the GitHub repository.
- Download: link to download the sources as .zip (take it from GitHub).
- License: license used to release the code.
- AzerothCore hash/commit compliance: version (hash) of AzerothCore used to compile the module in testing stage.
- Includes configuration?: specify if your module uses a configuration file (mymodule.conf.dist), and if the file is copied automatically by CMake or manually by the user. CMake is recommended.
- Includes SQL patches?: specify if your module patches the databases. If yes, indicate which databases are affected and if the patches have to be applied manually by the user or are included in the
- CMake hooks used: indicate CMake hooks used, if any.
- Core hooks used: indicate any core hook used, identifying the script type. Example:
WorldScript: OnHookA, OnHookB, etc.
Give a complete description of what does the module and how it does it.
Optional / Recommended
- Add a
README.mdin the root folder with a complete description of your module. It will be shown in the details page of the catalogue.
- Add an
icon.pngin the root folder. It will be shown in the module list and details page of the catalogue.
- Use the
db_assemblerto include your SQL patches.
- Give the user the biggest amount of options for configuration possible. It reduces the need to modify the code because "something doesn't work as I would like to".
- Use the GNU Affero General Public License v3.0.