new feature: replays
Posted: Sat Jun 13, 2009 11:25 am
The replay feature suggested by Caled has been implemented.
To begin with, you can now record a replay e.g. of a fight, PK-duel etc. and replay it later. This feature is intended to help improve your trigger and timer combat system, but you can also use it to record your glorious victories, of course.
Second, replays can be shared. The replay will display the text with the same timings as it arrived in the original recording.
If you share your trigger, timer & script system also, other users will be able to see the replay and all of the trigger/timer/script actions without the need to have an account on the particular MUD in question. This can be used nicely to debug Mudlet itself if there happen to be problems with some systems. People can now post a replay together with their own system and say exactly what doesn't work and everybody will be able to reproduce the issues.
How does it work?
1. Check the "log to raw stream" option preferences (this option isn't currently saved, so you'll have to reset it every time you restart Mudlet).
2. Start the recording with the usual "log" button on the right side of the command line.
3. Stop the recording with the same button and take a note of the file name ignoring the path component. The file name contains the date and time when the recording began. You can change the file name to something more appropriate, of course.
4. To load the replay make an alias with the pattern "^loadReplay (.*)" and the script "loadRawFile( matches[2] );" Then e. g. type "loadReplay 12-06-2009#19-21-09.dat" to start the replay.
5. location of the replay files: mudlet home dir/<profile_name>/log on my Debian machine this is e. g. "~/.config/mudlet/profiles/avalon/log" on windows it depends on your exact local version of windows. Look for the folder ".config" in your user document directory.
To begin with, you can now record a replay e.g. of a fight, PK-duel etc. and replay it later. This feature is intended to help improve your trigger and timer combat system, but you can also use it to record your glorious victories, of course.
Second, replays can be shared. The replay will display the text with the same timings as it arrived in the original recording.
If you share your trigger, timer & script system also, other users will be able to see the replay and all of the trigger/timer/script actions without the need to have an account on the particular MUD in question. This can be used nicely to debug Mudlet itself if there happen to be problems with some systems. People can now post a replay together with their own system and say exactly what doesn't work and everybody will be able to reproduce the issues.
How does it work?
1. Check the "log to raw stream" option preferences (this option isn't currently saved, so you'll have to reset it every time you restart Mudlet).
2. Start the recording with the usual "log" button on the right side of the command line.
3. Stop the recording with the same button and take a note of the file name ignoring the path component. The file name contains the date and time when the recording began. You can change the file name to something more appropriate, of course.
4. To load the replay make an alias with the pattern "^loadReplay (.*)" and the script "loadRawFile( matches[2] );" Then e. g. type "loadReplay 12-06-2009#19-21-09.dat" to start the replay.
5. location of the replay files: mudlet home dir/<profile_name>/log on my Debian machine this is e. g. "~/.config/mudlet/profiles/avalon/log" on windows it depends on your exact local version of windows. Look for the folder ".config" in your user document directory.