Alek

Safer = mirror

Uploading version .121

This isn't 1990, they can detect bots without needing to manually walk around the worlds.

The clear set of regulations:

You will have to either wait for another dev to finish fixing the client or wait for me to get back home. Sorry for the delays. Mirror mode should be working along with a decent chunk of users.

Try following these instructions:

have a mod unban you from chatbox, too tired from updating the client.

Fixed mirror mode and OSBot only loading World 301. Check it out here:

I made a few quick patches to try and remedy about 20-30% of users that had issues starting up OSBot. Although I typically don't even look at mirror mode, I was able to make a fix so that service should now be restored. Although I doubt this will change anything, please help me by testing development builds before I make them stable. Version 2.4.119 was released for 17 days before I put it as a stable build. Please remove any old version of 2.4.120 that you have and make sure you get it the latest version from the download link above or the homepage. I made additional changes to the 2.4.120 version.

Try this version out: https://osbot.org/devbuilds/osbot 2.4.120.jar

You will be unbanned on the next version of OSBot.

Thanks working on a fix

Try again with this version: https://osbot.org/devbuilds/osbot 2.4.119.jar

For those having issues and know how to use cmd/terminal: Change directory to where your OSBot jar is located and type in the following command: java -jar "osbot 2.4.119.jar" -debug 5005 Get the client to the point where it gives you the error. Copy and paste everything in the terminal/cmd window here, please do not screenshot.

Once again you will have to unfortunately wait for a fix since the bot is now on stable release. I had the bot sit as an optional dev build for 17 days with no complaints.

That sucks! We take the development builds pretty seriously and although we cant really force all of our customers to test these versions, it certainly helps both us and the customer.

I released OSBot 2.4.119 17 days ago, which should have been plenty of time for you guys to test it out before I forced the newest version. Unfortunately you will now have to wait until MGI can take a look and make a fix.

So you didn't get a script or your money back? You did get the two smaller scripts which you paid $50 for though?

Sorry it's a little late now, it was on the dev build for 17 days. I'll have MGI look into it.

Oh so we are going to take Discord banter as my official decisions? Well that's one less place you can find me.

Moved to stable and updated the API docs.

I think you had two repositories, the last one got deleted. PM me for more information.

There was an issue with his repository so i had to remove it. Looks like he changed repositories and the old one technically didn't exist but the script was still cached. In the meantime try using my Macro Killer script, it will kill your chickens.

I could go back to just not allowing private scripts and banning anyone that makes, sells, or uses private scripts. The rules are pretty straight forward regarding private scripts, there wasn't any picking and choosing. In k9thebeast's case, the script was already made at which point I was trying to help out both sides as a courtesy. The scripter was paid and k9 receive his script. If everyone here wants to chip in and pay me extra money to sit down and review private scripts all day, then fine. Otherwise I have to focus on our own products and services.