How to Use a Generic Recorder

With this simple device you can record and play back conversations in the MOO. These conversations will be saved and even emailed for later review.

@examine Obvious Verbs

start/stop Recorder
set Recorder to <anything>
play <anything> on Recorder
setdelay Recorder to <anything>
p*ut/in*sert/d*rop <anything> in Recorder
re*move/ta*ke/g*et <anything> from Recorder
@lock_for_open Recorder with <anything>
@unlock_for_open Recorder
@opacity Recorder is <anything>

open Recorder
close Recorder
g*et/t*ake Recorder
d*rop/th*row Recorder
gi*ve/ha*nd Recorder to v*iew Recorder dis*play Recorder connect Recorder to @webpref*erences Recorder

Instructions and Information on Specific Verbs (Commands)

Using the Encore Object Editor

From within the enCore Object Editor (whether as you create the Recorder or as you seek to edit it), you can describe the Recorder. From the Xpress window as you *look* at the recorder, you will be able to see the contents of past recorder transcripts (they show as separate notes). 


Using Specific Verb Commands

start <recorder>
This command starts the recorder. A note on which to record will be created for you automatically. You will be prompted to give this transcript note a name; just type in a name for your log and the recorder will start. It is wise to create a name for this log that will help you remember what the conversation is about. For example, you might type: Library Workshop 8/21/01
You will then see:

>> Loading log Library Workshop 8/21/01. Done. <<
>> A red light on the jill's recorder flashes to indicate that it has been turned on and is now recording everything that is being said in The Library<<

stop <recorder>
This command stops both the recorder and the player if they are on. It also prompts you for log retrieval.

When you've finished recording by using the stop <recorder> command, you will be asked if you want the log for the MOO session emailed to you. You will see:

Would you like me to send the log 'Library Workshop 8/21/01' to your registered email address? [Enter `yes' or `no'] Enter yes and the log will be emailed to you.

You will then see:

Mailing Math discussion 9/21/00 to youremail@univ.edu.
... 5 lines ...
>> Library Workshop 8/21/01 moved to jill's recorder <<
>> The red light on Library's recorder goes out. The recorder in The Library has been turned off. <<

Now the Recorder is no longer making a log of the room's conversation.

play <log#> on recorder
Using this command you can play any log in your player. In this way, the recorder will "replay" a previous MOO conversation. LOOK at the recorder to see is contents. If, for example, you wish to play note number two, type: play 2 on recorder"

setdelay <recorder> to <#seconds>
You can set the playback speed with this command when you are going to use the play command. Example: setdelay <recorder> to 3

set <recorder> to private/public
This command is used to control usage of the recording device. When you create a new recorder it is set to public usage by default which means that anyone can operate it. You can restrict its usage to the owner and wizards only by setting it to private. Example: set <recorder> to private and set <recorder> to public.


Viewing, Sharing, and Recycling Transcripts

Once you stop the recorder, it saves the MOO discussion that was recorded on a note. Various ways exist for viewing the note and letting others know how to view this discussion. For instance, you are part of a group that meets regularly. Those that could not attend the moo session can still view what was discussed by accessing the MOO transcript.

Viewing the Transcript (three ways)

  1. Within the MOO: Click on the Recorder icon, and the different MOO logs saved inside that Recorder will show as separate notes inside the Recorder. Simply, click on the link of the note you wish to view, and it will open the MOO transcript in the viewing, Xpress side of the screen.

  2. Via the WorldWideWeb: You can open the MOO transcript as a separate page via the web by knowing the log's object number. To find the object number of the log, simply type @examine <logname> or look <logname> . You should see the number of the transcript object in the text window. To then view this log via the web, add this object number to the URL of the MOO. For example, if your log were numbered as object #563, and the URL for the MOO were http://lingua.utdallas.edu:7000, then you would type in this web address: http://lingua/utdallas.edu:7000/563

  3. Via Email: If you had the transcript emailed to you, you should be able to look for this email message and open it.

Sharing the Transcript with Others

You can, of course, leave the MOO log as a note inside the Recorder (that is, don't do anything) and others can access the log via the web as is described above. However, these logs take up a lot of memory. The character who creates the transcript (the person who starts and stops the recorder) is the owner of the transcript. Since each MOO user has a limited quota of memory space in the MOO, it is generally a good idea to copy the MOO log and archive it in another way for sharing with others (such as copying the log onto another web page). Then, it is recommended that you destroy (or recycle) that MOO log note to conserve the amount of memory left in your quota. Once you recycle the log, though, it is no longer available inside the MOO.

Recycling the Transcript

As just mentioned above, if you were the person who started and stopped the Recorder for the log, then you own it and it counts as a portion of your memory quota. Since it is wise to conserve your quota, it is recommended that you archive the MOO logs outside of the MOO and then delete the MOO log inside of the MOO. To recycle your MOO log:

Find out the object number for the MOO log you want to recycle by typing @examine <logname> or look <logname>

Then type @recycle <object#>

If the MOO log were object number #467, then you would type @recycle #467

You could also use the Xpress Editor (click the EDIT button), look at the list of your objects, and recycle the object from there. Either way is good.

Object Help Index