This behavior happened to me for several custom items I created. I'm pretty sure it has to do with an item property that was not set correctly, but I don't know which one. In the attack.cpp file, I saw *why* it chooses the punching motion, but I can't figure out what would cause that condition to be triggered...
This is likely going to end up being a problem for a while, since it is a relatively harmless bug... And thus, you're not going to get a lot of people working on it.
|