What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

DB Create Game Flaw - Possible Bot Detection

Status
Not open for further replies.
M

mginster

New Member
Joined
Aug 28, 2012
Messages
124
Reaction score
0
So I made a post a few weeks ago proving that DB was not as "safe as we can make it" as the developers stated after the banwave. In it I posted a topic regarding DB being able to create quests that are not able to be selected in the UI. Tony stated the quote below.

Original Post:
http://www.thebuddyforum.com/demonbuddy-forum/98354-demonbuddy-concerns.html

Tony said:
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
Click to expand...


Here is a Jing video proving it is possible and that maybe the devs should actually listen to the users. Its large so let it load first. This is an A2 creation without A2 selectable in the UI. It proves the DB game creation process goes outside what a normal user can perform. Also, upon leaving the game, A2 still shows as locked, yet my character obviously went to it.

DBA2 - mginster's library

I wonder how many people are botting with accounts they rushed to A3 Azmo with their mains. Any creation of a quest outside of Azmo would be invalid and possibly detectable by Blizzard.
 
hotfix: dont be retarded enough to set your bot up to load shit you havent unlocked.
 
macedawg said:
hotfix: dont be retarded enough to set your bot up to load shit you havent unlocked.
Click to expand...

While that is true, at least it should be advertised. There are many people that set up their bots by rushing to A3/4 but run other acts/quests.
 
same happened by me before your last post. bot enter A4 when A3 is not finished.

but i didnt wanna waste my time to talk about this with DB team.

tony will give you a link : how to post your DB log.
or maybe " the video can be fake."
 
Last edited:
Just tested it:
New Barb Hell A1 -> i loaded Profile "New Hell A3) from RRIX, and it created the game. I freshly got to Hell, so it was never unlocked.

that's cool :D
 
Nesox said:
It's impossible to start quests you haven't unlocked.
Click to expand...

That is true. You cannot go forward to a quest that you have not obtained yet, but you can create a quest that is not selectable in the UI, which is the core issue posted. This would mainly be a problem for anyone that rushes their character with their mains (most multibotters). If you quest all the way to the point where you will bot then you will still be fine.
 
Nesox said:
It's impossible to start quests you haven't unlocked.
Click to expand...

I understand your point, but i just tried with a second char.

Try it please yourself, i did it exactly this way:

lvl 53 Char -> go to "Select Quest" only Act 1 & 2 is unlocked.

i go to DB and load profile A3 START NEW Hell

Whoops -> new game created A3 hell, without A3 unlocked.

If i post something like that, you can trust in me.
 
Its been able to do shit you couldnt since release. The original release could teleport to town without you being able to port yet (level 1) they said nope not possible for weeks yet people were doing it. How about the fact that it creates a game without opening the window to select quest ? You don't think blizzard can see if you opened that part of the UI ?
 
mginster said:
So I made a post a few weeks ago proving that DB was not as "safe as we can make it" as the developers stated after the banwave. In it I posted a topic regarding DB being able to create quests that are not able to be selected in the UI.
...snip...
I wonder how many people are botting with accounts they rushed to A3 Azmo with their mains. Any creation of a quest outside of Azmo would be invalid and possibly detectable by Blizzard.
Click to expand...

Thanks. We will fix this. Meanwhile we don't recommend you use this exploit and it would be easy to detect server side were Blizzard minded to do so.
 
Status
Not open for further replies.
Back
Top