No, it seems I don't have that installed... Additionally, I'm not seeing
the obvious exits anymore.. Maybe I just thought I saw them earlier.
I've been switching out look programs. Where can I get ObvExits, and
how do I register it?

Zobeid Zarathustra wrote:
>
> On Jul 4, 2006, at 2:04 AM, Kelketek Titikilik Rritaa wrote:
>
> > Mountains(#216RJ) Owner: Keketal_Kotaru Parent: Room Zero(#0R)
> > Type: ROOM Flags: JUMP_OK
> > DESC: You are in a forested mountain area. Up ahead, you can see
> > evidence of a village. Lower down is more mountains. A good distance
> > into the west, you can see a river. The mountain air here is
> > pleasently
> > cool, and the smells of trees please your senses.
> > Key: *UNLOCKED*
> > Chown_OK Key: *UNLOCKED*
> > Container Key: *UNLOCKED*
> > Force Key: *UNLOCKED*
> > Success: @$ObvExits
>
> Do you have a $ObvExits program installed on your MUCK? If you
> don't, I can see this @succ message causing a problem. ZoLook tries
> to match it to an executable MUF, doesn't find one, so it produces
> the error message instead.
>
> > dir /_/:
> > str /_showactions?:yes
> > 2 properties listed.
>
> The properties we are interested in can be found in the "_"
> directory. Thus:
>
> ex here=_/**
>
> You should find one "/_/sc:@$ObvExits" that is causing the trouble.
>
> > Also, I should note that it doesn't give you that error when you
> > enter a
> > room, just when you look at it after having entered.
>
> That's. . . odd. Maybe it's using the internal LOOK command when you
> enter a room. Probably you don't have your global LOOK action named
> with all the possible abbreviations, including the one the MUCK uses
> to trigger a LOOK when somebody enters a room. The name of the
> action in room #0 should be "look;loo;lo;l;lookat".
>
> It would appear that ProtoMUCK's in-built LOOK command simply ignores
> MUF calls it can't match, rather than producing an error message.
>
> -- Zobeid
>
>