This topic is to list where are the problems and try to solve them. Though a huge work has been made by Alige, there is still a lot to do. and I'd like to help newcomers and veterans as well to find their way in wiki
This is the actual organization of the development part of the wiki . It can certainly be improved.
In this topic I would like to get:2.1 Development General information
You want to join the DEV team but don't know where to start? Well look at these pages to know on what you would like to focus on first. You might also want to talk with other devs on IRC. irc.themanaworld.org and the Developers' channel is #tmw-dev.
Joining the project
Reporting Bugs
Git repository
Testing Server
How to Develop
Scripting Basics
Projects and Teams
2.2 Game Content - Guidelines
Graphics: Art in Development - Animations - Particle engine - Image dyeing
Mapping: Tileset development - Map development - Mapping Tutorial
Sound and music: Sound effects - Music
Other: Translations - Game systems - Weapons
2.3 Programming Information
EA Related: eAthena Scripting Standards- Dependencies- Ports
Miscellanous: Bug tracker-Source code documentation (Doxygen)
RFCs: Rendering - Action layers - Collision system - Movement system - Logging
Reference: Server development - Realtime combat - Monster Database
Releases: Making a new release - How to release an update
- First of all the wiki guidelines should be approved (and improved?). Please have a look on Crush's proposal; comment them either in the comment paragraph or on discussion page.
http://wiki.themanaworld.org/index.php/Wiki_Guidelines - Suggestions about organization of development part of the wiki. (for example I think that this wiki should include something about the client(s) and their development, the website and it's development, the wiki itself, a Tools page)
- A list of articles which are outdated so we can categorize them and update them when necessary
- A list of the tools (both local and online that you find useful for your work and that you would recommend (pastebin, dropbox, trello, doodle, Gimp, tiled, IDEs, Rosegarden, MySQL...)
- A View as clear as possible of the medium and long term working method of the various teams: I found for example links to content on googlecode, gitorious and git hub, with a lot of redirects which make a synthetic view of the project somewhat difficult to acquire. There is no reference document to track the history of the project and the choices which were made and their reasons. (except a patchwork on forum)