Just some stupid idea :D

On the contrary, it has everything to do with Abyssion's post.

It doesn't matter if you're actively botting or not...If the bot is running, it can be detected...That's how a detection works. I'm sorry that's hard for you to understand, but that's how all of this works.

The bot can't be running if it's not attached to the wow process. Go ahead and try to start the bot without having wow running. It will clearly tell you that you that it needs an HB process to attach to. If it's attached, it can be caught in a scan.

 

Abyssion's post and mine never said and asked how detection goes and how HB works
ofc u must attach to the wow but thats all,u dont start ur bot to take over character,thats simple

 

If you're going to get caught in a scan, it won't be because you have the bot running. It's because you attached to the wow process. Running the bot means nothing if you hooked into the process. You may not care at all about how HB works or how a detection happens, but you should at least somewhat educate yourself before asking people to do experiments for you. You look silly saying you want to know if they scan our computers and then saying you don't care at all about the workings of software.

I keep asking this over and over, but why do you care at all if they do scan our computers for software if you don't care at all about the security of your account? What exactly are you going to do with the knowledge you gain from such an experiment if you don't care about security?

 

sign 100% what ryftobuddy says. Wonder that he spends so much energy in answering such a stupid question which we had already discussed here again and again and again ....you know ^^

 

Im gonna tell people stop asking do blizz scan,cuz we did experiment it works,its proved,dot.Thats what we will do with knowledge
And again i will say,read carefully cuz my english is bad
I know how HB work,i know he attach on wow proccess
Now do it ur self,start wow,double click Hb but never click a start button on HB,never load some profile or anything,play manual,that way u have it running into proccess list,but u dont use it on character,u play manual.
I cant explain this simple step better cuz my english,but if u still have an answer on this ill give up u won u can close thread
Bdw,thanks for answering

 

lol...you think blizz is going to not scan your pc because you asked them to...That's funny. Keep in mind that you agreed to allow them to scan your pc when you agreed to the TOS. Since you agreed to the TOS, they are within their right to scan. If you don't agree to the scan, you don't agree to the TOS, and you no longer have access to play the game. It's the same for you or anyone else. If you don't like their written rules, you have absolutely no recourse other than not playing.

And if you want the answer to your question so bad, do the damn experiment yourself. I can tell you with 100% certainty that you will gain nothing from it, prove nothing and won't sway anyone with said experiment.

 

Guy already did that experiment and he got banned,there is thread i found here.
Ur right about ToS

 

I think there is some confusion here (yes, i go by captain obvious occasionally)

There are several types of "scanning" and "detection" at play here.

1. Intrusive scanning of the entire PC and it's processes. This is the scanning warden did a few years ago until Blizzard got their hand slapped. It is generally thought that Blizzard no longer does this. If they are, they are assuming some legal risk and I dont think it is likely they would.
2. Scanning within the game client and it's processes. This is where Warden will watch the memory and resources allocated to the game to detect if another process is interfering or modifying the data. This is the part where Bossland claims they are not detected. There are several techniques I am aware of being used that may be detectable by Blizzard (framelock being one of them). I am not saying it is detectable but it is conceivable that it would trip some sort of performance monitoring within the client that would get reported back to Blizzard.
3. Behavior. This is where most bans are assumed to come from. This is where the bots "look" like bots and are reported.

I think kekic's "experiment" might have some value if you can "sanitize" all the other factors. Blizzard can and probably does capture information like CPUID, network info...etc.

If you attach wow but never run it and it still gets banned, you have verified that HB is detected on a process level and that it is not simply behavior based bans.

So with all the hostility, it is useful to state clearly what kind of detection you are trying to test.

 

Yes,that is what im trying to say. Good explained

 

Ok, this may be, but there is absolutely no way to, as you put it, "sanitize" one method from the other...

And you still haven't given a valid reason why you want this information, other than to have it...

I'm done with this thread, I'm done with kekic91. There's absolutely no value in having the information they're looking for, there's no way, at all, to prove what they're looking for, and there probably never will be. You can go ahead and keep referring to that other thread, but that thread contains about as much useful information as the rest of your posts in this thread.

 

There are ways, but they require a bit of effort and expense. i don't think the results are worth the effort.


I never said i "wanted" the information.

 

Again i agree with this,only part with he dont want info is part correct cuz i want info just to share it

 

Honestly, i dont see the benefit of doing this in an open forum.

I see benefit for Bossland, and i expect they do these sorts of tests regularly.

Having specific information exposed in a public forum is not a good idea.

 

If they do such a test regularly we dont have idea about it
Well,if it is exposed i dont see any harmfull actions ,but maybe ur right idk