FAIR WARNING: I'm not an expert or even good at this kind of info I'm going to mention. It's just what I've heard and my experience and piecing together a guessing game based off that. Grain of salt.
Most people saying they were banned and never use it are likely not all truthful, but I can confirm that the bans happened to non-honor buddy users who use the same method they did for lua stuff, or at least I assume that is why I got banned on some accounts I did not use HB on. At first glance, it seems that some kind of trace on a call stack from a lua related function caught it.
I'm just not fully confident in that though because while I was banned as well on private software with no HB use at all on those accounts, I also have zero protection in the 'software' to protect my self from checks on the call stacks, solutions exist in a few different ways and I assume honorbuddy had already added protection for this when they noticed the hook added to a client a few months ago and analyzed it.
I'd say right now it is more likely their protection was just simply not enough to avoid detection or added another way to detect it as a side effect of the fix. It would work sort of like this if it is the case, though:
1. Login > Receive detection packets > Detection hook on _lua_load starts > detection packer handler loaded
2. User loads HB or program using the same code to execute lua stuff or close code.
3. The hook on _lua_load catches it by checking the call stack for anything calling this outside of WoW directly.
4. Blizzard sees the call coming from the stack to _lua_load now, flags you for a ban, ba
Most people saying they were banned and never use it are likely not all truthful, but I can confirm that the bans happened to non-honor buddy users who use the same method they did for lua stuff, or at least I assume that is why I got banned on some accounts I did not use HB on. At first glance, it seems that some kind of trace on a call stack from a lua related function caught it.
I'm just not fully confident in that though because while I was banned as well on private software with no HB use at all on those accounts, I also have zero protection in the 'software' to protect my self from checks on the call stacks, solutions exist in a few different ways and I assume honorbuddy had already added protection for this when they noticed the hook added to a client a few months ago and analyzed it.
I'd say right now it is more likely their protection was just simply not enough to avoid detection or added another way to detect it as a side effect of the fix. It would work sort of like this if it is the case, though:
1. Login > Receive detection packets > Detection hook on _lua_load starts > detection packer handler loaded
2. User loads HB or program using the same code to execute lua stuff or close code.
3. The hook on _lua_load catches it by checking the call stack for anything calling this outside of WoW directly.
4. Blizzard sees the call coming from the stack to _lua_load now, flags you for a ban, ba
