[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tads3] Should items revealed on opening a container be "seen"?
- From: Jesse Welton <jwelton@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [Tads3] Should items revealed on opening a container be "seen"?
- Date: Fri, 5 Sep 2003 12:45:38 -0400 (EDT)
- To: tads3@xxxxxxxxxxx
Mike Roberts wrote:
>
> 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.
If you haven't done so already, you might add a check in this handler
to suppress marking objects as seen if they have suppressAutoSeen = true,
or something like that. That makes it pretty trivial to correct the
problem in that minority of cases where an object should not be marked.
> 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.
This will hopefully share common code with the LOOK handler for rooms.
A markContentsSeen method, or somesuch?
-Jesse