Marathon Engine-Improvement Priorities. Several of them represent separate tracks. Updated on July 2001; many of these goals have been achieved

1. • Do a CodeWarrior build using CWPro 4 or 5. CodeWarrior is the most commonly-used MacOS development environment, and a build in it ought to be in good working order there before moving on to anything else. Since some routines had been removed from the code, this will be a good time to write replacements. [DONE]
2. • Add Marathon Infinity support: [ALL DONE]
     • Jjaro textures.
     • Jjaro scenery objects.
     • VacBobs.
     • SMG.
     • SMG ammo.
     • SMG wielding by others.
     • SMG wielding by self.
     • SMG status display.
   • Fixes for some of the simpler engine bugs. [ALL DONE]
   • Lifting of some resource limits. [ALL DONE]
3. • Support for the DrawSprocket. [Failed to work properly; the Display Manager is a good substitute]
   • Support for the InputSprocket. [DONE]
   • Fixes for some tougher engine bugs, like the line-of-sight bug. [MOSTLY DONE]
4. • Simple TCP/IP client-server networking. (collect, distribute keystrokes; periodically distribute snapshots). [Very little worked on]
   • Beginnnings of OpenGL support (easier things to render; more difficult things have placeholders). [DONE]
   • Simple AI improvements. [Very little work done on monster AI]
5. • Adding chatroom features to networking.
   • Doing detailed entity-state management in networking. (possibly)
   • Reasonably complete OpenGL version of original game graphics.
   • Fancier AI, including bot AI
   • Communication with friendly NPC's.
   • Marathon 1 support.
6. • Doing much fancier graphics, such as
     • Substituted wall textures [DONE]
     • 3D-model inhabitants (scenery, characters) [work in progress]
     • 3D-model landscapes
   • Objects that one can walk on?
   • Vertical portals?
   • Revised versions of editors?
   • Third-person perspective?