Sensing/detecting objects and forgetting

[backwardsEric]

If @ triggers an object sensing effect and detects nothing at a location, should that be enough to scrub the memory of something being at that location?

Should an object detection effect be treated the same in that regard or differently?

From what I see in effect_handler_SENSE_OBJECTS and effect_handler_DETECT_OBJECTS, both skip over locations where there's nothing. So they don't update @'s memory if that did have something there. I can see a certain logic behind that: "the absence of evidence is not evidence of absence.".

[Sky]

wut?

if you detect and there's nothing to be detected in that area, then, there's nothing in that area. you can't fail a detect, nor can object appear after the dungeon has been generated.
The detect effect does not persist, if that's what you are asking. So if you kill long-range something that you cant see and it drops and object where you previously casted detect, then you would not become aware of it.

[backwardsEric]

I had in mind this scenario:

1. @ uses a scroll of detect object
2. Now there's a detected unknown item.
3. Scruffy-looking hobbit takes that unknown item.
4. @ uses another scroll of detect object and the original detected location is in range.
5. Should the unknown item shown on the map go away?

[Derakon]

Makes sense to me. The lack of signal should be a sufficient clue that something you previously thought was there no longer is.

[DavidMedley]

I'm sure someone was just trying to save a few cycles long ago.

[Sky]

ah, no then. those treasure markers are what your character writes on their map, but once the spell has ended, you no longer receive info from the objects.

[Derakon]

Originally Posted by Sky

ah, no then. those treasure markers are what your character writes on their map, but once the spell has ended, you no longer receive info from the objects.

In the given example, the spell is used twice, and the object is removed after the first casting. The character ought to be able to say "according to my notes, there should be an object there, but when I cast the spell the second time, I did not detect an object there. It must have been moved or destroyed." Consequently they can remove the mark from their map.

[DavidMedley]

Come to think of it, I noticed in the code or one of the change logs that the player has his own complete map anyway. So it wouldn't even take that long (in processor time) to remove the in-range *s and then apply new ones.