Haven't used Honorbuddy since the huge wave last May, I was just wondering... did the Honorbuddy team adapt what the Demonbuddy team came up with for attempting to "hide" the *buddy process from Blizzard/Warden? Basically utilizing local user accounts on the machine to run the game as that user so that it's kind of "sandboxed" in the processes it has access to. *buddy is then ran as an admin which gives it access to the game but not vice versa. Obviously wouldn't help at all if Blizzard knew IP ranges of the buddy service itself, but for other kinds of detection it can.