[Prev][Next][Index][Thread]

# [slayer@kaiwan.com: Re: Modifying player properties based entering any command]

- Date: Thu, 20 Mar 1997 02:21:34 -0600
- From:

    ------- Start of forwarded message -------
    Return-Path: moo-cows-errors@parc.xerox.com
    X-Sender: slayer@pop.kaiwan.com
    X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
    Date: Wed, 19 Mar 1997 23:12:47 PST
    To: moo-cows@parc.xerox.com
    From: Brack <slayer@kaiwan.com>
    Subject: Re: Modifying player properties based entering any command
    In-Reply-To: <1.5.4.32.19691231190000.00671788@mailbox.syr.edu>
    Mime-Version: 1.0
    Content-Type: text/plain; charset="us-ascii"
    Sender: MOO-Cows-Errors@parc.xerox.com
    Precedence: bulk

    At 10:47 PM 3/19/97 PST, Kipp the Kidd wrote:
    >I don't think Henry was looking for this... he said anything a player types,
    >and players can't "type" binary.  The <CR> is really just enter, which makes
    >$do_command()'s argstr to "".  Also, this eliminates any chances of using
    >default parsing, if do_command wants to use it.  I can't imagine why you
    >would want this done on the main login port.
    >
    you could always parse out the command and then do your own parsing or
    force_input() back to the player (minding recursion of course). I did some
    weird stuff like that on a test moo just to see if I can capture backspace
    characters or respond to telnet "Are you there" requests... nothing
    seriously useful, however.
    ------- End of forwarded message -------

- Prev: [slayer@kaiwan.com: Re: Builtin]
- Next: [slayer@kaiwan.com: Re: Modiying player properties based entering any command]
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index