#1821 closed bug (fixed (in master))
"Chest mimic is no longer hasted" but player didn't know it was a mimic
| Reported by: | takkaria | Owned by: | |
|---|---|---|---|
| Milestone: | 3.5.1 | Keywords: | |
| Cc: |
Change History (5)
comment:1 Changed 5 years ago by noz
comment:2 Changed 5 years ago by takkaria
- Status changed from new to pending
So I did some hunting down and the only way mimics can be hasted without being activated is aggravate monster. So my fix in 2226386 activates mimics on aggravate effects.
comment:3 Changed 5 years ago by noz
Really? I tested with a shrieker mushroom patch and a chest mimic, and I thought the mimic got hasted without being noticed. I can check again.
What we should do though is decide what the behaviour *should* be, and then code that! :-)
comment:4 Changed 5 years ago by takkaria
- Resolution set to fixed (in master)
- Status changed from pending to closed
That's what I did - I asked on angband-dev and coded the desired behaviour that came out of the discussion. It just wasn't committed to a public repo yet, sorry! (hence 'pending') Should be fixed in 3.5-release now
comment:5 Changed 5 years ago by PowerWyrm
Note that "cloning" effect is still weird. You notice that there was a mimic, that it is now hasted and that a new one spawned, but the spawned mimic is not discovered as it probably should.
Not quite sure what the correct behaviour is here. There is code to say "something starts moving faster" and "something slows down", but is that correct - if the mimic is the only thing in the room, do we want to say that, or say nothing?
Actually that code also has a flaw, as the monster name is set to "something" if unaware, but the next bit of code changes the "something" into "it".