[Blizz Updated] Process killing Agent | Battle.net closes WoW as well.

So for a long time now we have been able to kill the processes regarding agent / webproxy / battle.net and still use WoW for botting / playing.

As of apparently this week (just tested this today and was working before maintenance) you now have wow.exe as a child process within those, making any process end request of the above agent or battle.net will kill wow along with them.

I'm not sure if very many people use this extra feature of process management but for some of it is a key role in botting and how we handle things.

 

Pro-tip: Suspend the process

Edit:
https://i.gyazo.com/1b0ccffadde1956a5de8dc61f18d0e8f.png

Wow isnt a child process of Agent.

 

Suspend isn't really a good idea since it can be reinstated without any notice if you are using a listener / watch service for specific processes. Wow hasn't ever been tied to those 2 PIDs before until just recently.

Good tip regardless if you just want to suspend.

 

Can you elaborate? I'm not familiar with this practice. If I understood you right, in task mngr there's a process ran by blizzard/wow/battlenet that is suspected to monitor our playtime in a suspicious way? But they put the game client under it so killing that process would close the client too?

What's the name of the process and what's its purpose?


Edit: Saw following post, so it's the update process 'agent' and we can't disable it anymore? Do we know if it has more nefarious tasks besides just updating the game client, or are we just speculating? There's gotta be a thread on this somewhere I'll look...

 

Yes that is correct, but what Agent does outside of updating battle.net, is unknown if anything at all.

I have found a workaround currently that seems to keep everything from freaking out.

- Run the HB launcher
- Get fully logged into the game
- Kill Agent if it's running
- Kill webbrowserproxy (it loads when you go in game)

This keeps battle.net from wrapping wow under it's PID and seems to allow you to disable the agent separately.

 

Hope you guys know this does the complete opposite effect of what you are trying to achieve.

But eh, I can't change what you think.

 

The opposite...no not really.

 

proof?

 

many times across multiple forums. restricting the processes down to just the exe with no wrappers keeps it all in one place as far as PIDs monitoring and memory monitoring. I'm sure someone here will want to say that dropping those PIDs (processes) will cause flags or hurt you but it seems to be the one thing I'm doing that's not getting me banned in these waves like most others, when I bot the same stuff everyone else does.

 

I have no issue killing it, im using the same batch file.

 

I would love to have an official statement from hb on this

 

An official statement on something that isn't part of the HB bot, nor involves any functionality of HB in any way? Yeah, ok...

 

yeah that wouldn't happen.

 

Would the buddy staff please entertain us and let u know if this is something we should worry about? I know blizzard is starting to do what they can ingame to beat botting.

 

The HB team never has, nor will they ever, comment on Blizz's detection schemes BEFORE a banwave.

As has been stated, the discussion going on has absolutely nothing at all to do with HB as a bot, nor is the killing of processes part of any protection scheme that HB employs.

If you're expecting a response from the HB team on this matter, you're not going to get one.

 

Problem with your theory is people that do this ARE getting banned. You can claim you haven't been banned all you want, it doesn't change the fact that others are getting banned regardless if they do this or not. In my own personal experience, I appear to get banned faster.

Conclusion: Completely look like a legitimate user, this includes not doing something Blizzard can so obviously detect/flag/give you points (what ever you want to call it) for.

This isn't just a little detectable, it is ridiculously easy to detect for.