xcrossover25x
New Member
- Joined
- Apr 7, 2012
- Messages
- 47
- Reaction score
- 0
I was originally going to wait for this to come out before buying another other bot, but decided it wouldn't be worth it to wait when I could cash in on the profit early, and then migrate to this because I thought it would pull the same numbers and be safer. It could not be any more the opposite.
I bought this this morning, have not got it to run over 30 minutes at a time without getting stuck. Can't even get it to pull 30% of what other bots can pull out of the box. You may just say - "This bot just came out, of course it is bad for the first few days, wait a while before judging it."
No- The truth is this bot was in development for a month. Other bots were released the first week of D3 and were almost flawless. They are faster then DB, they are more configurable, they don't require going into notepad files and require you to download profiles, download custom classes, download plugins. Anything of the sort, they all work really well out of the box, and are highly configurable to increase gains.
Since this thread will probably get closed, in an effort to try and keep it open for constructive criticism here is a list of what I think could be changed/improved.
- Why does the bot get stuck at all? I don't even understand why this happens, if the bot goes up to a wall and then just doesn't do anything there must be a huge programming fail there. I don't even see how you could overlook this.
- Why is it so slow? It pauses sometimes between movement, it ignores targets, it starts to attack targets but then ignores them, and then 100 yards later will decide to go back and get them. How do you overlook this?
- Why is it so clunky? Why do we need to download profiles custom classes loot configuration files just to get it to work? If you could make it into an all-in-one .ini file, this would work wonders.
- Not supporting spells. Why can't I use teleport for my wizard. It couldn't be that hard to program? If teleport is up use it to get to your next waypoint. ??????
- There are probably a lot more, but I'm going back to the other bot. I would gladly risk getting banned once a month in exchange for a 300% increase in yield and stability.
If by chance there is anyway to get a refund I'd be glad to hear it, it is a pretty massive fail when autoit scripts can pull more gp/h then a bot in development for a month.
I don't mean to say that DB should cease operations here, people can use this all they want, I just want to give honest input as to why I'm reverting back to other bots.
I bought this this morning, have not got it to run over 30 minutes at a time without getting stuck. Can't even get it to pull 30% of what other bots can pull out of the box. You may just say - "This bot just came out, of course it is bad for the first few days, wait a while before judging it."
No- The truth is this bot was in development for a month. Other bots were released the first week of D3 and were almost flawless. They are faster then DB, they are more configurable, they don't require going into notepad files and require you to download profiles, download custom classes, download plugins. Anything of the sort, they all work really well out of the box, and are highly configurable to increase gains.
Since this thread will probably get closed, in an effort to try and keep it open for constructive criticism here is a list of what I think could be changed/improved.
- Why does the bot get stuck at all? I don't even understand why this happens, if the bot goes up to a wall and then just doesn't do anything there must be a huge programming fail there. I don't even see how you could overlook this.
- Why is it so slow? It pauses sometimes between movement, it ignores targets, it starts to attack targets but then ignores them, and then 100 yards later will decide to go back and get them. How do you overlook this?
- Why is it so clunky? Why do we need to download profiles custom classes loot configuration files just to get it to work? If you could make it into an all-in-one .ini file, this would work wonders.
- Not supporting spells. Why can't I use teleport for my wizard. It couldn't be that hard to program? If teleport is up use it to get to your next waypoint. ??????
- There are probably a lot more, but I'm going back to the other bot. I would gladly risk getting banned once a month in exchange for a 300% increase in yield and stability.
If by chance there is anyway to get a refund I'd be glad to hear it, it is a pretty massive fail when autoit scripts can pull more gp/h then a bot in development for a month.
I don't mean to say that DB should cease operations here, people can use this all they want, I just want to give honest input as to why I'm reverting back to other bots.
Last edited:
