Chapter 3. TODO Listing

These lists cover changes to these documents, the game data (graphics etc) as well as the engine of the game itself. See About The Developers to discover who handles each section. This section will be updated as changes are fed back to the documentation maintainers and so may be a little behind the bleeding edge. If you wish take responsibility for one of these items please see Joining The Project.

Game Engine TODO. Currently the game engine shall urgently updated to add the following features:

  1. Event queue (running in its own thread)

  2. Loading of models from perl and guile removal

  3. Mesh reduction, and sensible heuristics for deciding which mesh to draw.

  4. Perl event callbacks

  5. Models, according to the above spec, for a selection of spacecraft and a space station (and a planet possibly?).

  6. Converting lwo files with textures and labels to perl, and the associated rendering.

  7. Lasers, including working out where they`ve hit, and taking appropriate action (inflicting damage).

  8. AI for computer ships (by event handlers).

  9. Useful functions for perl AIs to call.

  10. Explosions, model destruction, particle spewing.

  11. Make sure it keeps working under Windows!

Some less important features which would be nice and shall be added as soon as possible:

  1. Targetting of other ships (there`s an interface issue here)

  2. Mouse control, including some GUI stuff (toolbar?)

  3. Docking

  4. Autopilot (this may be possible to accomplish with the same AI as the computer ships).

  5. Pretty background pictures (starfield, gas clouds, etc)

Documentation TODO. Much about this documentation remains incomplete. Below is a roadmap of forthcoming improvements.

  1. Restructure the documentation as a Docbook Set to provide:

    • Mote Quick Beginnings (antecedent of this document)

    • Mote design notes. Summarising the design related traffic on mote-dev and the findings from MoteCons. A format for papers (as Articles) that are to be inserted into this document must also be discussed. Part 1 is game and technical information, Part 2 contains graphics/gameplay information and Part 3 contains plot information.

    • Mote Technical Reference. A wrapper document containing information about finalised game mechanics. May remain empty for some time.

    • Mote Tool Manual. Uses the tools documentation simple wrappers to generate man pages (this should be possible).

    • Mote specialised entity set. This does not produce a document itself but provides generic elements for all the Mote documents including such things as the GPL and attribution boilerplate.

  2. Include the following existing documentation entities in these documents:

    • Program "man" pages (using docbook2man).

    • The section regarding controlling the ship.

    • The whitepapers, stories and other stuff derived from mote-dev/

    • The bug reporting form (currently renders poorly in anything but tex)

    • The problems checklist (test for plib/fnt.h is missing from configure and glutg3-dev,plib-dev is required whatever edwin says Also note that these pacakges are from woody)

    • The joining in section (no correct addresses or up-to-date web pages for Mote information so I left it out

  3. Create or modify the following documentation entities:

    • A reformatted dependencies table (has to be rendered landscape in print format).

    • A reformatted buglist.

    • Graphics for both print (eps) and online (png) inclusion as graphics conversion has not been entirely successful.

    • Using glide with Mote

    • Authoritative list of Mote resources (links, papers, people).

    • A better Joining In section with the correct mail addresses and a variety of contact means.

    • Alternate means of getting/running Mote EG tarball, cygwin...

    • Extensions to the DSSL HTML sheet to blend at least some portions of the document with the new Mote web page, including whizbang graphics.

    • Provide a better set of examples, including sample Bug Reports and so forth.

  4. The documentation rendering process must produce:

    • Print documentation with no typesetting errors

    • HTML documentation which validates against the HTML 3.2 DTD (my Docbook and stylesheets are old)

    • Unix man pages for the tools renderable with groff and friends.

    • A manifest suitable for inclusion in web pages.

    All documents should include versioning information and architecture specific data ensuring that documents for Win32, Linux/PPC and Linux/i386 can all be produced from the same SGML source tree. A consistent tabbing style of three spaces per nested tag (from para downwards at least) shall be adopted throughout the source code.

Game Data Todo.

  1. Modify the ship conversion tool to handle Lightwave textured objects and convert the data to Mote's own Perl format.

  2. More models, textures and other game entities.

  3. A design for the economics model (rational economic actors and a producer/consumer graph should work) and possibly a proof-of-concept too.

All, could you possibly give me some more content for this section

Miscellaneous TODO.

  1. The new look Mote website to be completed and uploaded to our various peices of hosting.

  2. The modifications (if any) required to Mote to allow Win32 execution under cygwin should be briefly documented and a suitable cygwin installation should be made available for Windows users.

Note To Reviewers: This is not based on the TODO file in the source directory as that is very out of date.