Re: connected_seconds() fails for not-yet-connected folks

• Date: Mon, 10 Jun 1996 17:13:58 PDT
• From:
  Kipp the Kidd <mcmudge@mailbox.syr.edu>
• Content-Type: text/plain; charset="us-ascii"

At 01:56 PM 6/10/96 PDT, Seth I. Rich wrote:
>I'm using an unmodified LambdaMOO-1.8.0p5, and I'm examining a not-yet-
>connected fellow, say #-20, who shows up in `connected_players(1)' and
>whose idle time I may see with `idle_seconds(#-20)', but I get E_INVARG
>when I try to view `connected_seconds(#-20)'.  This isn't right, right?

Okay, to rephrase your message:
You're looking at an unconnected player, and you check their
connected_seconds().  Why does it return E_INVARG?  They're not connected!
Connected_seconds() starts when they get the '*** Connected ***' message.
Because of this, on a lagged MOO, people may have a higher idle time than
connection time.

- Kipp
http://radioactivo.com.mx/~paradigm

• Prev: Re: connected_seconds() fails for not-yet-connected folks
• Next: Re: connected_seconds() fails for not-yet-connected folks
• Index: MOO-cows
• Thread: MOO-cows