Camaro

Here's where you can find information about CLI arguments Basically, open the command prompt and type: java -jar "C:\PATH TO OSBOT JAR HERE\osbot.jar" -allow norandoms In the next update, I will add script CLI args allowing to define the selected worlds from CLI, along with pulling in the parameters saved as default in the GUI (whenever you press "OK", any settings you have are automatically saved as default)

Just use datacenter proxies if you're fine with accounts getting banned next day (which you should if you're suiciding)

Could just leave it as a string and do text.equals("1234")

I've been able to recreate this by running a blank script and cycling through the worlds manually, not my problem so I cant fix it unfortunately. Try running with CLI arg -allow norandoms to disable the login handler.

You dont need to instantiate a new GE object. The org.osbot.rs07.script.Script class (which this class is extending) already contains an instance to a GE object. You can access it by getGrandExchange() edit: which, by the looks of it, you are already doing in the if condition

Was anything posted to the log?

I plan on doing some major improvements soon to this soon once i'm able to generate a continuous supply of testing account. Also, feel free to pm me any suggestions for randomization

Using my Simple Continuous Loop Class,

Could do public void onStart() throws InterruptedException { gui = new fighterGUI(); while (gui.isVisible()) { sleep(1000); } . . . } to make it wait

If you could lend an account with 500 total, yes

I can add a CLI interface to define worlds to use ex. -script name:300-301-302, will this work for you?

Hmm not exactly sure what this could be. Im guessing this happens when you press the pause button?

Hey guys, made a simple app to help gather collision data for specific positions. Source Code Download Jar

Ive been banned before within 30 minutes of creating the account without botting. I'd suggest throwing out that proxy.

Sure, ill add that in soon

Issues should now be fixed.

Can you give me some more information on the freezing? Was there anything in the logs? Was it able to fill the inventory? Did it happen every time?

If you're calling the method in onLoop(), it would be 'this' (Main extends Script) Although passing the script instance is bad practice... and I would suggest against using this due to the comments from above. You can pass multiple areas to the webWalker and it will automatically choose the closest.

Optional<NPC> cageFishingSpot = this.getNpcs().getAll().stream() .filter(o -> o.hasAction("Cage")).min(closestCageFishingSpot); if (cageFishingSpot.isPresent()) { cageFishingSpot.get().interact("Cage"); fishingConditionalSleep.sleep(); } can be replaced with NPC cageFishingSpot = getNpcs().closest(o -> o != null && o.hasAction("Cage")); if (cageFishingSpot != null && cageFishingSpot.interact("Cage")) { fishingConditionalSleep.sleep(); } Notice How there is a null check in the lambda expression itself. Also, I moved the interact() method into the if condition. Only sleep if the interact() was successful.

Which options?

Yeah, I could have extended ConditionalLoop instead of event, but it wouldn't be different internally because ConditionalLoop executes an event anyway. Either way, enables lambda expressions similar to the custom sleep methods that are around.

Added something similar

So... in a lot of these methods, you're calling getWidget() multiple times back to back. This stresses the MethodProvider more than it has to as it retrieves an instance of this object every time you call it. You should only call the getWidget() method once in the entirety of the method you're using it in. For example, private boolean isMyWidgetWorking() { RS2Widget wid = getMyWidget(); return wid != null && wid.isVisible(); } Also, having the above method just to check if the widget is working isn't really necessary. Just put it right in the if condition in onLoop(). Finally, I hear getWidget().singleFilter() works pretty nice

Here's a little class to help execute a self-contained loop under a certain condition Usage

Making the account is a completely separate process from doing tut island. First, you would have to make a program that would generate an email address and then register an account on the runescape site. After that is complete, you could start the osbot client through CLI in that same program (think python subprocess module) and pass the email and password as parameters. Along with that, you would pass the name of a script that would complete tutorial island. Multithread, and you have millions of accounts instantly.