Alek

Need fresh blood, not a crusty ex-mod or someone that's going to push their market services. What about @Dbuffed?

you too cuckolis

Read the following article I wrote: https://osbot.org/forum/java

In the next version of OSBot it will detect your Java version instead of giving you the "verify your boot options are valid" message. If you are not on Java 8, it will tell you to visit this new article I wrote here: https://osbot.org/forum/java DO NOT suggest fully downgrading Java or uninstalling Windows, Linux, Mac.

I don't understand, you had antiban on? You should have not been banned. By the way "antiban" is against the rules because I consider it scamming. Can you take a screenshot of the GUI that said "antiban settings"?

No gravedigging

The issue comes from extending GrandExchange, because the modules aren't initialized. You can use either initializeContext from MethodProvider or initialize the context yourself. It's returning null because of this. Not related to 2.5.8 or the new version, I guarantee you.

Are you using CLI commands, specifically -norandom?

Well, it helps if you already know C++. The difference between C and C++ is using malloc instead of new, and using structs instead of classes. Other than that they're fairly similar. I don't have any good advice for learning it, since I already knew C++ before learning C which made it really easy.

Low resource mode, if I have the checkbox there I will have complaints that users cant see their paints, even if it says "Disable paint".

Anything that you're painting. Scripts with fancy paints are certainly more cpu expensive than a script with absolutely no paint.

Sorry for all the recent releases, I promise this is the final one provided there are not even more problems. The initial release had an oversight with norandoms not being compatible with the GraphicUtilities caching. The follow-up to that resulted in the ResizableMode solver not being displayed on Resizable Mode - so it worked as intended but still left me with the problem of displaying a message to the user that their script won't work. Finally decided to use our painting system instead to affix a permanent message that will only go away after restarting the client (stopping/starting scripts wont make it go away). So now although you can still bot with resizable mode on, the warning message will never disappear regardless of -norandoms or not. This update is important for both scripters and the dev team to help us identify issues that users are having with the client.

Doing another release, sorry for all the updates.

2.5.21 patch now works with -norandoms argument.

Yes because the entire client needs to recache, this has existed for a few months - but it probably went unnoticed because most of the API supports resizable mode anyways.

Something doesn't seem quite right with the error you are giving me, can you PM me your source code? Either the bot instance or methodprovider are null for you to be getting this error. Also please let me know all the CLI commands you are using and if you are using mirror mode or not. Edit: Just realized you are using a custom login handler. You're most likely in resizable mode.

Well I don't work on mirror mode but nothing seems out of the ordinary for the client as a whole, best bet is to wait for MGI to take a look.

No ex-mods or someone active in the market.

Can you post this again but with the actual text and not a screenshot?

What does the logger say

Once again, the client version is completely unrelated to any functionality of mirror mode. Reverting back to version 17 wont solve whatever problem exists (which I'm still not sure what you're referring to). Could you elaborate on the problem?

The client version is 100% unrelated to mirror mode version.

They check to see if you look at your exp in the skills tab. Real humans will check this, so if you dont check it you will get banned much faster. Also they check if you are using random numbers in your scripts, because each script and each bot that exists has a profile associated with it. So make sure to do stuff like random(422, 9421). Don't use whole numbers because that will look suspicious.

OSBot will now force you in fixed mode again, so you will not have the option of running resizable mode unless you start with -norandoms. I thought the warning message would make it clear that using OSBot in resizable mode is not stable, however perhaps the message was not clear or the message was widely ignored causing a whole assortment of issues. Now instead, OSBot will detect resizable mode and give you this warning: Deposit Box has now been patched. Thanks for using OSBot!