[Release] Demonbuddy - Glorious Monday build (#252)

Why not just TP out?

 

i wanted to use the wp at the end of keep depths 3 to go to my next area instead of tping and using the wp in town.

instead i just reversed it and went depths 3-2-1 and after leaving 1 just runs out to battlefields which works fine.

 

Nesox can you atleast give us an update of whats happening with the latest release bugs?

 

Sorry for my language.. The bot has become freaking useless after the recent releases, the longest session I've had, without being stuck some odd place, is 30 mins. It worked fine before the release, why fix something that aint broken man?

 

Buy a mirror and stand infront of it long and hard and then repeat your question to your self....

Why did you update if it aint broke and no features you'd use.

In other news you are right though in the sense 242 and 246 did cause issues 240 and before were fine with object handling

 

If you agree with me, then why do you write this?

 

Because instead of complaining nonstop I just went to a previous version till its fixed?

 

Crashes.

Actually I got bot crashing while trying to run kick's acts profiles for leveling.

Any clue if there is any luck to see it fixed or it's just because of the development status of the scripts ?

 

Another run of 1 step forward, 2 step back, this seems like a regular thing

 

While that is a temp fix... It is not how support should work... You guys seem to be ok with getting bent over. While others see this as bullshit, and lack luster support.

 

why is everyone so upset? the last 3 builds didn't work well for me, so im just using the last stable version i have run.
like .222 its old but it works... shouldnt be a big issue

 

No, its just that I realize that they are working at their own pace and while they are there is still a workable product at the moment. Of course in the perfect world it'd be going to how everyone personally wants it to be, but things happen.

I am not getting bent over, I am being reasonable.

 

Reasonable is not trying to produce more bots when you are already short handed.

 

I'm also getting a lot of stucks in open fields, next to weapon racks, corpses, etc. that seems to be only happening with the newer version. Trinity 1.5 is throwing missing unstucker API errors when using with DB 222.

 

I never got to try out 242 does anyone have a copy of it, I have 246 and it keeps crashing on me and would like to try 242 before going back to 222.

 

So you are really back to the trying to intimidate me method?

I will keep stating the obvious facts that you guys do not care about your customers.


I really do hope you guys beat blizzard when it comes down to it in a few months. Sooner you do the sooner other people can produce bots without fear of being shut down.

Simple fact is the only reason you guys are still operational is no one else has wanted to challenge them in court.

 

going downnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn

bann inc!

 

I have been having issues with the 2 latest versions of the bot crashing D3. It used to run for 20+ hours easily, but now I get maybe an hour in before it crashes. I deleted all of my log files, and am going to run just one client. I will upload the log if it crashes, since I had like 10 log files for just yesterday alone.