From articles I've read, it looks like Warden protects critical in-game memory addresses targeted by bot programs. Nice article here:
https://jordanwhittle.com/posts/exploiting-warden/ . Maybe it is also guarding the keyboard and mouse input chain, but there are a lot of programs that legitimately modify them. There's also scanning of Windows processes for known bad actors. Presumably, InnerSpace is now on that list, so logging in with the software running would [presumably] trigger a suspension or ban. A temporary workaround would presumably be for InnerSpace to be called something else, say, "Bob". Eventually Blizzard would find out that "Bob" is also a "bad actor" and update the Warden to include it. Instead, what I'm hoping is that "Bob" will be a version of InnerSpace that doesn't have the keyboard broadcasting component *and* Blizzard is smart enough to realize and accept this as ok, rather than doing another knee-jerk ban. My point is, simply not using the key broadcasting in InnerSpace is unlikely to avoid a ban.
I've seen those flocks of druids sucking herbs dry in Nazjatar. I started multi-boxing my own herbingin defense simply to get a full stack of herbs from *an hour* of flying around Nazjatar. I've also organized a raid group to down a group of 8 multi-boxed druids in War Mode. Single players had no hope of surviving. Those things are what prompted the ban, I'd guess.
I'd like to still be able to see more than one WoW client on screen and a time and click between them. I'm hoping that "Bob" can do this and everything will go back closer to normal.
Posted: Fri Nov 06, 2020 10:59 am