[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tads3] Should items revealed on opening a container be "seen"?
- From: "Eric Eve" <eric.eve@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [Tads3] Should items revealed on opening a container be "seen"?
- Date: Sat, 6 Sep 2003 19:41:59 +0100
- To: "Tads3" <tads3@xxxxxxxxxxx>
Mike Roberts wrote [in response to my point about being things not being
marked as seen is response to LOOK IN etc.]:
> 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.
Yes, I think it was I who raised it; for some reason I overlooked the LOOK
IN/OPEN case at the time and only recently seem to have come back to
discovering that it might be a problem.
> 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 agree; though Jesse's suggestion seems to cope with the erring.
> 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 should do the trick.
> Jesse Welton <jwelton@pacific.mps.ohio-state.edu> wrote:
>> 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.
> That's a great idea - I'll add that.
Excellent.
-- Eric