Subject: generic guests

From: [email-masked]
Date: Mon, 14 Dec 1992 08:06:47 -0800

Forgive my ignorance, could someone please explain, how I get the generic
guest login to work, e.g. like on lambda with the coloured guests. I am using
a recent core.db from parcftp, and have just managed to get 1.7 working on
my 386 pc at home.
 Thanks in advance.

---

From: [email-masked]
Date: Mon, 14 Dec 1992 16:30:34 -0800

Your message dated: Mon, 14 Dec 92 08:06:47 PST
> a recent core.db from parcftp, and have just managed to get 1.7 working on

To make a guest, make a player, and then change its parent to $guest.
You must make one called "Guest" before you make all the colored ones.
I also chown the player object to me, (guests don't own themselves.)
(Is that a good idea?)

If you want to change the guest description, don't forget to
change the slot default_description, rather than just changing
the description.

While we're on the subject:
Can someone please tell me what the "responsible" slot does?
In the October release of the core, $guest.responsible
has a whole bunch of junk on it.

-- Amy

---

From: Pavel Curtis <[email-masked]>
Date: Mon, 14 Dec 1992 17:08:32 -0800

> Date:	Mon, 14 Dec 1992 16:30:34 -0800
> From:	[email-masked]
> 

This is the slot used by the @check and @paranoid commands for spoof-detection.
It contains the callers() lists for the last `n' calls to your :tell.  Sorry
about the grunge in the core.

	Pavel

---

From: Roger Crew <[email-masked]>
Date: Mon, 14 Dec 1992 18:12:54 -0800

>   To make a guest, make a player, and then change its parent to $guest.

Life might be slightly easier if you @create a child of $guest and
then @detoad it --- given the current popularity of @newt/@denewt,
this is probably one of the few real uses left for @detoad (*)
@detoad (really $wiz_utils:set_player) understood about $guest
children last I checked so the ownership issue should take care of
itself (as long as you haven't recycled $hacker ... if you have, lots
of things in LambdaCore will break).

>   I also chown the player object to me, (guests don't own themselves.)

The reason for guests not owning themselves is so that random
people can't login and do arbitrary things to your guest's properties.
--
Roger Crew
Internet:   [email-masked]
LambdaMOO:  Rog

(*) still remembers the days when @toad/@detoad were added as a
matter of completeness, not because anyone thought they would actually
get used.  sigh...

---

From: Judy Anderson <[email-masked]>
Date: Mon, 14 Dec 1992 21:20:00 -0800

Date: Mon, 14 Dec 1992 19:30 EST
    From:	[email-masked]

No.  Don't let your guests be owned by a wizard or they can get into any
room they want, @lock or no.  Better to have them owned by $hacker than
any person who owns real estate.