Demonbuddy concerns

[mginster]

There I took out an fbomb and maybe tony won't close it.....

My concerns are entirely valid below and I was not a trolling asshole as one points out...

Yes, you can create a quest that is not selectable. Rush an account to azmo a3 without doing any a3 quests. You will have the initial quest and azmo as the only selectable quests for a3. Demonbuddy however can create a game in between those quests while a real user would be unable to.

On the topic of ilvl, sure you can shift click, but do you really think anyone is 100%.

I am merely pointing out flaws with demonbuddy, yet the close minded devs continue to state db is as safe as they can make it. So what are you devs going to say after the next banwave? Listen to your customers!!!



Original post closed by tony for no reason is below:



Demonbuddy is now as safe as we can make it....
That is a very bold and irrational statement. No software is ever as safe as you can make it.

- Game joins still do not select the quest / act from the UI, but rather join directly. If the devs theorize that having the inventory window open when identifying is detectable by Blizzard, then why do you not also resolve this issue.

- Being able to create a game on a quest you have not yet unlocked is a flaw.

- Pickup rules are unsafe. Blizzard can detect if someone doesn't ever pick up an ilvl 58 amulet, considering you have no clue what ilvl it is when its sitting on the ground.

This list could go on forever if the devs are really going to be so arrogant to state "Demonbuddy is now as safe as we can make it."

 

[ToeNisLubBer]

If you dont like their product, dont use it.
Also, you can customize what ILVL you want to pick up.

edit: ALSO, you can detect what item level the item on the ground is. Its called CTRL click. Advanced tool item settings something in game options...

 

[Job2k9]

They closed your thread and you made a new one... I can see where this is going. Try to have a good Christmas.

 

[Aion]

They closed your thread and you made a new one... I can see where this is going. Try to have a good Christmas.

Flaming constructive comments is worse than trolling.

He made some valid points. The concerns he share seems logical and in place with the last weeks banwave, from a non-dev point of view at least.
And its pretty obvious, that some of his comments towards the devs are "overreacting", which may led to his previous post removed.

 

[hackerlol]

If you dont like their product, dont use it.
Also, you can customize what ILVL you want to pick up.

edit: ALSO, you can detect what item level the item on the ground is. Its called CTRL click. Advanced tool item settings something in game options...

They closed your thread and you made a new one... I can see where this is going. Try to have a good Christmas.

I have not read his previous thread but what is wrong with this one ? Unless the points he brought up are untrue.
I for one did not know that DB could create games that the client wouldn't normally allow a player to..

 

[Tony]

DB cant create games when a quest step or difficulty step is locked and also you can check item lvl on an item as a human as well


now you know why your thread got locked


so its better to double check things before posting

 

[mginster]

DB cant create games when a quest step or difficulty step is locked and also you can check item lvl on an item as a human as well


now you know why your thread got locked


so its better to double check things before posting

Just try the steps I layed out with azmo a3, you can create quests that are not selectable in the ui.

I'll drop the ilvl argument, my other points are still valid.

Also the main point I am trying to make is still entirely valid, the db devs claim the software to be as safe as they can make it, yet there are still flaws that can even be seen by the users.

This is a product we paid money for, we should treat it just as we treat any other paid software. We submit bugs, support requests and assume that someone will listen and not just close threads and make false claims.

 

[richarjb]

DB cant create games when a quest step or difficulty step is locked and also you can check item lvl on an item as a human as well


now you know why your thread got locked


so its better to double check things before posting

Tony, you are clearly NOT understanding the issue he is pointing out. Stop being arrogant and read what he is saying.

DB will *ATTEMPT* to create an Act 3 Inferno Quest BLAH game even if you dont have it unlocked. If you fire up wireshark you can clearly see network traffic being sent to the server... the REMOTE SERVER responds with an ERROR and the local client parses it. You see the problem? The client couldn't request that ACT/Difficulty and the server knows it so it responds with an error.

 

[Eisenberg]

Is it really so big problem that db can create game wit locked q ? Just be sure to unlock and select proper q in D3 client BEFORE u run DB, theres a difference between making bot "as safe as possible" in terms of blizz detection and in terms of foolproofness

 

[richarjb]

Is that really so big problem that db can create game wit locked q ? Just be sure to unlock and select proper q in D3 client BEFORE u run DB, theres a difference between making bot "as safe as possible" in terms of blizz detection and in terms of foolproofness

Is it a problem that with one simple mistake (loading wrong profile) results in the client generating a request to the server it could NEVER make on its own? YES. Do you know how easily bliz could use this to flag accounts? This is a HUGE issue. I brought it up a while ago in support. HAWKER liked the post... said he agreed it was an issue and that it would be fixed.

http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/97237-server-side-bot-detection-via-gui-bypass.html

I also understand the frustration the OP is experiencing having his thread closed by a mod who doesn't have a clue (didn't take the time to read) what he is talking about.

 

[mginster]

Hawker also agreed to my point regarding how db joins games (joining directly from any quest/act screen), yet that was also closed shortly thereafter.

 

[ToeNisLubBer]

It's because your bringing up things they have already addressed and are working on.

Hawker - This is one of the things we are looking at. Even if its not the cause of so many bans, we will likely change it.

And well... some of the stuff you said was 100% wrong. If you are trying to alert people with false information. They should close the thread. At least have it all correct.

 

[Tony]

we will cover(if not already) what we thinks that needs to be covered

this doesnt mean that we will follow every theory people are posting here

suggestions are welcome tho,but people should be check before posting

 

[richarjb]

Tony

[1] You didn't acknowledge that the game creation was an issue in the OP's original post -- you just closed it and you were rue about it. You also did so without understanding/reading.
[2] This isn't a wild tinfoil hat theory and your public reaction throws it into that bucket. This is such a serious issue it should be stickied. I've personally spent a couple of hours in wireshark/ida pro/immunity debugger verifying this is an issue.
[3] There was no open thread on this. I posted it in support and even though Hawker liked the post someone else closed it saying it belongs in Dev.

This is going to be fixed, I know it is... and I know it's not a quick fix either. The "detection fixes" you guys put into the most recent release were easy and quick to implement and they were to quiet us all down. If anyone thinks that selling/ID'ing stuff in order == flag they are just silly. Compare that to the game client performing actions not presented to the user... calling functions with arguments that the GUI wouldn't allow... that's where you need to be looking.

ATTENTION DB USERS:
If you load a profile (eg INFERNO) and your character does not have access to that level of difficulty OR if the profile you loaded starts at a quest you have not unlocked it *WILL* attempt to create a new game. A request WILL be sent to the server. Blizzard WILL see you are using 3rd party tools to launch games.

I understand that frustrating, stupid, re-occurring tinfil hat theories pop up and you need to shut them down as a mod. As a mod, it is also your responsibility to see when they are not.

EDIT: I forgot a word.

 

[Smitherer]

I hope this Mginster/Richarjb's theory is not working just like that! I was used to group up all my slaves to same game wich is even funny to observer.

This idea of sending requests to the server wich are not normally possible to send. I started to realize being sending quite a lot of them, before got my first hit by hammer.

My dudes are allways grouped, they wont leave group even when they start new profile. Pretty often the timing goes like one of the bots is still on game when the leader is trying to make new game, and since in that situation it is only possible to "Resume game", it will end up with an "error". Leader is trying to "Start game". Request sent.

In theory I could allmost avoid that kind of behavior, if I manage to fix them leave party after profile is done, but im pretty sure that someday of month they manage to send couple of those requests anyway, they are verry creative little....

I hope this is nothing that can be used againts anyone! I would like to continue party.

Those "requests" from errors are not gathered to later investigation anywhere? If they are, can you please tell me?

 

[Tony]

Tony

[1] You didn't acknowledge that the game creation was an issue in the OP's original post -- you just closed it and you were rue about it. You also did so without understanding/reading.
[2] This isn't a wild tinfoil hat theory and your public reaction throws it into that bucket. This is such a serious issue it should be stickied. I've personally spent a couple of hours in wireshark/ida pro/immunity debugger verifying this is an issue.
[3] There was no open thread on this. I posted it in support and even though Hawker liked the post someone else closed it saying it belongs in Dev.

This is going to be fixed, I know it is... and I know it's not a quick fix either. The "detection fixes" you guys put into the most recent release were easy and quick to implement and they were to quiet us all down. If anyone thinks that selling/ID'ing stuff in order == flag they are just silly. Compare that to the game client performing actions not presented to the user... calling functions with arguments that the GUI wouldn't allow... that's where you need to be looking.

ATTENTION DB USERS:
If you load a profile (eg INFERNO) and your character does not have access to that level of difficulty OR if the profile you loaded starts at a quest you have not unlocked it *WILL* attempt to create a new game. A request WILL be sent to the server. Blizzard WILL see you are using 3rd party tools to launch games.

I understand that frustrating, stupid, re-occurring tinfil hat theories pop up and you need to shut them down as a mod. As a mod, it is also your responsibility to see when they are not.

EDIT: I forgot a word.

its just another theory like other theories on forums
also you have to read more carefully and understand what OP said

he said that DB can create games when the quest/difficulty are locked
this has nothing to do with the fact that DB is trying to create a game and receives an error


can you see the difference or not?

 

[blista08]

There I took out an fbomb and maybe tony won't close it.....

My concerns are entirely valid below and I was not a trolling asshole as one points out...

Yes, you can create a quest that is not selectable. Rush an account to azmo a3 without doing any a3 quests. You will have the initial quest and azmo as the only selectable quests for a3. Demonbuddy however can create a game in between those quests while a real user would be unable to.

On the topic of ilvl, sure you can shift click, but do you really think anyone is 100%.

I am merely pointing out flaws with demonbuddy, yet the close minded devs continue to state db is as safe as they can make it. So what are you devs going to say after the next banwave? Listen to your customers!!!



Original post closed by tony for no reason is below:



Demonbuddy is now as safe as we can make it....
That is a very bold and irrational statement. No software is ever as safe as you can make it.

- Game joins still do not select the quest / act from the UI, but rather join directly. If the devs theorize that having the inventory window open when identifying is detectable by Blizzard, then why do you not also resolve this issue.

- Being able to create a game on a quest you have not yet unlocked is a flaw.

- Pickup rules are unsafe. Blizzard can detect if someone doesn't ever pick up an ilvl 58 amulet, considering you have no clue what ilvl it is when its sitting on the ground.

This list could go on forever if the devs are really going to be so arrogant to state "Demonbuddy is now as safe as we can make it."

You
Are
A
Moron

The statement "Demonbuddy is now as safe as we can make it" simply means that. "It is as safe as it's going to get" as in they've exhausted all options that are relevant to super cockroach tin foil hat people like you.

 

[Alekssis]

Tony

ATTENTION DB USERS:
If you load a profile (eg INFERNO) and your character does not have access to that level of difficulty OR if the profile you loaded starts at a quest you have not unlocked it *WILL* attempt to create a new game. A request WILL be sent to the server. Blizzard WILL see you are using 3rd party tools to launch games.

I understand that frustrating, stupid, re-occurring tinfil hat theories pop up and you need to shut them down as a mod. As a mod, it is also your responsibility to see when they are not.

EDIT: I forgot a word.

Writing profile is not without errors. How then do you check them out, that would not be noticed by Blizzard?