On Sat, 15 Dec 2001, Rob Casko wrote:
> Soo....you could "get 1." to get the first thing off the ground...instead of
> needing the name.
You already can do this, although the order is somewhat, umm.. weird.
look 2.
A wand sparkles in the light.
-=]Sauron's Office[=- -=]Valhalla[=- -=]1210[=- Exits: NESWUD
look 3.
You see a black cloak.
-=]Sauron's Office[=- -=]Valhalla[=- -=]1210[=- Exits: NESWUD
look 20.
A large desk made of oak sits here.
-=]Sauron's Office[=- -=]Valhalla[=- -=]1210[=- Exits: NESWUD
The 2. and 3. - are objects I'm wearing - the 20. is an object in the
room.
The order it scans for objects, is:
1. Objects in ch->carrying
2. Room's extra description(s)
3. Objects in ch->in_room->contents
> Or..."look 3." to look at the third person in the room.... or "Murder 5." to
> kill the fifth thing in the room.
What happens if I do "drop 2." to drop the second object in my inventory..
The problem is what's the scope of your "dot" targetting at the time you
execute your command. A simple command like "get" - can have several
scopes.
get 2. -- get second object from ground
get 2. bag -- get second object from "bag"
The biggest problem is that the command parser that ROM implements, is not
smart enough to distinguish between these two, and so you don't know the
context in which you're calling do_get(), etc.
> What I would like...is just a DOT targetting...that would scan through items
> or players in the room(depending on the command) without actually having
> anything after the DOT.
See above.
--
Dominic J. Eidson
"Baruk Khazad! Khazad ai-menu!" - Gimli
-------------------------------------------------------------------------------
http://www.the-infinite.org/ http://www.the-infinite.org/~dominic/
