Re: Porting MOO objects

• Date: Tue, 28 Nov 1995 13:43:45 PST
• From:
  Boots <boots@crl.com>
• Cc: Madhu Rao <mrao@site.gmu.edu>, list moo-cow <moo-cows@parc.xerox.com>
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <Pine.SUN.3.91.951128152724.18388A-100000@lance>

I like @autoport a lot too.. couple things I found tho..

Although it will make an object for you on the MOO you want to port to, 
it will strip your quota.. heehee.. You may find yourself going from 
200000 to 1972  :)  (Course that was a good year...)   Best thing to do 
is to @create an object with the same parent of course.. and have it 
ready to receive the port..

@autoport <MOOaddy> <your char name on that MOO> <your password on that 
MOO> #<of the object/verb you want to port> object=#<object/verb that will 
receive the port> timeout=<amount of time you think you will need to 
port, such as 300 or 400 or whatever>

Sometimes for some reason, I've found that it will bulk at the port.. 
mebbe 1 out of 5 times. I send the command again and it goes thru.  
Anyone know why?

Boots
PS Applause and confetti to the creator of @autoport tho :)

• Re: Porting MOO objects
• From: <batman@epix.net>

• Re: Porting MOO objects
• From: david@castle.net

• Prev: Re: Porting MOO objects
• Next: Re: Porting MOO objects
• Index: MOO-cows
• Thread: MOO-cows