This version includes checkpoints tracking (mostly for Rounds/Team mode), the requested TMX info/recs support, other requested commands like /admin prev and /song, more polish, and the still inevitable bug fixes. One day I hope to do a release that doesn't contain further bug fixes. 
Here is the complete list from http://www.gamers.org/tmn/Features_093.html :- New features and other changes in the v0.93 release of ASECO/RASP:
* new checkpoints tracking support with the following features:- o all checkpoints and finishes are now tracked internally
o new /cps command to enable/disable displaying the checkpoint passages (since the TMx client has it built for TimeAttack mode, this is only useful in Rounds/Team modes)
o the first run on a track only stores all checkpoint passages (as long as the finish is reached)
o if /cps is enabled, subsequent runs will display a small pop-up window at each checkpoint for two seconds (just as long as the TMx client displays the checkpoint time), containing the time and the difference to the best run so far
o if a run has a better finish time, it's stored together with those checkpoints as the new best run
o the finish is also a checkpoint, but no pop-up is displayed there
o the checkpoints are only remembered for the duration of each track, not stored in the database
o a player's display setting is remembered until the next ASECO/RASP restart
- o new /tmxinfo command to display the TMX information on the current track or, when given a track ID (from /list) or a TMX ID, any other track; note that with a TMX ID, the UID field in the output remains empty
o new /tmxrecs command to display the TMX top-10 world records on the current track or, when given a track ID (from /list) or a TMX ID, any other track
o optionally show the TMX world record at the start of a new track (configurable via new config.xml setting <show_tmxrec>)
* new /song command (based on a new GBXDataFetcher class) to show the (file)name for the current track's song; no method is currently known to decode the title/artist from the song file
* new /admin prev (alias /admin previous) command to quickly revisit the previous track
* new /list option: /list oldest # displays the # oldest tracks added to the server (default: 10) to complement /list newest
* the /statsall output now includes the Wins/Losses (W/L) ratio
* the rounds reports now also work in Team mode
* finalized the optimization (in v0.92) of the jukeboxing & track switching process
* when a TMX /add or chat-based vote is cancelled by the server during the Tab scoreboard, that reset is also logged
* documented the dependencies of all plugins in their respective headers
Bug fixes in the v0.93 release of ASECO/RASP:
* when using jfreu.plugin.php (not jfreu.lite.php), if rank limiting is off then newly connected players are not properly entered into the internal players list – fixed
* at ASECO/RASP start-up, authentication errors are ignored (oops) – fixed
* if the same track is /add-ed or /admin add-ed multiple times, multiple files are created in the 'GameData/Tracks/Challenges/TMX/' or 'GameData/Tracks/Challenges/TMXtmp/' directories – fixed, duplicate files for identical tracks are prevented
* if a file already exists in the 'GameData/Tracks/Challenges/TMXtmp/' directory for a /add-ed track and that track is then /add-ed again, the file (with an incremented name) is stored in the 'GameData/Tracks/Challenges/TMX/' directory instead – fixed
* in the TMNDataFetcher, if the serverlogin for an online player starts with a non-alphanumeric character (e.g. '-') then the servernation isn't found – fixed
* if plugin.matchsave.php is not included in plugins.xml (which is the default), /admin match begin crashes the system – fixed, a warning is shown if the plugin is not included
* the administrator check for the 'chat_tc_listen' ability doesn't work – fixed - o all checkpoints and finishes are now tracked internally
- Important:
* In the zip file, all *.XML and config files are now located inside the newinstall/ directory. This means that you should be able to unzip the download and replace all the code files (unless you made changes to any) without worrying about overwriting your customized config files. However, for every XML/config file that was updated (see above), you must replace your version with the one from the newinstall/ directory, or compare them and add any new/changed configuration settings to your version to insure the system remains working correctly.
http://www.gamers.org/tmn/
Enjoy!
Xymph
