d0zza

What are you using to search the chatbox? You can use OnMessage to do something whenever the message you want has appeared in the chatbox.

Bump

Bump

Use the widget debugger to get some more information on that widget, you can definitely do what you want with it.

Open osbot settings, go into the Debug tab and click the Widgets checkbox, now you'll be able to see that each bank slot is made up of a widget.

Not sure why you need to do this, the osbot bank withdraw api method automatically does all scrolling and tab changing necessary to withdraw an item even if it's not visible. But if for some reason you still need to do this, each bank slot has a widget, use the widget debugger and you should be able to figure out how to do this.

I really doubt this is the case, the break condition should be getting evaluated multiple times a second. If you could post your code for the WalkingEvent it'd be much easier to help you. Another option is to disable running for the WalkingEvent by setting the energy threshold to greater than 100 by using: walkingEvent.setEnergyThreshold(101);

Bump

The devs usually catch all of the broken hooks. It's very rare they miss some obscure hook, if they do just make a post in the client bugs section.

Bump

Yeah just put the images into your Osbot\data folder and you'll be able to use them.

The new directory is OSBot\data. You can get this directory in your script by doing getDirectoryData() and then concatenate the file name onto that.

If you're wondering how to get the widget ids/strings you need use the widget debugger in osbot settings.

You should learn how to write a basic java program before trying to script. There are plenty of online resources that are great to learn from but if you don’t know what a return value is or how to use it you’re going to have a very hard time scripting.

Bump

The client should be working now, the devs don't need to release a new client in order to fix hooks.

Bump

Bump

This guide may be a little outdated. 1) Make sure you have the osbot jar set as a dependency for the project. 2) Try just using getInventory().isFull() instead.

Bump

Bump

When the monster is spawned the NPC Callisto is not null, however when it isn't spawned it is null, which means you're calling .isVisible() on a null object. This is the reason why your client crashes, have a null check as well in your code.

Bump

The error you posted above is to do with the osbot API and mirror mode. Your script should run fine if you use injection instead of mirror mode.

As far as I know there aren't any configs for the coal bag, I've used a boolean flag in the past to check if it's full or not.