# Amiguous Matches

Graeme Smith (grysmith@freenet.edmonton.ab.ca)
Sun, 3 Mar 1996 07:30:07 PST

- Messages sorted by:[ date ][ thread ][ subject ][ author ]

    The problem, is simply that you are using the wrong approach...

    I am not sure if #0:do_command, is the correct path for that approach,
    but if not, you will have to parse, from inside the database. Use a verb
    on the room, or person, that will show up in the do_huh hierarchy instead
    of the server bf.

    				GREY

    GRAEME SMITH                         email: grysmith@freenet.edmonton.ab.ca
    2536 138A ave Edmonton

    On Sun, 3 Mar 1996, Matthew Hapke wrote:

    >   I am running a MOO in which a player may wind up in a room with several
    > objects with the same name, (ie a room full of swords or whatever)
    >
    >  I wanted to switch around do_huh, so that if an ambiguous match occurs, the
    > player can select the item from a list, or at the very least, will be
    > returned to the first item on the list.
    > Unfortunately, it appears that the parser already decides that it doesn't
    > know which verb you mean before it ever hits do_huh. Am I reading this
    > right? Is there any way to solve this dilemma?  I was using the standard
    > Lambda core, with the get verb on thing in my testing of this code.
    >
    >