Alek

I removed the Resizable Mode random and added better detection if you are in resizable mode or not. There was an "issue" recently that was related to people starting their client in resizable mode, probably after playing on a helper client like RuneLite. When this happens you will be greeted with a warning message to switch into fixed mode and restart your client. Please be mindful that running in resizable mode is not fully supported yet, and even if you switched to fixed mode - you will still need to restart. Changelog: -Added warning message when loading OSBot in resizable mode -Patched minimap issue, which was related to resizable mode -Removed resizable mode random event (can now run scripts) -Patched Trade offerAll -Patched Friend/Ignore tabs -Improved Bank open method

Please read my post here: https://osbot.org/forum/topic/146120-no-bots-working-after-update/?do=findComment&comment=1723570

2.5.13 has been released for 36 days, I try my best to test the client but its not feasible to do unit testing. It's another unfortunate realization that dev builds go unused so from now on I will be going back to pushing everything immediately to forced stable. Please do not make anymore posts regarding this, I'll work to fix the issue over the next few hours.

This isnt really useful information, I'm sorry.

Can I have the rest of the log?

Thanks guys for helping me out, I'll try testing my scripts too.

Mind telling me specifically which scripts?

Yeah I don't think 30 days of VIP is worth a maxed F2P account - unless you do (but I wouldn't recommend it).

That's really interesting and I'd like to know what's going on as well. Edit: Are you getting any errors in the logger?

No deal ?

I need a throwaway account with no membership on it, needs to have at least one unread message (visible on welcome screen). I'm willing to give 1 month of free VIP for the account. Thanks!

But what about anti ban? Are you using scripts with anti ban?

@Jackthedon - Are you sure this is for OSBot 2.5.15 only? I didn't make any changes to tabs. This is kind of important.

I... I don't know what the f*** this means.

Download Link: http://osbot.org/devbuilds/osbot 2.5.15.jar Changelog: -Removed connection retry codes from AutoLogin: 8, 17 -Added connection retry code to AutoLogin: 21 -Added MISTHALIN_MYSTERY to Quests -Attempted to relieve client freeze issue from AccountSelector if hooks fail to load -BreakManager will explicitly state that it can't log out because you're under attack --Should help pinpoint BreakManager issues

Moved to mirror mode forum.

Moved to mirror mode bug reports.

Closing this because the answers here are good, and I don't want the band of trolls ruining this.

They didn't find a new way, this would imply they know something that reversers don't already know. With this said each bot can have a different method of injection, which would mean they custom create injection detection for every single bot - at which point they should just invest into anticheat and use signature scanning and call it a day.

Says the man who uses another bot client that clicks on entities that are not even visible, and claims the interactions to be revolutionary - yet they were copy pasta'd from rs-hacking (or similar sites) over 10 years ago. How do I know you weren't banned using their client which obviously has a lot of questionable methods? There's no lying from our end; our injection techniques aren't naive; I really don't want to spend time writing out in layman's terms what this means. Although the other devs aren't as outspoken as me, it doesn't mean they are inactive and don't care. I can't really discuss everything we do to protect your accounts, as that would compromise it. What I can say is that the OSBot team is not a bunch of new developers, they've been doing this for many, many years and you're in good hands. We can't stop server-sided heuristics. If you want to run a F2P/P2P farm with accounts that botted off tutorial island, I'm sorry but you're going to run a much higher risk. Please take a look at my botting guide.

Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

Because you can use any generic combat script to kill them. In the future, use Widgets closeOpenInterface() instead of the method you wrote; it handles more interfaces. Seems like a good start though.

The instance is not the script, its bot.