If it is Pull Distance, then it is HBcore's fault. A program should *never* allow a property to be set to an invalid value--either through the GUI or API. To allow such is just plain sloppy programming (at several layers, but the buck stops with HBcore).
Kick's Wintersaber profile is only a couple of months old, and most others are interested a *lot* of other stuff besides Wintersaber Rep. So, its also completely understandable why this error has yet to be encountered. It could also be tied to the class that is running the profile, or other such things.
In any case, it boils down to sloppy programming at several layers (Profile, CB, HBcore). The buck stops at the HBcore.
cheers,
chinajade
There is no reason to have pulldistance set to 0. Melee is 5 so at the very least maybe 4.
Programmers shouldn't have to put catches for human stupidity.
They shouldn't but i guess they might start having to. Sigh. When did everyone's mentality go from "let me try to fix this myself" to "omgz why doesnt this work!?!! fix now!11!oneleventeen."
"cheers",
Rory