Eh, like I said, it was probably just an anomaly of the old system which let some minor coding mistakes slide and now that the new system is in place, they come back to haunt me. But the program glossing over those problems should be no reason for sloppily coded pony.inis, so yeah, not really looking forward to checking all those ponies, but if that's what needs to be done, then okay.
Now, the program automatically re-enabling auto-select even when it was disabled in the pony.ini is still something I find strange, because that's an anomaly that goes against the coder's wishes. Buuuut eh, that's just me, and since this only affected a few ponies, it's probably no big deal.
About the collision detection: Back in the era of DesktopPonyGuy, I once suggested that the ponies should maybe use a simple hitbox for their collisions instead of relying on the sprite boundaries. This would probably require an additional line of code in the pony.inis specifying the approximate size of the character, but since most ponies are based on the default templates anyway, this could be optional, defaulting to a set size if omitted (to ensure compatibility with older ponies).
Or just, you know, have the ponies not go crazy if their sprites ever so slightly overlap an area they are not supposed to be in. Whatever is easier to implement. At the very least, it shouldn't cause them to enter desperation mode.
Last edited at Sun, Mar 2nd, 2014 16:41