I have the same source pull date, and have also noticed this issue. I was assuming it had to do with adding a field in the npc_type table (attack delay or something?) and it may be throwing a column read off somewhere, but I didn't notice until this source pull.
I will say that I do not think it is a bug, but an oversight on my part though. Will post back if I resolve the issue.
|