To-Do List



MAPZ Revision History

1.1 Beta 01/14/99
- Added NICE feature to lower priority of compile commands to be low.
- Added QUE, so that multiple maps can be awaiting compile.
- You get a message now as to whether or not you are in que if you blindly
  send a compile command (before you had to send status to see if it was free)
- Added overall system logging on everything...should be easy to see who's
  doing what, and where the problems are now (hard to read log though ;)
- Added a 'visonly' command so that you can skip the rad step if you are
  only interested in vis of your map.

NOTE: Not sure what to do if people have upper case textures when it should
  be lower cased (aka pak file), since win95 doesn't seem to care..hmmm.

1.0 Beta 12/24/98
Just all the basics, would compile, status, help and cancel...that's about it.
Nothing too fancy.

----------------------------------------------------------------------

MAPZ v1.2 TODO List:

 1) option to make kill message only allowed from user's original email address
   (I will make this optional, but i think you should be allowed to do it from
    anywhere - for those of us with lots of email accounts)

 2) mail storage in a file other than /var/spool/mail/user
   it seems to screw up the interecptor for some reason if there is mail there
   not sure about this one....needs more testing, but it was making the server
   not send back status, and also would not cancel compiles...wierd.

 3) test MIME base 64 encoding...not sure if this works or not.

 4) lower case the command line so MAPZ compile MyMaP 1 = MAPZ compile mymap 1
   (easily done, but i should force people to do it right ;)
 
 5) cancellation of que'd jobs, currently no way to do that through email, you 
    can only cancel them once they become active (a lot silly).

 6) sender can only have 1 map per email account option. (i don't agree with this
    policy, but i should put the option in for the host that might want it)
    (first come, first server IMHO)

 7) when a map is cancelled...send to the sender as well as the map starter
    (ought to be the same), but send the starter the email of the guy that
    cancelled it...incase it was malicious (same if they get code or map
    name wrong..alert the originator of the map)

 8) add quake1 map compiling <-- big step...should do this for sure..
    might have to generalize some things, but i think it's going to take
    specific functions for each type of map compile needed.  Should at least
    add one more to see if there are some functions you can share among games.

 9) look into adding any other game types (hexen, heretic, etc...)

10) modify the status command so that you only get the job your interested in, not
    everything related to the compile.

Once I have a added support for  quake1 compiling, and all the minor
things are in there, i'll release the source code.  Should be some time
before February (because school starts! hehe.)

Coding Suggestions, send to creep@nofadz.com or starless@nofadz.com