I am asking this question here because i think it is HB's responsibility to not allow community devs to create these problems. I wont mention specific items in the Buddy Store that I am observing this with because i do not want this to turn into a flaming thread. So, 2 questions....
1. Please correct me if i am wrong but the only HB component that should really be using framelock are Combat Routines...right? Why would a Botbase need to use framelock? I notice my Wow client freezing at the same point every time and it looks the same as when i try to use framelock and am sloppy with the code to do so. If CRs are the only ones that should be using it, HB should prevent other objects from using it.....IMHO.
2. Whn i switch botbases, a certain botbase does not seem to go away. I see log messages from it as if it is still active. The only way to truly unload it is, to switch to a different botbase, shut it down and then restart. If i close with said botbase configured, the problem is still there at startup. Even if i never start HB.
Why does HB allow this? It should terminate anything the Botbase is doing when i change to another Botbase.
1. Please correct me if i am wrong but the only HB component that should really be using framelock are Combat Routines...right? Why would a Botbase need to use framelock? I notice my Wow client freezing at the same point every time and it looks the same as when i try to use framelock and am sloppy with the code to do so. If CRs are the only ones that should be using it, HB should prevent other objects from using it.....IMHO.
2. Whn i switch botbases, a certain botbase does not seem to go away. I see log messages from it as if it is still active. The only way to truly unload it is, to switch to a different botbase, shut it down and then restart. If i close with said botbase configured, the problem is still there at startup. Even if i never start HB.
Why does HB allow this? It should terminate anything the Botbase is doing when i change to another Botbase.
Last edited: