AsBakedAsCake

Hello everyone!
A new version of DreamBot is now live!

Changes:
Added more ItemTeleport checks Various minor fixes Always remember, to be on the latest version of our client you must run DBLauncher.jar! The client does NOT update itself!
Thanks,
The Dream Team

When I stop my scripts, onExit is looping like 15 times.
Started happening recently. No negative impact on scripts but figured it's worth mentioning

Edit: Pretty sure this only happens when I use stop(). Manually stopping the script fixes it.

Update on this: I found just returning -1 instead of using the stop() function fixes it.

yeah i'm in the same boat, it's really weird all of a sudden happening...

Annoying to say the least, the past 4 days ive been facing this issue since getting stock back, in that time I have made a whopping 14M back on my bonds/accounts etc lol because of all the freezing/closing. At the moment i'm baby sitting them to see where they go, and if any errors happen but even then it's like I have things I need to do and shouldn't be doing this lol.. Annoyed to say the least, especially as someone who is reinvesting back into the website like many others

I'm having a similar issue with client freezes, I'd already made a post about a possible memory leak, but no one ever replied.
Mine don't freeze too often though, it seems to usually happen after 20+ hours.
Also doesn't matter what script I'm using. Increasing the allocated ram did seem to help a bit with it, but still getting the occasional freeze.

I make classic tobacco pipes as a job, here are a few that are actually still available, message me if you'd like to discuss.
My company is AndersonBriars, and you can view work on instagram! 

Very high starting about 2-3 months ago. Before I was running 200+ accounts 24/7 with minimal bans, but around 2-3 months ago they cleared all my farms. I've been taking a break and every time I return my accounts get banned relatively quick. They even banned some accounts that I prepped over 1-2 years ago.

Don't bot your main, it will 100% get banned. Doesn't matter if you're watching or not.
Most bans are based off detection.

Apparently the estimated time OSRS is supposed to be back up is 12:00 GMT.
RIP.

You definitely got chained, it's been happening a lot recently.
I'd suggest only botting 1-2 accounts until you get a feel for ban rates, then scale up. That way if you get banned, losses are minimal. I'm currently in this process as well.
If one thing gets you banned quick - scrap it, move on, and try something else.

I think I found the issue possibly, I'll push a hotfix in a few minutes and you can let me know if it helped.

No worries, I do appreciate any constructive feedback so we can improve the client.
And thanks to your report, I actually found that the issue from the GE -> Lumbridge taking different paths was actually not due to the random paths, it was a simple core bug with the pathfinder so that'll be fixed and we'll see less sub-optimal web paths everywhere in the next build.
Thanks again for the report.

Make sure to update the client, as the latest build is 3.14.2.8. If it still has that issue, run the client with the -debug arg and send those logs over.
Will try to recreate this.
There's nothing to listen to if no one complains
You're describing the randomized paths, which I've already tweaked once from your prior input about them being too random. I've just further lowered the randomness for the next build, and will check the output of those to make sure those paths are less random.

If you go through my thread, lots of people are experiencing the same problems. I do think the update had something to do with it, regardless of what a few others say.
 

It's not every bot client that's having these problems. There are two other platforms that have avoided this issue.

I already stopped using DreamBot for now. With a 2-3 hour ban time, it's impossible to make any profit.
Hopefully the detection thing gets sorted.

If they did update their detection, hopefully there is something the developers here can do to get around that.
There are at least 2 other clients out there where ban rates haven't changed and people are still having success.

I already stopped using DreamBot for now. With a 2-3 hour ban time, it's impossible to make any profit.
Hopefully the detection thing gets sorted.

If they did update their detection, hopefully there is something the developers here can do to get around that.
There are at least 2 other clients out there where ban rates haven't changed and people are still having success.

I'm here to call for the removal of all the new content from 3.14, urge the return of all the deprecated methods, and urge the engineers to seriously consider users' opinions and stop using us as guinea pigs.
I don't want to wait for you to update and experiment again and again, it is meaningless.
Again, I love using db, the community is great, the API is convenient, and everything is wonderful, but I need something to live and hope for, or I'll have to give up. After all, I have to survive, too.

same thing here had a farm going strong for 3 months 0 bans...2 days after update I lost like 12 accs lmao 

I started up a fresh account 600+ days rested before I went to work, brand new proxy.
Account was banned 3 hours after I left.
This update sucks. We need a revert.
Anyone that's had a successful gold farm on Dream Bot knows exactly what I'm talking about. Maybe the update broke Covert mode?

This is 100% true, before the last update i was running my private scripts almost 247 and i was catching less bans, now is just awful even with cracked accounts with decent total levels still the same getting bans even at evening which is odd af, i been using this bot since 2017 and its never been like this before 

Just want to add that I purchased VIP / Prem scripts on Friday evening and was banned this morning, hardly 24 hours of use..
refunded of course, but quite the distaste to be someone new to dreambot.

Yes, I am the same way, every day I keep being banned, before this, I can keep my robot alive for a month or more, all the measures have not changed, but it is banned.
I changed the proxy ip, reinstalled the system, and used accounts that had been cooled for more than 180 days, but that didn't work and the vast majority of accounts didn't survive 24 hours before they were banned.
I don't know what else I can do.
As the user of the db, I don't know whether because of version 3.14 has led to all of these cases, however, did not happen before 3.14 so frequently banned, I hope the developer serious to think about the future, whether to back version, not for some unnecessary functions, the user as a test of rats.