[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tads3] Should items revealed on opening a container be "seen"?
- From: "Kevin Forchione" <kevin@xxxxxxxxxxx>
- Subject: Re: [Tads3] Should items revealed on opening a container be "seen"?
- Date: Thu, 4 Sep 2003 16:24:54 -0700
- To: <tads3@xxxxxxxxxxx>
----- Original Message -----
From: "Mike Roberts" <mjr_@hotmail.com>
To: <tads3@v-space.org>
Sent: Thursday, September 04, 2003 3:58 PM
Subject: Re: [Tads3] Should items revealed on opening a container be "seen"?
> "Eric Eve" <eric.eve@harris-manchester.oxford.ac.uk> wrote:
> >I've found that things are not marked as seen when they're discovered by
> >opening or looking in a container, which limits the usefulness of the
> >openWhenSeen and closeWhenSeen conditions.
> >
> >My quick-and-dirty (and not fully tested workaround) is to [modify
> >BaseThingContentsLister.showList and DescContentsLister.showList]
>
> This is akin to a problem that cropped up a while back with room
> descriptions involving unlisted objects (such as objects with special
> descriptions) - doing the marking in the lister didn't mark things that
> weren't listed. The solution we settled on was to move the marking into
the
> room's LOOK handler, so that displaying a room description explicitly
marks
> everything visible as having been seen. This can mark too many things as
> seen in some cases, in the sense that it marks everything that's visible
to
> the player *character*, even if some of those objects were never mentioned
> to the *player*. That seems the better side to err on, though.
>
> I think in this case it might be best to take a similar approach. I'm
> thinking that the EXAMINE, LOOK IN, and OPEN handlers should mark
everything
> visible within the object being examined as having been seen.
That sounds right to me.
--Kevin