24-Mar-2013, 1:54 PM
Quote:Whoa, if you're actually handling competitive issues...I sent you an email in the middle of June about a Lynx issue, which appears to be related to ajmiam's thread on clone desynchronization in Lynx. I'm not actually sure if you got it, since you never responded (I think I came across rudely in that email, so that could also be the reason why). In any case, that issue is worth a fix as well if you can track down the source of it.
I apologize for not responding to your e-mail, my dear fellow. You certainly didn't come across rudely.
It came at a time when I "couldn't be bothered much", and that situation has - over the past few months - further degraded to approximately zero CC time. That message has been lying in my Yahoo Inbox as the one unread message which I must some day reply to, for so long now, that I am used to seeing "Inbox (1)" as an indication of no new mail, and dare not open it for fear of being confused.
Just kidding.
Meanwhile, Miika - who has the ability to send me messages that seemingly innocently meander into random topics in a way that somehow prompt me to respond - hath discussed an odd behavior with a bug turning around when it could-and-should have turned right (in a level constructed by random8 I think), which he cleverly presented in the form of screenshots to sufficiently arouse my curiosity. I believe it was not a bug (I mean the behavior) and provided a hypothesis that would explain it [forwarded that to you now]. The crux was that if a creature makes a choice of direction on step x, then on step x+1 it will "turn" in that direction, irrespective of whether that direction is now blocked; and if indeed blocked, then on step x+2 it will make its new choice of direction with the consideration that it has already "turned". Possibly the same applies to Blazes, but I'm still too lazy to check the TWS or the code.
- Madhav.
[Goes back into cave.]