The Mana World Forums

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)

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

Nard wrote: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.

Jenalya wrote:https://gitorious.org/tmw-eathena/mainline This is the repository with the server sources.

1. First steps inside TMW
   • History, awards, external references; TMW and manasource. Main forks (?)
   • Customize your client, play with data
   • script Basics
   • Graphics Basics (where to find graphics, customize)
   • Sound Basics (where to find music and sounds, customize)
   • How to?/FAQ (selected content from forum?)
2. The TMW project:
   • Project state (Yearly reports?)
   • Team(s?)
   • The GHP
   1. TMW eAthena (include global working information)
      • Content (each page includes actual working information, state of the art, actual plans)
      • client (s?) (where to find binaries complilation information)
      • server
   2. Manaserv (idem)
      • content
      • client (s?)
      • Server
   3. Bugs and issues tracking
      1. TMW eAthena test server
      2. Bugreporting
   4. Game concepts (all pages concerning concepts and story, approved or not, rather tricky to sort )
   5. Graphics Design
      1. player and mob sets, items (equipment), Other items, NPCs),guidelines and conventions
      2. Maps and mapping, guidelines and conventions
   6. Music and sound
   7. The website
      1. website (git...)
      2. Wiki guidelines, development, conventions ...
      3. Forum
3. Tools reference and reference tools:
   1. Git (working with git)
   2. Tiled
   3. Eathena script
   4. lua
   5. IDEs
   6. Interactive web tools Pastebin, team editors, filesharing...
   7. Graphic tools: GIMP....
   8. Sound and Music tools; Rosegarden, Audacity, Ardour, lilypond...

tux9th wrote:I'm not sure if that many wiki pages having a very similar content are necessary. Because it is hard to maintain every of these pages.

tux9th wrote:I think it is going to be confusing if we put the maps which are reserved in there.
For starters we now have to edit two pages to reserve a mapname and second some of these projects won't be realized in the next time.
I would rather keep the list clean to what's released on the mainserver and keep the rest to the Teams and Project site.

eg. Barbarian Village is on hold. One map is nearly finished but the tileset isn't. If no tileset artist picks that up and finishes it, it will never be released.

greets

1. What is a map: Client side, Server side... any information that could fit here to help understanding how it works (globally).
2. existing and planned maps
3. How to Map: includes guidelines , Map naming conventions, references to special pages on Mapping Tutorial page and/or Tiled

Crush wrote:Nard, when you want things to happen on the wiki, don't suggest. Just do and ask for feedback afterwards.