If you want to help us, this is where you can find information on how to help us.

The easiest ways to help us:

• Play the game !
• And then report a bug if you find one !
• Tell us your wishes, your ideas, your suggestions (in the forum, there is a section for this)
• You may translate some parts of FTS in your language.
• You may create new, original maps. (Later)
• If you’re a programmer, you may either look into our mantis bug tracker and solve a bug or implement a feature. Or just get in touch with us in the dev's forum.
• If you’re a good programmer, you might even begin to develop one of the following tools we really need:
  • Create a map editor.
  • Write export scripts for our model format for your preferred modeling program.
  • Create any other tool you might think one needs.

Here is what we have to do for the redesign (reorganization) of the website. Write the name in front of a part if you want to work on it. There are already two tasks assigned, as an example.

• Dev’s page
  • Link to the developer’s edge of the forum.
  • Link to our dokuwiki.
  • Link to a help-us page with a link to the bugtracker.
  • Link to a credits page.
• Gamepage, big things
  • Use the forum as a blog-writing engine.
  • pompei2: Publish the latest blog entries on the gamepage.
  • mooshie: Make a forum design that integrates with the game.
  • Gallery:
    • pompei2: Come up with a design to allow translating it.
    • pompei2: Integrate an admin interface to easily manage the galleries.
    • pompei2: Add a BBCode to the forum that allows it to insert a gallery (using PiroBox) in a forum post.
    • pompei2: Use this to show screenshots and design arts.
  • Try to integrate dokuwiki to the gamepage for the library and the FAQ sections.
  • pompei2: Write a short overview of the webpage sourcecode so we can give it to a web developer when we have one.
• Gamepage, details
  • mooshie: Fix the skin of the logout button.
  • pompei2: Remove the debug code in the database code.
  • mooshie: Make the system-message have a prettier green background, and a red one for error messages.
  • pompei2&mooshie: Add an orange system-message (mooshie) that stays at the top forever to use for important messages like server downtime for example (pompei2).
  • mooshie: animate the light blue part at the bottom of the logo using a gif file.
  • Make the currently useless buttons like “tournaments” and “league” grey and disabled.
  • Make the logo always be a link to the homepage.
  • mooshie: Create a - (dash) ' (Apostrophe) and numbers 0-9 in the title font. Maybe release the psd file so that one can easily add new languages?
  • mooshie: Create the buttons in other languages. See the table below.
  • mooshie: Create the member area buttons in other languages. See the table below. → NO THAI TILL NOW !
  • mooshie: Clean-up the css files of the gamepage
  • pompei2: Make the “Detailed Introduction” link show somewhere in the (integrated) wiki.
• Integration of components:
  • Make the forum use our users-table for login (note to me: I saw one can write a plugin for this in the sourcecode!)
  • Make the dokuwiki use our users-table for login
  • Make the mantis bugtracker use our users-table for login
  • Make the ideatorrent use our users-table for login
• pompei2: List of additional links to put in the community category
  • Idea torrent.
  • Links
    • Developer’s page
    • pompei2’s blog
    • credits
    • donate
    • help us
    • Sourceforge
• Secure the whole thing

Note: I know Déconnexion and ออก จาก ระบบ are quite long and hard to get into the button, if you can’t get it, I might try to think of shorter words.

Here, we enumerate the various places (classes, files, domains, ...) in the sourcecode that we don’t like at all, are absolutely not proud of, but that just work and we don’t want to waste our time rewriting right now. One could call them legacy code:

• The local accounts stuff. Is this needed anyways? Yes probably for the campaign progress but only that. I mean we have different users (and their folders) in the operating system already!
• The parser utility and conf file reading/writing stuff. Should be replaced by python/lua files as soon as we got that in.
• The server2 code. This server needs a complete rewrite. Will probably be made using ZeroC Ice. Got a start on my notebook already.