Notes |
(0012389)
reid (reporter)
2011-04-11 08:26
|
I've also observed this happening a couple times today where the monster trail appears on a mapped square, so the fact that the square is unmapped isn't a critical part of the bug. It does make it more obvious that something odd has happened, though. |
|
(0012430)
jpeg (manager)
2011-04-12 22:48
|
This was unintentional, but I rather like this behaviour. :)
It displays information the player already has (there's an orc right behind that orc warrior on the edge of vision), so I didn't see any point in blocking this behaviour and instead went the opposite route of also making it work in Tiles. Still, thanks a lot for pointing this out! :D |
|
(0012433)
elliptic (developer)
2011-04-12 23:24
|
jpeg: If I understand the bug correctly, it tells the player which square the monster who pushed forward was on... definitely *not* information the player already had. |
|
(0012434)
KiloByte (manager)
2011-04-12 23:29
|
elliptic: it depends if you consider strictly the information you can see on a screen (ie, in discrete snapshots every once a turn) or what you would see with slightly realism. For example, in early tile games like Civ 1, you could see the direction an enemy came into LOS from.
Both interpretations are valid. |
|
(0012435)
elliptic (developer)
2011-04-12 23:35
|
Kilobyte: But then why can't I tell where an enemy comes into LOS from when it isn't pushing past another monster? |
|
(0012443)
KiloByte (manager)
2011-04-13 00:41
|
It's not something that usually matters, so the game doesn't bother telling you that. |
|
(0013418)
reid (reporter)
2011-06-08 04:52
|
You also can't see which way a fleeing monster went when it just left your LOS, which matters rather more often. |
|