MOO-Cows

moo-cows Topic: do_login_command questions

Article #1092
Subject: do_login_command questions
Author: Mark O'Neil
Posted: 3/20/2001 12:12:32 PM

What gets run after the following message is displayed?

*** Connected ***
enCore Starting Point
You see nothing special.
You see News and Box of Educational Tools here.
Last connected Tue Mar 20 11:49:03 2001 EST from
berry89-dhcp-6.dartmouth.edu
ATTENTION:  There are new news items to read!  Type 'news' for a summary.
#$#mcp version: 2.1 to: 2.1

I am trying to track down a non-destructive, but annoying, (because I don't
see where it is coming from) response of "I don't understand that" at the
end as in the following:

*** Connected ***
enCore Starting Point
You see nothing special.
You see News and Box of Educational Tools here.
Last connected Tue Mar 20 11:52:19 2001 EST from
berry89-dhcp-6.dartmouth.edu
ATTENTION:  There are new news items to read!  Type 'news' for a summary.
#$#mcp version: 2.1 to: 2.1
I don't understand that.

Am I correct in that the server goes through the #0:do_login_command/#10:co
sequence twice for a CO (?).

I could understand this in the event of a no-password but why when both are
provided?

Perhaps the wrong questions all together....

My scenarios are thus:

A co request comes in; if it gets authenticated then I log them in done and
fine except for the "I don't understand that." msg.

When I do a std co name password, everything is fine no message... Perhaps
something is not getting set in the first that I am missing?

Oh and those negative incoming player ids (#-743). do those keep
accumulating (the #-743 is from my server) or should the be decrementing on
connection?

Thanks!
-m


Responses:

Article #1094
Subject: Re: do_login_command questions
Author: Robert Sanderson
Posted: 3/20/2001 12:39:42 PM

> ATTENTION:  There are new news items to read!  Type 'news' for a summary.
> #$#mcp version: 2.1 to: 2.1
> I don't understand that.

Check in player:confunc and room:confunc

> Oh and those negative incoming player ids (#-743). do those keep
> accumulating (the #-743 is from my server) or should the be decrementing on
> connection?

They just keep on growing.
Especially bad if you run a webserver out of the game as well.

Mar 20 12:52:34: DISCONNECTED: #-9112 on port 8000 from (hostname)

Rob

--
      ,'/:.          Rob Sanderson (azaroth@nospam)
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Room 218, French Dept, Liverpool University, ext 2752
,'---/::::::::::.    Syrinnia:  telnet:  syrinnia.o-r-g.org 7777
____/:::::::::::::.                WWW:  http://syrinnia.o-r-g.org:8000/
I L L U M I N A T I


Article #1093
Subject: Re: do_login_command questions
Author: Chris Jones
Posted: 3/20/2001 12:44:04 PM

On Tue, 20 Mar 2001, Mark O'Neil wrote:
> I am trying to track down a non-destructive, but annoying, (because I don't
> see where it is coming from) response of "I don't understand that" at the
> end as in the following:

        Does encore have @paranoid?  You might wish to try enabling
@paranoid, then tracing where the text's coming from ("@check-full", I
believe).

> Am I correct in that the server goes through the #0:do_login_command/#10:co
> sequence twice for a CO (?).

        It goes through #0:dlc at least twice (once to show the login
screen, once to handle the "co <player> <password>" input) per login.
#10:co should get called once.

> Oh and those negative incoming player ids (#-743). do those keep
> accumulating (the #-743 is from my server) or should the be decrementing on
> connection?

        They keep accumulating.  Each connection gets its own unique
negative object.



MOO-Cows Home