Errors happen, sooner or later a bug always appears. It's the unwritten rule of computer science. And as it has been thoroughly discussed it happened for the render part too.But we can agree that something like the Dylan error should never have happened, and if it did happen it should have been fixed quickly, right? From a basic sense of pride that should have been fixed quickly.
This one seems more like a distraction error to me, as in e.g. he changed the value to test and forgot to set it back. Or something like that.
It's no shocker to me. I'm more surprise that so far there are no errors on the event dependencies: the number of choices, outcomes and branches are starting to multiply and, as I said before, this can be easily become a mess to deal with.
On the other hand, I completely agree that it was so easy to fix and it has been reported by the users so quickly and early that making a patch or a new release would have taken what, 15mins, upload time included? Dismissing it with the excuse that you can now cheat is sloppy to say the least. It's something that would trigger the OCD of any programmer in no time
And it's strange for a perfectionist like him, but I guess that he is really obsessed with the rendering part rather than the code (and if you look at the code you clearly see that he lacks some basic programming background).